Podcast thumbnail for Engineering Evolved

Engineering Evolved

Claim This Podcast

by Tom Barber

17 episodes
Updated Daily
Accepts GuestsHas Sponsors

Podcast Overview

Where business meets innovation and technology drives transformation. Engineering Evolved is the podcast for leaders navigating the forgotten ground between startup chaos and enterprise bureaucracy. If you're building and scaling teams at organizations in the middle — where startup rules no longer apply and enterprise playbooks are far too large — this show is for you. Hosted by Tom Barber, each episode explores the real challenges facing today's engineering leaders: scaling systems without breaking them, building high-performing teams, aligning engineering strategy with business goals, and making technical decisions that drive measurable impact. Whether you're a Director of Engineering, VP of Technology, CTO, or an IC engineer stepping into leadership, you'll find practical insights drawn from real-world experience — not theoretical frameworks that only work on whiteboards. Topics include: Scaling engineering teams and systems for growth Building effective engineering culture Bridging the gap between technical and business strategy Leadership tactics that actually work in the messy middle Making architectural decisions with limited resources Navigating organizational complexity Engineering Evolved — guiding today's leaders through the evolution of engineering. New episodes drop weekly. Subscribe now and join the conversation about what it really takes to lead engineering in the modern era.

Language

🇺🇲

Publishing Since

11/9/2025

1 verified contact email on file for Engineering Evolved

Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.

Recent Episodes

Episode thumbnail for From Napkins to Agents: How AI Rewired Product Design

July 8, 2026

From Napkins to Agents: How AI Rewired Product Design

<p>In this episode of Engineering Evolved, Tom sits down with Amelia Prasad, Director of Product at Concept to Cloud, to trace how AI has reshaped the day-to-day of UX and product design. Amelia — who came to product from astrophysics and climate science — walks through the shift from manual research, whiteboards and "back-of-the-napkin" sketches to building zero-to-one products directly in Claude Code.</p><p>It's not a hype reel. Amelia is candid about the friction: learning version control from scratch, bloated six-thousand-line files, the designer-to-developer handoff problem, and the diminishing returns of heavy token usage in tools like Claude Design and third-party wrappers such as Lovable. Her current answer is a marriage of tools — passing work back and forth between Claude Code and Figma via MCP — so prototyping speed and real usability, accessibility and design-system rigour can each live where they belong.</p><p>They close on what the next 12 months might hold: more human-led user research, not less, and why juniors and design intuition still matter in an industry tempted to hire only senior builders.</p><p><strong>Chapters</strong></p><ul><li>00:00 — Welcome &amp; introducing Amelia</li><li>02:53 — From astrophysics to product design</li><li>03:33 — The pre-LLM UX workflow: manual research &amp; competitive analysis</li><li>05:23 — Old-school tooling: Figma, Miro, Maze, pen &amp; paper</li><li>06:56 — The lost art of napkin sketches and paper prototyping</li><li>07:57 — Meeting at Princeton: first exposure to LLMs</li><li>08:52 — AI workflows before AI building: the interview note-taker</li><li>11:02 — Stepping into Claude Code as a non-developer</li><li>13:45 — Handing off code on a small team: value and limits</li><li>15:17 — Guardrails, context and the handoff problem</li><li>20:02 — Lovable, Cursor and the trouble with wrappers</li><li>21:05 — Claude Design: token cost and diminishing returns</li><li>22:45 — Figma's MCP and the two-way handoff</li><li>24:50 — A suite of tools: knowing when to hand off to which</li><li>29:06 — Why active engagement in Figma beats waiting on the terminal</li><li>33:02 — The next 12 months: user research, systemic processes, robustness</li><li>38:16 — Will design jobs disappear? Juniors, intuition &amp; human-in-the-loop</li><li>41:27 — Wrap-up &amp; thanks</li></ul><p><strong>Key takeaways</strong></p><ul><li>AI adoption in design was gradual — automating admin and research before it could build whole products.</li><li>The real skill now is orchestration: knowing which tool (Claude Code vs. Figma) does which job best.</li><li>Speed doesn't replace craft — usability, accessibility and design systems still need a designer's hand.</li><li>Human intuition and user research grow more important as products become AI-native.</li><li>Cutting junior roles is short-sighted: today's juniors build the intuition tomorrow's products depend on.</li></ul><p>Enjoyed this one? Find us at conceptocloud.com and on LinkedIn. Subscribe to Engineering Evolved so you don't miss the next episode.</p>

Episode thumbnail for The $13K Company Backlog: Private Equity's Capital Return Crisis in 2025

June 24, 2026

The $13K Company Backlog: Private Equity's Capital Return Crisis in 2025

<p>Private equity firms are facing an unprecedented challenge with a backlog of 13,000 companies. The biggest issue for 2025 isn't raising capital or sourcing deals—it's successfully returning capital to investors after buying at market peaks.</p> <p><b>Show Notes</b></p> <p><b>Episode Overview</b></p> <p>A concise analysis of the private equity industry's current crisis: managing a backlog of 13,000 companies while struggling to return capital to investors.</p> <p><b>Key Topics Covered</b></p> <p><b>The 13,000-Company Backlog</b></p> <ul> <li>Unprecedented number of portfolio companies awaiting exits</li> <li>Industry-wide challenge affecting firms of all sizes</li> <li>Redefining what success means in private equity</li> </ul> <p><b>The Capital Return Challenge</b></p> <ul> <li>Why returning capital has become the #1 priority for 2025-2026</li> <li>Shift from traditional metrics of success (fundraising and deal flow)</li> <li>Impact on limited partners and fund performance</li> </ul> <p><b>Market Timing Issues</b></p> <ul> <li>Consequences of buying at market peaks</li> <li>The "top of the bubble" problem</li> <li>Current valuation challenges and exit environment</li> </ul> <p><b>Key Takeaways</b></p> <ol> <li>The private equity industry faces a structural challenge with 13,000 companies in the exit pipeline</li> <li>Capital return has superseded fundraising and deal sourcing as the primary challenge</li> <li>Firms that bought at peak valuations are particularly vulnerable</li> <li>The traditional definition of private equity success is being rewritten</li> </ol> <p><b>Relevant for:</b></p> <ul> <li>Private equity professionals</li> <li>Limited partners and institutional investors</li> <li>M&amp;A advisors and investment bankers</li> <li>CFOs and business owners considering exits</li> <li>Financial market analysts</li> </ul> <p><b>Chapters</b></p> <ul> <li>0:00 - Introduction: The Private Equity Challenge</li> <li>0:11 - The 13,000-Company Backlog Crisis</li> <li>0:19 - Capital Return: The New Priority</li> <li>0:28 - The Peak Valuation Problem</li> </ul>

Episode thumbnail for Your Users Don't Care If It's AI - They Just Want Results

June 16, 2026

Your Users Don't Care If It's AI - They Just Want Results

<p>Tom Barber challenges the AI hype cycle, arguing that users care about outcomes, not architecture. Learn why slapping an 'AI-powered' label on everything is the wrong approach, and discover how to thoughtfully integrate LLMs into products without falling into common pitfalls like dependency on unstable APIs or unnecessary chatbot interfaces.</p> <p><b>Show Notes</b></p> <p><b>Episode Overview</b></p> <p>Tom Barber returns with a critical examination of AI integration in modern software development, challenging teams to focus on user outcomes rather than jumping on the AI hype train.</p> <p><b>Key Topics Covered</b></p> <p><b>The AI Marketing Problem</b></p> <ul> <li>Why 'AI-powered' labels are often meaningless marketing</li> <li>The difference between machine learning (which has existed for decades) and modern LLMs</li> <li>Examples of invisible AI: spam filtering, fraud detection, map rerouting</li> <li>Users grade products on consistency, not on the impressiveness of the underlying model</li> </ul> <p><b>Engineering Considerations for LLM Integration</b></p> <ul> <li>Choosing the right model for your specific use case (Opus, Sonnet, GPT-4, etc.)</li> <li>Tradeoffs between cost, speed, and inference quality</li> <li>Building evaluation systems and fallback paths</li> <li>Managing latency budgets and graceful degradation</li> <li>Handling API outages from providers like Anthropic and OpenAI</li> <li>The risks of depending on frontier models that can be deprecated</li> </ul> <p><b>Trust and Transparency</b></p> <ul> <li>AI as a potential trust liability</li> <li>Managing user expectations around hallucinations</li> <li>The importance of data provenance and quality (garbage in, garbage out)</li> <li>When and how to disclose AI usage to users</li> <li>The ethical obligation to be transparent when AI makes consequential decisions</li> </ul> <p><b>Product Strategy</b></p> <ul> <li>Why you can't charge an 'AI tax' on top of existing pricing</li> <li>Pricing based on outcomes, not on the technology stack</li> <li>How to use LLMs to deliver genuine efficiency gains</li> <li>Reducing user overhead and friction through thoughtful AI integration</li> </ul> <p><b>Beyond Chatbots</b></p> <ul> <li>Why chatbots may be the most inefficient way to interact with LLMs</li> <li>The challenge: How to integrate LLMs without forcing users to type everything</li> <li>Asking 'What's now instant that wasn't?' instead of 'How do we add AI?'</li> <li>Innovation opportunities for those who can solve the chatbot problem</li> </ul> <p><b>Key Takeaways</b></p> <ol> <li>Users care about reliable outcomes, not whether you're using AI</li> <li>Engineer for model availability issues and API outages from day one</li> <li>Select and tune models specifically for your use case rather than defaulting to frontier models</li> <li>Be transparent about AI usage, especially for consequential decisions</li> <li>Focus on delivering value through AI rather than adding an 'AI-powered' label for marketing</li> <li>The future belongs to products that leverage LLMs without relying on chatbot interfaces</li> </ol> <p><b>Resources Mentioned</b></p> <ul> <li>Various LLM providers: Anthropic (Claude/Opus/Sonnet), OpenAI (ChatGPT-4)</li> <li>Example of model deprecation: Fable model being pulled</li> </ul> <p><b>Connect</b></p> <p>Engineering Evolved is hosted by Tom Barber. If you found this episode valuable, please leave a rating and review to help other leaders discover the show.</p> <p><b>Chapters</b></p> <ul> <li>0:00 - Introduction: Users Don't Care If It's AI</li> <li>1:01 - Machine Learning Has Always Been Here</li> <li>2:19 - The AI Marketing Problem: Selling Architecture vs Outcomes</li> <li>5:16 - Engineering Realities: Models, Consistency, and Reliability</li> <li>10:11 - The Cost of the AI Label: Trust and Pricing</li> <li>14:39 - When Users Do Care: Transparency and Consequential Decisions</li> <li>17:15 - Beyond Chatbots: The Future of LLM Integration</li> </ul>

17 total episodes available

Deep-dive analytics for Engineering Evolved

Frequently asked questions

Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.

What is Engineering Evolved?

Where business meets innovation and technology drives transformation. Engineering Evolved is the podcast for leaders navigating the forgotten ground between startup chaos and enterprise bureaucracy. If you're building and scaling teams at organizations in the middle — where startup rules no longer apply and enterprise playbooks are far too large — this show is for you. Hosted by Tom Barber, each episode explores the real challenges facing today's engineering leaders: scaling systems without breaking them, building high-performing teams, aligning engineering strategy with business goals, and making technical decisions that drive measurable impact. Whether you're a Director of Engineering, VP of Technology, CTO, or an IC engineer stepping into leadership, you'll find practical insights drawn from real-world experience — not theoretical frameworks that only work on whiteboards. Topics include:

Scaling engineering teams and systems for growth Building effective engineering culture Bridging the gap between technical and business strategy Leadership tactics that actually work in the messy middle Making architectural decisions with limited resources Navigating organizational complexity

Engineering Evolved — guiding today's leaders through the evolution of engineering. New episodes drop weekly. Subscribe now and join the conversation about what it really takes to lead engineering in the modern era.

How often does this podcast release new episodes?

This podcast updates daily.

Where can I listen to this podcast?

This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.

Does this podcast accept guests?

Information about guest appearances is not available.

Legal Disclaimer

Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.

All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.

We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.

While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.

By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.