The 20 Best Software Engineers Podcasts (2026)

Software Engineering Radio has been running since 2006 and is backed by the IEEE Computer Society and IEEE Software magazine, which gives it a kind of institutional credibility that most tech podcasts can only dream about. With over 700 episodes in the archive, it covers the full spectrum of software engineering — from system design and architecture to programming languages, testing strategies, and team practices.

Every episode is either a focused tutorial on a specific technical topic or an in-depth interview with a recognized expert. Recent guests have included researchers discussing continuous architecture, engineers working on low-latency AI systems, and language designers talking about the evolution of C. The rotating roster of hosts keeps perspectives fresh, and each one brings real industry experience to the conversation. Episodes run about 45 to 60 minutes and arrive weekly.

What makes SE Radio valuable for working engineers is its commitment to being a lasting educational resource rather than chasing trends. You can go back and listen to an episode from 2015 on microservices or 2018 on distributed systems and still get meaningful takeaways. The production is straightforward — no flashy sound effects, just substantive technical conversation. It holds a 4.4 star rating from 271 reviews on Apple Podcasts, and many listeners describe it as the podcast they wish they had discovered earlier in their careers.

Software Engineering Daily has been publishing interviews with working engineers roughly every weekday since 2015, which adds up to a back catalog of more than two thousand episodes covering nearly every stack, framework, and infrastructure fad of the last decade. Founded by Jeff Meyerson and carried on by a rotating group of hosts after his death in 2022, the show's format is straightforward: one guest, one topic, about an hour, usually with a founder or principal engineer from a company building something specific. Recent episodes have covered vector databases, Rust in the Linux kernel, WASM at the edge, Postgres internals, and the practical economics of running large model inference. The interviews are competent rather than flashy. Hosts come prepared, let guests explain, and resist the urge to turn every conversation into a hot take. That restraint is actually the point. If you want to understand what a particular tool does and why a real team chose it over the obvious alternatives, the archive is a treasure. Production quality varies a bit episode to episode given the volume, and the show's scope sometimes wanders into adjacent business territory, but the core remains a reliable way to hear engineers talk shop without marketing polish getting in the way.

Adam Stacoviak and Jerod Santo have been hosting The Changelog since 2009, and with over 1,000 episodes under their belt, they have built one of the most trusted voices in open-source and software development media. The show combines a weekly news roundup with deep-dive interviews and a rotating "Friends" segment that brings recurring guests into looser, more conversational episodes.

The guest list reads like a who's who of open-source software. Recent episodes have featured Steve Ruiz (creator of tldraw), Paul Dix (InfluxDB co-founder), Nicholas Zakas (ESLint creator), and Brett Cannon from the Python team. Stacoviak and Santo have a relaxed but focused interview style — they let guests tell their stories without rushing them, but they also know when to push for specifics on architecture decisions, business models, or community governance.

What stands out about The Changelog is how it covers the human side of building software alongside the technical details. Episodes about Docker security sit next to conversations about open-source sustainability and the trust models that hold the ecosystem together. The production quality is consistently high, episodes run about an hour, and the 4.7 star rating from nearly 300 reviews speaks for itself. If you care about the tools and communities that power modern software development, this show belongs in your rotation.

Gergely Orosz built The Pragmatic Engineer newsletter into one of the most-read publications in software, and the podcast spun out of it keeps the same tone: specific, opinionated, and written by someone who has actually shipped code at Uber, Skype, and Microsoft. Each episode is a long interview with an engineer, manager, or founder, and Orosz is unusually good at asking the questions readers of his newsletter would actually want answered. How did Stripe's engineering org scale past 1,000 people without collapsing? What does on-call really look like at Cloudflare? How do staff engineers spend their Tuesdays? Guests have included DHH, Martin Fowler, Charity Majors, Will Larson, and engineers from companies most podcasts never reach past the PR team. Orosz is Hungarian, records from Amsterdam, and has a direct interview style that skips the small talk and gets into headcount, compensation bands, and migration horror stories within the first ten minutes. Episodes lean longer, often 90 minutes or more, and the RSS feed doubles as an audio companion to the newsletter rather than a standalone show. If you write code for a living and want to hear how other senior engineers are thinking about AI tooling, hiring, or career moves right now, this has quickly become essential listening.

CoRecursive is not your typical programming podcast, and that's exactly why it stands out. Host Adam Gordon Bell takes a narrative-driven approach to software stories, treating each episode more like a mini documentary than a standard tech interview. The result is something that feels closer to Radiolab than it does to a conference talk, and it works brilliantly.

With 114 episodes and a near-perfect 4.9 rating from almost 200 reviewers on Apple Podcasts, the show has earned a devoted following. Episodes come out monthly, which means each one gets serious production attention. They typically run 40 to 50 minutes, though some shorter "field notes" episodes clock in under 10 minutes for quick takes on specific topics.

The subject matter ranges widely but always centers on the human side of building software. You'll hear about the early days of Google and how AdWords came together. There are episodes about software bugs that had real-world consequences, developers navigating mental health struggles, and the surprising stories behind viral games. A recent episode explored how AI coding agents are changing the way programmers work, told through the experiences of people actually using these tools.

What makes Adam's hosting style so effective is his ability to weave technical details into compelling narratives. He doesn't just explain what happened -- he makes you care about why it happened and what it meant for the people involved. Listeners consistently praise the storytelling quality and the way complex topics become accessible without being dumbed down. If you've ever wished programming content had the narrative depth of a good book, CoRecursive is exactly what you're looking for.

Dev Interrupted sits at the intersection of writing code and leading the people who write code, which makes it particularly valuable for programmers thinking about what comes next in their career. Produced by LinearB, the show features hosts Andrew and Ben alongside a rotating cast of engineering leaders from companies like Atlassian, Netflix, and plenty of fast-growing startups.

The format splits into two distinct flavors each week. Tuesday episodes are longer interview sessions running 30 to 50 minutes, where they sit down with CTOs, VPs of engineering, and senior developers to discuss real challenges in running engineering teams. Friday episodes are shorter industry roundups that keep you current on trends without eating up your whole commute. With 271 episodes and counting since 2020, there's a substantial back catalog to explore.

Recent topics reflect where the industry's head is at right now: multi-agent orchestration, the infrastructure strain that comes with agentic workflows, voice dictation tools for developers, and what "outcome engineering" actually means in practice. The show isn't afraid to call out buzzwords or push back on hype, which keeps it grounded.

What makes Dev Interrupted particularly useful for programmers is that it bridges the gap between individual contributor work and engineering leadership. You'll hear practical discussions about how teams ship faster, how productivity actually gets measured, and what makes some engineering organizations thrive while others struggle. The 4.8 rating from 146 reviewers on Apple Podcasts suggests the audience appreciates that balance. If you're a developer who wants to understand the bigger picture of how software organizations work -- or you're considering moving into a lead or management role -- this show gives you a serious head start.

Jonathan Cutrell started Developer Tea in 2015 with a simple premise: give software engineers short, actionable episodes they could listen to during a tea break. Over 1,300 episodes and 17 million downloads later, the formula clearly works. Episodes release twice a week and typically run 13 to 40 minutes, making this one of the most digestible engineering podcasts available.

Cutrell is an engineering leader with more than 15 years of industry experience, and his focus goes well beyond code. Recent episodes tackle how software engineers can remain relevant alongside AI, the psychology behind career stagnation at the mid-to-senior level, how the overjustification effect kills intrinsic motivation, and practical strategies for de-risking career moves through financial planning. The Career Growth Accelerator series has been particularly popular, addressing specific blockers that keep engineers from reaching staff or principal levels.

What sets Developer Tea apart from other career-focused tech podcasts is Cutrell's willingness to draw from psychology, behavioral economics, and management science rather than just recycling standard career advice. The show does not assume every listener wants to become a manager — it speaks to individual contributors who want to do meaningful work and grow on their own terms. The 4.8 star rating from over 400 reviews and the massive download numbers make it one of the most popular engineering podcasts, period.

Wes Bos and Scott Tolinski are both full-stack JavaScript developers who have been teaching web development through online courses for years, and their podcast Syntax brings that same energy to audio form. Since 2017 they have released nearly 1,000 episodes — dropping twice a week — covering everything from React and TypeScript to CSS architecture, tooling, and the business of being a developer.

The chemistry between the two hosts is a big part of why the show works. They trade off between deep-dive "Hasty Treat" episodes (shorter, focused on one topic) and longer episodes where they break down a technology, compare tools, or share lessons from their own projects. Recent coverage has included AI coding agents and editors, WebMCP standards, advanced TypeScript patterns, mobile web optimization, and browser engine developments. They are not afraid to have opinions, and they regularly update listeners when those opinions change.

With a 4.9 star rating from nearly 1,000 reviews, Syntax is one of the highest-rated and most popular web development podcasts. It skews toward front-end and full-stack JavaScript, so backend-only engineers may find some episodes less relevant, but the show regularly covers general software engineering topics like debugging workflows, testing strategies, and developer productivity. If you build things for the web, Syntax probably covers the tools you use every day.

Henry Suryawirawan hosts Tech Lead Journal for engineers who are moving, or thinking about moving, from writing code all day to leading people and shaping technical direction. Every episode is a long conversation with someone who has walked that path, usually a staff engineer, engineering manager, CTO, or author who has written a book on the subject. Guests have included names you'll recognize from the software leadership world, and the discussions are substantive, not surface level. Henry asks good follow-up questions and doesn't rush guests through their points. Topics range across architecture decisions, technical debt, team dynamics, hiring, running incident reviews, managing up, and the weird human parts of engineering that nobody teaches you in a bootcamp. The show is particularly useful if you've been promoted recently and are figuring out what your job actually is, or if you're trying to decide whether the management track or the IC track is the right move. Episodes tend to run long, often 90 minutes or more, which gives guests room to actually develop an idea instead of cramming it into a soundbite. New episodes come out roughly weekly.

Robby Russell — who also created Oh My Zsh, the wildly popular terminal framework used by millions of developers — hosts Maintainable with a focus on a question that every engineer eventually faces: how do you keep software healthy over time? Since 2019, the show has published 223 episodes featuring senior engineers, architects, and CTOs sharing how they deal with technical debt, legacy codebases, and the organizational challenges that make software hard to maintain.

The format is conversational interviews that run about 30 to 45 minutes, released every two weeks. Recent topics have included using AI for incremental maintenance rather than full rewrites, fast feedback loops and observability, database architecture decisions that pay off years later, dependency management strategies, and why code consistency is ultimately a cultural problem rather than a tooling problem. Russell's guests bring real war stories from long-running production systems, not theoretical best practices.

What makes Maintainable stand out is its narrow but deeply relevant focus. Most software podcasts celebrate the excitement of building new things, but this show tackles the less glamorous reality that most engineers spend their time working on existing systems. The show has a perfect 5.0 star rating from 32 reviews on Apple Podcasts, with listeners noting that nearly every episode maps directly to challenges they have faced in their own work. If you have ever inherited a codebase and wondered how to make it better without burning it down, this podcast is for you.

Coder Radio has been a weekly fixture in the software development podcast world since 2012, making it one of the longest-running shows in the space with nearly 590 episodes. Currently hosted by Mike, the show takes a pragmatic look at both the art and business of software development — covering not just what tools and languages engineers are using, but the industry dynamics, career realities, and business decisions that shape the profession.

The format is a weekly talk show rather than a strict interview podcast, which gives it a different energy from most engineering shows. Mike brings his own development experience to the table and riffs on current tech news, emerging tools, and industry trends. Recent episodes have featured conversations with professionals from companies like Red Hat, MongoDB, Tabnine, and Cisco, covering topics ranging from Docker and AI-powered development tools to vector databases and open-source business models.

What Coder Radio does well is treat software development as a profession with business, cultural, and economic dimensions — not just a set of technical skills. The show appeals to engineers who want to understand the bigger picture of the industry they work in. With a 4.7 star rating from 152 reviews, it has maintained a loyal audience over more than a decade. Episodes drop weekly and run about 45 to 60 minutes.

Andrew Lisowski and Justin Bennett host devtools.fm, a podcast that zeros in on the tools developers use every day and the people building them. With over 160 episodes, the show has built a solid niche by focusing specifically on developer tooling across the entire stack, from build systems and package managers to testing frameworks and design systems.

Each episode typically features a guest who is building or maintaining a notable developer tool. Recent conversations have covered React Native development, community-driven conference organizing, and the intersection of game development and web tooling. The hosts bring genuine technical curiosity and enough hands-on experience to keep conversations grounded in real-world usage rather than abstract theory.

The show also offers a paid tier that includes an extra 20 to 30 minutes of uncut interview content, which is a nice touch for listeners who want more depth. Episodes land on YouTube as well as all the usual podcast platforms, and the hosts maintain an active newsletter alongside the show. If you care about the tools that make your development workflow faster and more pleasant, or if you are building tools yourself, devtools.fm is one of the few podcasts that treats developer experience as a first-class topic worth serious discussion.

CaSE has been quietly producing thoughtful software engineering content since 2017, with 61 episodes that prioritize depth over frequency. The show is run by a small team of experienced practitioners — including Heinrich Hartmann, Sven Johann, and Alexander Heusingfeld — who alternate between discussing recent industry developments among themselves and interviewing external guests from the software engineering world.

The topics lean toward software architecture, reliability engineering, data engineering, and the organizational practices that make engineering teams effective. Recent episodes have covered architecture governance approaches (golden paths and architecture advice processes), observability costs, cloud-native testing strategies, AI-assisted development workflows, and team topology. The conversations are grounded in real experience — these are working engineers talking about problems they have actually solved, not consultants promoting frameworks.

Episodes release roughly monthly or bimonthly, which gives each one a considered, unhurried quality. The production is clean, the discussion is substantive, and the perspectives are distinctly European, which provides a welcome counterpoint to the Silicon Valley-centric view that dominates most tech podcasts. CaSE holds a perfect 5.0 star rating on Apple Podcasts, and while the review count is small, the listeners who find it tend to become devoted fans. This is a podcast for engineers who value architectural thinking and want to hear from peers who take their craft seriously.

Overcommitted comes from a crew of self-described overcommitted software engineers who juggle full-time jobs, side projects, open-source contributions, and the constant pull to learn something new. The podcast captures that experience honestly, covering the realities of software engineering careers and the tech industry from the perspective of people who are actively living it rather than looking back from executive positions.

The show tackles software engineering career insights and tech industry trends with a conversational, unpolished energy that feels like listening in on a group of experienced friends talking shop. Topics range from practical career advice and job market analysis to technical discussions about tools, frameworks, and engineering practices. The hosts share their own experiences with side projects, burnout, time management, and the tradeoffs that come with being deeply invested in multiple technical pursuits simultaneously.

Overcommitted is a newer show that launched in 2024, but it has found an audience quickly among engineers who relate to the specific challenge of having too many interests and not enough hours. The format is casual and approachable, with episodes that feel like the conversations that happen after conference talks or during late-night hackathons. If you are the kind of engineer who always has three tabs open for unrelated projects and a list of technologies you want to try, this podcast speaks your language.

Hussein Nasser has been breaking down backend engineering concepts on this show since 2018, and the depth he brings to each topic is genuinely impressive. With over 500 episodes in the catalog, he covers everything from PostgreSQL performance tuning and HTTP/2 internals to operating system page tables and kernel-level memory management. The episodes are audio versions of his popular YouTube content, so if you already watch his videos, this is the same material in a format you can absorb during a commute or workout.

What makes Hussein stand out is his ability to take dense infrastructure topics and explain them clearly without dumbing things down. He'll walk through how a database handles connection pooling, then pivot to analyzing a real cloud outage and what went wrong architecturally. Episodes run anywhere from 10 minutes for quick explainers to over an hour for deep technical walkthroughs. Most land in that 25-to-50-minute sweet spot.

The show is solo-hosted, which means you get Hussein's unfiltered take on each subject. He has strong opinions about system design tradeoffs and he's not afraid to share them. If you're a backend developer trying to understand what's actually happening under the hood of the systems you build, or you're preparing for system design interviews, this podcast delivers practical knowledge you can use immediately. The 4.9-star rating from listeners backs that up.

Quincy Larson, the founder of freeCodeCamp.org, sits down each week with developers, founders, and ambitious builders in tech for long-form conversations that regularly stretch past the hour mark. These aren't surface-level chats. Quincy has a knack for getting people to open up about their actual career paths, including the messy parts, the failures, and the lucky breaks that got them where they are.

The guest list spans a wide range -- you'll hear from self-taught developers who switched careers in their 30s, open source maintainers juggling side projects with day jobs, and engineering leaders at major companies talking about how their teams actually work. Episodes touch on AI tooling and its real impact on day-to-day development, frontend and backend practices, and the broader question of how the tech industry is shifting.

With nearly 500 ratings and a 4.9-star average, the show has built a loyal audience, especially among people who are early in their programming journey or considering a career change into tech. But it's not just for beginners. The conversations go deep enough that experienced engineers pick up useful perspectives too. Quincy's interviewing style is relaxed and curious -- he asks follow-up questions that actually matter instead of sticking to a script. If you want honest stories from people building real things in software, this is a solid weekly listen.

If you've ever wondered how to actually measure developer productivity without making your team miserable, this podcast is for you. Hosted by Abi Noda and Laura Tacho from DX, Engineering Enablement brings on engineering leaders, platform team managers, and researchers from companies like Google, Microsoft, and GitHub for in-depth interviews about what makes software teams work well.

The show has about 94 episodes, and each one runs roughly 40 minutes. That's long enough to get into real substance but short enough to finish in one sitting. Topics include developer experience metrics, platform engineering strategy, how AI is actually changing development workflows (not just hype), and the organizational patterns that separate high-performing engineering teams from struggling ones. The conversations are grounded in research and data rather than gut feelings, which is refreshing in a space full of hot takes.

Abi and Laura bring complementary perspectives -- Abi as a CEO focused on measurement and Laura as a CTO who's lived through the implementation side. They push their guests beyond generic advice into specific tactics and frameworks. You'll hear about how teams identify bottlenecks in their software delivery lifecycle, how to build a DevEx team that actually ships improvements, and why most engineering metrics miss the point. The show holds a perfect 5.0 rating, and it's earned that from listeners who care about making engineering organizations run better, not just faster.

Jack Bridger interviews the founders and leaders behind developer tools companies, and the result is one of the most practical podcasts out there for anyone building or marketing software aimed at developers. With 180 episodes and counting, Jack has talked to people from Vercel, ElevenLabs, OpenAI, and dozens of smaller startups about how they found product-market fit, acquired their first users, and scaled their go-to-market strategies.

The episodes land around 40 to 50 minutes and come out biweekly. Jack keeps things focused -- there's very little filler. You get straight into how a company approached pricing, why they chose community-led growth over traditional sales, or what their developer relations team actually does all day. It's the kind of specific, operational detail that's hard to find elsewhere.

This show sits at an interesting intersection of engineering and business. It's not purely technical, but the conversations assume you understand how developers think and what they value in tools. If you're a software engineer thinking about starting a devtools company, or you work in DevRel and want to understand how other teams approach developer marketing, these episodes will give you concrete ideas you can act on. The guests are candid about what didn't work, not just their success stories, which makes the advice much more useful. Jack's interviewing style is conversational and direct -- he asks the questions a builder would actually want answered.

Three software engineers, two at a time, talking about algorithms, data structures, programming languages, and whatever else catches their attention. That's the format of ADSP, and it works surprisingly well. Conor Hoekstra, Bryce Adelstein Lelbach, and Ben Deane rotate through hosting duties, and each pairing brings a different energy to the conversation. With 281 episodes recorded, they've built a substantial back catalog.

The show leans heavily into C++ and systems programming, but it doesn't stay in one lane. You'll hear episodes about recreational mathematics, conference trip reports, AI and machine learning developments, and broader industry commentary. Episodes typically run 25 to 45 minutes, which makes them easy to fit into a lunch break or a short drive. The tone is casual and genuinely fun -- these are friends who happen to be deeply technical people, and the conversation often takes unexpected detours that end up being the best parts.

What listeners seem to appreciate most is the mix of rigor and personality. Conor brings infectious enthusiasm about array languages and algorithm design. Bryce contributes deep C++ standards committee knowledge. Ben rounds things out with pragmatic engineering experience. They disagree with each other, go on tangents, and occasionally get nerdy about things like the mathematical properties of sorting algorithms. If you enjoy thinking about the fundamentals of computer science and want to hear smart people debate the finer points without taking themselves too seriously, ADSP is a great pick.