Software engineering at Big Tech and startups, from the inside. Deepdives with experienced engineers and tech professionals who share their hard-earned lessons, interesting stories and advice they have on building software.
Especially relevant for software engineers and engineering leaders: useful for those working in tech.
Software factories and code reviews with Harjot Gill
Wednesday, November 18, 2026 • Duration 01:26:37
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Entire – The Git forge for agent-human collaboration. Built for the scale and throughput of agentic coding.
• WorkOS – everything you need to make your app enterprise-ready.
—
In this conversation, we step into the world of an AI-pilled CEO to explore how their startup works. This episode might as well be a way of succeeding that contradicts the growing convention that AI spending costs are too high and must be clamped down on.
Harjot Gill is founder and CEO of CodeRabbit, an AI code review business, and he shipped over 5,000 pull requests last month, spending on AI at a monthly run rate of $250,000(!) It’s certainly not a conventional approach and Harjot gets into detail about the thinking and reasoning behind it.
In this episode of The Pragmatic Engineer Podcast, we talk about his background in building software and founding infra startups for the last 30 years, and how things changed into the era of building software factories at CodeRabbit. We talk about why he believes human code review is dead, and how his team maintains quality while shipping at unprecedented speed.
We also get into the rising costs of AI development, why Harjot is convinced that tech startups need more funding than ever, and how AI is changing recruitment and the skills for success.
Timestamps
00:00 Intro
03:17 How Harjot shipped over 5,000 pull requests in a month
08:46 Harjot’s path into tech and his first startups
12:25 Early conviction around AI and founding CodeRabbit
14:40 Switching to AI coding
20:35 Software factories explained
25:37 What’s replacing human code review
38:44 Technical debt and deslopping tests
46:05 Evals
50:25 Formal methods
52:05 AI cost at CodeRabbit
54:57 Startup funding in 2026 and the value of AI spend
1:08:20 Hiring
1:13:03 Work pace, sleep, and burnout
1:21:55 Skills for the AI era
1:24:30 Book recommendation
—
The Pragmatic Engineer deepdives relevant for this episode:
Software engineering after code becomes cheap with Satya Nadella
Monday, November 16, 2026 • Duration 01:02:40
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Linear – the product development system for teams and agents.
• WorkOS – everything you need to make your app enterprise ready.
—
What does software engineering look like when generating code becomes cheap, and verifying it becomes the hard part?
Today’s guest is Satya Nadella, Microsoft’s CEO, who is one of the very few Big Tech CEOs who started his career as a software engineer (back at Sun Microsystems). He joins me to discuss how building software is changing inside Microsoft, and what these changes mean for engineers.
We start with Microsoft’s embrace of open source and the lessons from building VS Code in the open. I also ask how Microsoft went from an early lead with GitHub Copilot to catching up with Cursor and Claude Code, and what this reveals about building products around rapidly improving models.
Satya explains what a “software factory” means to him, why specifications and verification are becoming more important, and how teams working on existing products like Windows are adapting. We discuss Microsoft’s voluntary exit offers, the anxiety around AI and engineering careers, and why he cautions against drawing long-term conclusions from the slowdown in junior hiring.
We also explore open and local models, why companies need to control their own AI infrastructure, and how to build safeguards around increasingly capable agents. Satya closes with advice for engineers who want to excel through this change, and why he’d like to spend more time building himself.
Sidenote: we recorded this episode, in Redmond, a few hours before Microsoft’s day-long Outlook outage started: and so there was no way we could have touched on that topic - but expect for me to follow up on that massive outage in a future The Pragmatic Engineer episode.
Get full access to The Pragmatic Engineer at
Scaling Slack and GitHub with Maude Lemaire
Thursday, November 5, 2026 • Duration 01:18:33
Brought to You By:
• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Entire – The Git forge for agent-human collaboration. Built for the scale and throughput of agentic coding.
—
What is involved in scaling up large, popular products at places like Slack and GitHub?
We get an insider’s view on this from Maude Lemaire, a principal engineer and author of ‘Refactoring at Scale: Regaining Control of Your Codebase.’ She spent nearly eight years at Slack, where she led the backend performance infrastructure team, before joining GitHub to tackle database scaling challenges. Most recently, she worked on improving performance at Cursor – including time to first token.
In this episode of The Pragmatic Engineer, Maude and I dig into the challenges of scaling some of the world's largest software products. We explore how Slack handled growing numbers of enterprise customers, how it evolved its approach to load testing, and the lessons Maude learned during nearly eight years of scaling Slack's infrastructure.
She also tells us what it was like joining GitHub in 2024 when Copilot was taking off, the challenges of working with GitHub's gigantic Rails monolith, and how Maude uses AI in her work – while keeping judgment calls and decision-making firmly in her own hands.
Get full access to The Pragmatic Engineer at
Software engineering at Google & CS education with Titus Winters
Thursday, October 29, 2026 • Duration 01:40:12
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable
• Linear – the product development system for teams and agents
• WorkOS – everything you need to make your app enterprise ready.
—
An engineer who helped create today’s software engineering curriculum now says to burn down almost all of it. What’s the cause of this contradiction? We find out from the lead author of Software Engineering at Google.
Titus Winters spent more than a decade at Google, where he led its readability program and built Abseil, Google’s open-sourced foundational C++ libraries. He is currently a Senior Principal Scientist at Adobe, where he focuses on developer experience and productivity.
In this episode of The Pragmatic Engineer podcast, Titus and I discuss how his team tackled a massive refactoring project across Google's 250-million-line C++ codebase, why Google made testing mandatory, and his work on updating the ACM/IEEE undergraduate computer science curriculum guidelines.
We also explore why traditional productivity metrics miss some of AI’s biggest benefits, what needs to change in CS education, and how new engineers can stand out.
Timestamps
00:00 Intro
07:01 Getting hired by Google
Get full access to The Pragmatic Engineer at
The revised rules of engineering management with Will Larson
Wednesday, October 21, 2026 • Duration 01:55:34
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Entire – Git hosting, rebuilt for the agentic era. Every agent session, prompt and tool calls: stored in your repo.
• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
—
What’s changed in “the unwritten rules” of engineering management since the 2010s, what drove the shift to today, and what has it done to the engineer-to-CTO career path? Today’s guest is one of the best people I know who can tackle these questions.
In this episode, we explore how engineering leadership has evolved from management practices shaped in the long post-financial-crisis ZIRP era to the altered expectations of engineers and managers today.
Get full access to The Pragmatic Engineer at
Uber’s AI infra, from the inside
Wednesday, October 14, 2026 • Duration 01:33:18
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable
• Linear – the product development system for teams and agents
• WorkOS – everything you need to make your app enterprise-ready.
—
What do developer tools look like inside of Uber, today? They are very different from what you would see at most places. For example, can you guess what service a system called DevPods, Code Inbox, Slate or Wisdom would be providing to engineers?
Today’s episode is a deepdive into the day-to-day tools of devs at Uber, our tour guide being on of Uber’s longest-tenured engineers: Uday Kiran Medisetty. Uday is one of the few Distinguished Engineers at the company, and leads much of the work on agentic AI, today.
With Uday, we talk through how Uber’s developer infrastructure prepared it for AI agents. We look at the systems Uber built before generative AI and the new tools that connect agents to its code, internal services, and engineering knowledge. Uday explains how engineers use background agents, why tools like Slate make development (and bugfixing!) more efficient, and how code review is changing. We also cover Uber’s approach to token costs and how it measures productivity as the engineer’s role changes.
Timestamps
00:00 Intro
02:48 Uday’s early days at Uber
05:40 Uber’s move to microservices
07:55 Uber’s engineering team, then and now
09:05 Developer tooling before AI
Get full access to The Pragmatic Engineer at
Building resilient systems with Sam Newman
Wednesday, October 7, 2026 • Duration 01:58:22
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Entire – Git hosting, rebuilt for the agentic era. Every agent session, prompt and tool calls: stored in your repo.
• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
—
Sam Newman wrote one of the most-read books about microservices (“Building Microservices”), but he calls them an architecture of “last resort.”
In this episode of the Pragmatic Engineer podcast, Sam explains his thinking on this, and he’s certainly well placed to do so; he was in the room when the term “microservices” was coined. We discuss what teams get wrong when adopting microservices, why independent deployment matters, and how microservices can help teams work more autonomously.
We also delve into his new book, ‘Building Resilient Distributed Systems’, and Sam explains his three rules for distributed systems, why observability is essential, and also why it’s vital to take business context into account when deciding whether to fail open or fail closed on errors.
We also explore how AI is changing software development, from specs versus code as a source of truth to cognitive debt and cognitive surrender. Sam shares how modular architecture can help teams experiment with AI while maintaining understanding of the systems being built.
Timestamps
Get full access to The Pragmatic Engineer at
Distributed databases with Peter Mattis
Wednesday, September 30, 2026 • Duration 01:41:49
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable
• Linear – the product development system for teams and agents
• WorkOS – everything you need to make your app enterprise ready.
—
How is it that a software veteran who regularly shipped ~100K of database-grade code to production each year, pre-AI, feels like he’s even more productive today, with no drop in quality? Peter Mattis is co-founder and CTO of Cockroach Labs, and an original creator of GIMP. He also worked on Gmail and distributed storage at Google.
In this episode, Peter reflects on his journey from open source to Google to founding a database company, and we explore how to keep systems fast, reliable, and correct at scale, from Gmail’s early storage challenges to the tradeoffs in building distributed databases.
Peter tells us how AI has brought him back to writing code after his work shifted toward management, and why he believes AI can improve quality and multiply the impact of domain experts. We also consider the future of code review, and Peter has some advice about how to level up our engineering skills.
Timestamps
00:00 Intro
02:42 Peter’s path into tech
04:00 Building GIMP
09:30 Working on Gmail at Google
14:51 Google’s infra: google3, build files, Bazel, and Colossus
Get full access to The Pragmatic Engineer at
Design Engineering with Maggie Appleton
Wednesday, September 23, 2026 • Duration 01:27:23
Brought to You By:
• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• Entire – every agent prompt, tool call, stored in your repo, and mirrored.
—
What can everyone else learn from designers and design engineers? As it turns out, there’s plenty, as I discovered when one of the best design engineers in the industry, Maggie Appleton, came onto the Pragmatic Engineer Podcast. She’s a staff research engineer at GitHub Next, where she builds prototypes to explore how software engineers might collaborate with AI in new ways. Maggie is at the intersection of design, anthropology, and web development, and was the first designer hired by AI startup Elicit, and Lead Design engineer at AI startup, Normally.
Today’s episode is more visual than usual because Maggie brought her notebook along, so there are peeks inside its pages of prototypes and more:
We got into designers’ work and how their design processes are adapting to and changing with AI. We explore why Maggie starts projects with pens and notebooks, what distinguishes design engineers from other designers, and why understanding engineering constraints leads to better collaboration with engineers.
We also discuss how Maggie uses jigs to gain more control over AI agents, why human judgment and style still matter when models can generate designs, and how inconsistent AI capabilities can mislead us.
Get full access to The Pragmatic Engineer at
AI Skills with Matt Pocock
Thursday, September 17, 2026 • Duration 01:35:31
Brought to You By:
• turbopuffer– a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable
• Linear – the product development system for teams and agents
• WorkOS – everything you need to make your app enterprise ready.
—
Why is the “grill-me” skill so popular, and why does its creator swear by the importance of software fundamentals? Matt Pocock created this widely-used skill – and many others – alongside being an educator, content creator, and engineer. His latest course is AI Hero, and he previously created the Total TypeScript course that generated more than $2.5 million in sales.
In this episode, Matt and I discuss his unconventional path from working as a voice teacher to becoming a developer and going all-in on technical education. He reveals how communication skills helped him break into tech, why he took an unusual three-days-a-week contract at Vercel, and how he built Total TypeScript through workshops, courses, and a lot of free content.
We also explore “strategic coding,” and how he uses skills like “grill me” and “wayfinder” to plan, delegate, and course-correct with AI agents. Matt explains his “day shift” and “night shift” approach, why splitting context up can keep agents in their “smart zone,” and how concepts from classic software engineering books can guide agents to do better. In this episode, there’s also local versus cloud workflows, whether agents need TDD, how AI is changing the ways that engineers learn the fundamentals, and why humans are still essential in teaching.
Get full access to The Pragmatic Engineer at
Timestamps
00:00 Intro
02:12 Microsoft’s open-source shift
04:15 Building VS Code in the open
05:55 Copilot, Cursor, and Claude Code
09:52 Decision engines
12:32 Verifying AI-generated code
15:39 The software factory
20:45 Bringing AI to existing products
24:06 Why adopting AI is different to adopting React
26:29 The changing role of software engineers
29:25 Microsoft’s voluntary exit offers
34:05 AI anxiety and changing roles
36:35 Junior hiring
42:36 Open models
45:39 Owning your AI infrastructure
51:21 Building trust in AI agents
53:48 Local models and hybrid intelligence
56:39 Microsoft’s model strategy
59:26 Advice for engineers
1:01:21 Closing takeaways
—
The Pragmatic Engineer deepdives relevant for this episode:
Is middle management an increasingly precarious career path, and might managers need to reskill and return to hands-on technical work – or even consider retirement? Will makes the case, and we hear why the traditional path to engineering executive roles is changing, as well as why taking one step backward might sometimes be the best way forward.
We discuss Will's early career, and get his first-hand account of Digg's disastrous relaunch, his own path to CTO, and he tells us why career ladders still matter. We also explore how AI is changing engineering roles and bringing technical decision-making back to leadership.
Timestamps
00:00 Intro
08:20 Stories from Yahoo!
12:47 Digg’s v4 rewrite: the insider story
26:02 Will’s path to eng leadership
30:03 Uber, Stripe, Carta, and Calm
35:11 What does a CTO do?
38:09 Will’s role at Imprint
42:48 How engineering management has evolved
51:08 ZIRP’s impact on tech
57:21 Career ladders
1:01:03 Eng 1 vs Eng 2
1:06:58 How software engineering roles are changing
1:16:25 Revised rules of engineering leadership
1:21:57 The risks of becoming a bureaucrat as an EM
1:25:57 How to become a CTO?
1:31:33 Middle management vs. line management
1:41:36 Will’s writing
1:52:13 Book recommendations
—
The Pragmatic Engineer deepdives relevant for this episode:
Discover shows related to The Pragmatic Engineer, based on actual content similarities. Explore podcasts with similar topics, themes, and formats, backed by real data.