How Netflix Scaled Developer Velocity

This episode explores the specific architectural decisions that allowed Netflix to scale its engineering organization without collapsing under its own complexity. We look at how they replaced rigid microservice boundaries with fluid domain ownership, implemented chaos engineering not just for resilience but for developer confidence, and why they stopped measuring code churn in favor of deployment frequency. The conversation centers on the trade-offs between autonomy and consistency, using Netflix as a case study for sustainable growth. Listeners will learn one concrete thing: how to structure teams around business outcomes rather than technical layers, and why monitoring system health is actually a proxy for team morale. #SoftwareEngineering #Netflix #Microservices #DevOps #EngineeringCulture #ChaosEngineering #TechLeadership #SystemDesign #Scalability #DeveloperExperience #CloudNative #AgileAtScale #FexingoBusiness #BusinessPodcast #TechTrends2026 #EngineeringBestPractices #CodeArchitecture #TechManagement Keep every episode free: buymeacoffee.com/fexingo