Brought to You By: •⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more. Statsig enables two cultures at once: continuous shipping and experimentation. Companies like Notion went from single-digit experiments per quarter to over 300 experiments with Statsig. Start using Statsig with a generous free tier, and a $50K startup program. •⁠ Linear ⁠ — ⁠ The system for modern product development. When most companies hit real scale, they start to slow down, and are faced with “process debt.” This often hits software engineers the most. Companies switch to Linear to hit a hard reset on this process debt – ones like Scale cut their bug resolution in half after the switch. Check out Linear’s migration guide for details. — What’s it like to work as a software engineer inside one of the world’s biggest streaming companies? In this special episode recorded at Netflix’s headquarters in Los Gatos, I sit down with Elizabeth Stone, Netflix’s Chief Technology Officer. Before becoming CTO, Elizabeth led data and insights at Netflix and was VP of Science at Lyft. She brings a rare mix of technical depth, product thinking, and people leadership. We discuss what it means to be “unusually responsible” at Netflix, how engineers make decisions without layers of approval, and how the company balances autonomy with guardrails for high-stakes projects like Netflix Live. Elizabeth shares how teams self-reflect and learn from outages and failures, why Netflix doesn’t do formal performance reviews, and what new grads bring to a company known for hiring experienced engineers. This episode offers a rare inside look at how Netflix engineers build, learn, and lead at a global scale. — Timestamps (00:00) Intro (01:44) The scale of Netflix  (03:31) Production software stack (05:20) Engineering challenges in production (06:38) How the Open Connect delivery network works (08:30) From pitch to play  (11:31) How Netflix enables engineers to make decisions  (13:26) Building Netflix Live for global sports (16:25) Learnings from Paul vs. Tyson for NFL Live (17:47) Inside the control room  (20:35) What being unusually responsible looks like (24:15) Balancing team autonomy with guardrails for Live (30:55) The high talent bar and introduction of levels at Netflix (36:01) The Keeper Test   (41:27) Why engineers leave or stay  (44:27) How AI tools are used at Netflix (47:54) AI’s highest-impact use cases (50:20) What new grads add and why senior talent still matters (53:25) Open source at Netflix  (57:07) Elizabeth’s parting advice for new engineers to succeed at Netflix  — The Pragmatic Engineer deepdives relevant for this episode: • The end of the senior-only level at Netflix • Netflix revamps its compensation philosophy • Live streaming at world-record scale with Ashutosh Agrawal • Shipping to production • What is good software architecture? — Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [email protected].

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

Supported by Our Partners • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half • Augment Code — AI coding assistant that pro engineering teams love — How do you architect a live streaming system to deal with more load than it’s ever been done before? Today, we hear from an architect of such a system: Ashutosh Agrawal, formerly Chief Architect of JioCinema (and currently Staff Software Engineer at Google DeepMind.) We take a deep dive into video streaming architecture, tackling the complexities of live streaming at scale (at tens of millions of parallel streams) and the challenges engineers face in delivering seamless experiences. We talk about the following topics:  • How large-scale live streaming architectures are designed • Tradeoffs in optimizing performance • Early warning signs of streaming failures and how to detect them • Why capacity planning for streaming is SO difficult • The technical hurdles of streaming in APAC regions • Why Ashutosh hates APMs (Application Performance Management systems) • Ashutosh’s advice for those looking to improve their systems design expertise • And much more! — Timestamps (00:00) Intro (01:28) The world record-breaking live stream and how support works with live events (05:57) An overview of streaming architecture (21:48) The differences between internet streaming and traditional television.l (22:26) How adaptive bitrate streaming works (25:30) How throttling works on the mobile tower side  (27:46) Leading indicators of streaming problems and the data visualization needed (31:03) How metrics are set  (33:38) Best practices for capacity planning  (35:50) Which resources are planned for in capacity planning  (37:10) How streaming services plan for future live events with vendors (41:01) APAC specific challenges (44:48) Horizontal scaling vs. vertical scaling  (46:10) Why auto-scaling doesn’t work (47:30) Concurrency: the golden metric to scale against (48:17) User journeys that cause problems  (49:59) Recommendations for learning more about video streaming  (51:11) How Ashutosh learned on the job (55:21) Advice for engineers who would like to get better at systems (1:00:10) Rapid fire round — The Pragmatic Engineer deepdives relevant for this episode: • Software architect archetypes https://newsletter.pragmaticengineer.com/p/software-architect-archetypes  • Engineering leadership skill set overlaps https://newsletter.pragmaticengineer.com/p/engineering-leadership-skillset-overlaps  • Software architecture with Grady Booch https://newsletter.pragmaticengineer.com/p/software-architecture-with-grady-booch — See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠ — Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [email protected].

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

Supported by Our Partners • WorkOS — The modern identity platform for B2B SaaS • CodeRabbit — Cut code review time and bugs in half • Augment Code — AI coding assistant that pro engineering teams love — How do you architect a live streaming system to deal with more load than it’s ever been done before? Today, we hear from an architect of such a system: Ashutosh Agrawal, formerly Chief Architect of JioCinema (and currently Staff Software Engineer at Google DeepMind.) We take a deep dive into video streaming architecture, tackling the complexities of live streaming at scale (at tens of millions of parallel streams) and the challenges engineers face in delivering seamless experiences. We talk about the following topics:  • How large-scale live streaming architectures are designed • Tradeoffs in optimizing performance • Early warning signs of streaming failures and how to detect them • Why capacity planning for streaming is SO difficult • The technical hurdles of streaming in APAC regions • Why Ashutosh hates APMs (Application Performance Management systems) • Ashutosh’s advice for those looking to improve their systems design expertise • And much more! — Timestamps (00:00) Intro (01:28) The world record-breaking live stream and how support works with live events (05:57) An overview of streaming architecture (21:48) The differences between internet streaming and traditional television.l (22:26) How adaptive bitrate streaming works (25:30) How throttling works on the mobile tower side  (27:46) Leading indicators of streaming problems and the data visualization needed (31:03) How metrics are set  (33:38) Best practices for capacity planning  (35:50) Which resources are planned for in capacity planning  (37:10) How streaming services plan for future live events with vendors (41:01) APAC specific challenges (44:48) Horizontal scaling vs. vertical scaling  (46:10) Why auto-scaling doesn’t work (47:30) Concurrency: the golden metric to scale against (48:17) User journeys that cause problems  (49:59) Recommendations for learning more about video streaming  (51:11) How Ashutosh learned on the job (55:21) Advice for engineers who would like to get better at systems (1:00:10) Rapid fire round — The Pragmatic Engineer deepdives relevant for this episode: • Software architect archetypes https://newsletter.pragmaticengineer.com/p/software-architect-archetypes  • Engineering leadership skill set overlaps https://newsletter.pragmaticengineer.com/p/engineering-leadership-skillset-overlaps  • Software architecture with Grady Booch https://newsletter.pragmaticengineer.com/p/software-architecture-with-grady-booch — See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠ — Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [email protected].

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe