Balancing autonomy, technical alignment, & speed through strategic collaboration
summary
Concrete claims and operational details: Spotify runs ~25 Technical Steering Groups and maintains 100+ ADRs; Core Infrastructure TSG acts as a virtual tech lead for ~100 engineers across 10 squads, owning backend dev experience for ~900 engineers and handling 1.3 trillion events/day, 3,600 microservices, ~4,000 deployments/day, 1.5M Kubernetes pods and ~10M requests/s. Processes include weekly standups, weekly deep dives, short 1–2 month workstreams, transparency of outcomes, exercises like a cold-start workshop, and ongoing monorepo onboarding of thousands of components.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:06Building ownership
- 2:50Spotify’s engineering culture
- 3:51Driving alignment
- 8:24Reforming tech steering
- 13:00Key principles
- 16:32Long-term planning
- 19:23Retrospectives
- 20:48Steering group examples
- 26:31Closing
related talks
40mScaling code health with always on rewrites and AI at Spotify
27mShifting Spotify Engineering from Spreadsheets to Backstage
49mMicroservices at Spotify
19mHigh Performance Backstage for High Performing Organizations
20mSpotify's Growth Exposed the Abstraction Paradox
23mScaling the Sound: Fleet Management at Spotify
24mScaling the Stage: Managing 200+ Plugins & Thousands of Engineers
46mModelling Microservices at Spotify