Topics / Engineering Leadership
Engineering Leadership Podcasts
55 shows and 7,618 episodes sit under Engineering Leadership.
The best podcasts on engineering leadership in 2026: management transitions, CTO scope, technical debt strategy, org design, and work intake — curated from the PlayNext corpus.
Photo: Lazar Stankovic on Unsplash · Unsplash License
Swipe · Engineering Leadership only
Swipe through Engineering Leadership
Save time discovering your next favourite podcast by listening to just the best minute of an episode.
The engineering leadership slate · every cover a link
All 55 engineering leadership shows →
Next to this on the shelf
Choose a subtopic
Before you press play
Finding the right Engineering Leadership show for you
The hard part usually begins after the promotion, when technical judgment is still expected but every decision now travels through people, incentives, and incomplete information. In audio, that tension produces everything from workplace advice to long technical interviews. The strongest episodes stay close to recognizable situations: unclear authority, accountability without control, fragile systems, and pressure from above. You can hear experienced engineers thinking through the mess rather than presenting leadership as a finished doctrine.
The manager’s actual inbox
Soft Skills Engineering starts where formal management books tend to stop. Its two-host mailbag format treats listeners as capable engineers stuck inside strange organizations, and the dry humor keeps difficult career questions from becoming grim. Titles such as Episode 454: Tracking productivity? and my CTO is ChatGPT and Episode 451: Un-collaborative architect and who is my boss? capture its fondness for problems with several awkward layers. Episode 507: I got fired unexpectedly and breadth and depth widens that frame from management trouble to career resilience. Come here for candid reasoning, qualified advice, and the occasional terrible hypothetical that somehow clarifies the real problem.
Developer Tea is more deliberate. The solo format takes one workplace pattern, defines it in plain language, and follows its consequences until the advice becomes usable. A Pragmatic Definition for Accountability is a clean entry point for managers tired of treating accountability as a motivational slogan. What the Science Actually Says About Effective Feedback tackles another leadership staple, while Why Reducing Complexity Is A Sign of Seniority connects technical maturity with the ability to make work easier to understand. Episodes are compact in spirit even when the reasoning takes its time.
For a process-heavy counterweight, Software Process and Measurement Cast brings a practitioner’s interest in measurement, delivery pressure, ethics, and change. Its interviews test principles against workplace consequences. The tone is collegial, occasionally dry, and comfortable with questions that resist a tidy answer.
When leadership becomes architecture
At larger scale, organizational choices become visible in the systems. SeAñors at Scale - Software Engineering & Tech Leadership approaches that boundary through working-engineer interviews, usually moving from an origin story into architecture, tradeoffs, and the inevitable gotcha. Observability at Scale with Erik Grijzen, Principal Software Engineer at New Relic and MicroFrontend at Scale with Igor (Director of Engineering at Cloudflare, co-creator of Angular) and Natalia (Principal Product Manager at Microsoft) signal the level of detail. Databases at Scale with Tyler Benfield (Staff Engineer @ Prisma) | ORMs, Indexes, Connection Pooling & Scaling Postgres to Billions of Requests is the long-form option when a quick leadership takeaway would feel evasive. This is management heard through the design decisions teams must eventually live with.
Software Engineering Radio - The Podcast for Professional Software Developers occupies a similarly technical register, though with a more scaffolded interview style. Questions define terms, separate categories, and keep asking for the next layer down. Listeners seeking leadership conversations that retain implementation-level precision are well served here.
The narrower Engineering Leadership Excellence Podcast offers Driving product mindset and engineering excellence at scale (with Vinay Ram). That title puts product thinking and engineering standards in the same conversation, a useful pairing for leaders whose remit crosses both.
Influence, change, and the view from above
Some leadership problems only make sense once authority enters the room. It Depends: Lessons in Technology Leadership goes directly there with Working with the CEO: Close Enough to Influence, Independent Enough to Be Honest. The dilemma is sharply drawn: access can increase a leader’s influence while making candor harder to preserve.
Innovation and the Digital Enterprise takes a broader organizational view. Balancing Speed and Stability in Digital Transformations with Adan Pope names a tension familiar to any team carrying legacy systems and new expectations at once. Communication and Culture Drive Business Outcomes with Sean McCormack places the social machinery in the foreground, and Leading with Humility Through Uncertainty with Michael Pozzi offers a quieter route into executive judgment. The interviews favor practical experience over grand declarations.
For the changing role of the engineer, Karachi Wala Developer is unusually direct. The Shifting Role of the Developer: From Writing Code to Writing Specs and From Coder to Architect: The Power of the Producer Mindset both point toward work shaped by leverage and direction rather than code volume alone. Stop Reviewing Code, Start Reviewing Tests: TDD in the Age of AI brings that shift back to a concrete engineering practice.
For wider technical listening, move up to Software Engineering. AI & ML Engineering follows the model-building and agent side of the field, while DevOps & Cloud stays closer to infrastructure and operations. For programming technique, head instead to Languages & Craft; stay here for judgment, teams, and responsibility.
Where to start
Begin with Soft Skills Engineering if the problem already has names, meetings, and office politics attached to it. Turn to Developer Tea to hear one management idea examined carefully. Try SeAñors at Scale - Software Engineering & Tech Leadership for the connection between organizational decisions and production architecture. For executive influence, start with It Depends: Lessons in Technology Leadership and Working with the CEO: Close Enough to Influence, Independent Enough to Be Honest.
Featured shows below are part of the PlayNext catalog. Updated weekly.
Featured shows
5 shows, described rather than listed
Each has a short write-up and a note on what it does best here.
The clearest starting point for engineering leaders: GM thinking, company archetypes, resilience, trust, and change all in one feed.
Brisk, dry, and listener-letter-driven — the show for engineers wondering whether management is actually a good idea.
For leaders who believe the soft problems usually have a system underneath: intake, prioritization, micromanagement, delivery ethics.
Covers the full arc: becoming a CTO, leading what you haven't done before, technical debt as strategy, and organizational design.
Steady, technical, and workmanlike — scaling engineering management and the CTO role grounded in real practitioner interviews.
Where to start
4 routes in, one per reader
Start with 'Episode 333: Unsure about management and I shall decline the offer' — it cuts through the ceremony before you commit.
'Work Intake Nuances in Mid-Management, Seamless Communications, Essays and Conversation w/ Jeremy Berriult' names the squeeze most new leads feel first.
'Becoming a CTO' and 'Technical Debt Isn't the Enemy: A Strategic Framework for Engineering Leaders' cover scope, architecture, and ambiguity together.
'How to convince your CTO it's worth paying down tech debt' catches leadership where it usually appears — in debt, architecture, and the next uncomfortable tradeoff.
Glossary
Terms worth knowing before you listen
The process by which a team accepts, filters, and queues new work — a common pressure point for mid-level engineering managers balancing stakeholder demand against delivery capacity.
Accumulated shortcuts, outdated decisions, or missing investment in a codebase that increase future cost; managing it strategically is a core engineering leadership responsibility.
How an engineering organization is structured into teams, reporting lines, and accountability boundaries — decisions that shape delivery speed, communication, and culture.
The move from individual contributor (a role measured by personal technical output) to engineering manager (a role measured by team output and development).
Leadership practices that hold as an organization grows: hiring loops, delegation, performance frameworks, and coordination across multiple teams or product lines.
A project-control technique that compares planned work, completed work, and actual cost to give quantitative delivery status — relevant where Agile methods meet regulated or contract-driven environments.