The Production Engineering Lifecycle: How We Build, Run, and Disband Great...
summary
Facebook describes a deliberate lifecycle: hire production engineers as strong coders with systems experience and vet them in software-engineer coding interviews, place them based on a 10:1 developer-to-production-engineer ratio and a three‑stage maturity model (bootstrap, scale, awesomize), prioritize work with a service pyramid priority, choose advisory/consulting/full engagement levels, co‑locate teams when possible, use three on‑call models (mixed up to ~12, separate for scale, or refuse on‑call until supportable) and run examples like five concurrent cache rotations and centralized auto‑remediation and deployment tooling.
AI-written summary · about
chapters (27)
- 0:00Intro
- 1:00What is Production Engineering
- 4:05Facebook Software Engineering Requirements
- 5:15Facebook Operating Environment
- 5:58Facebook Production Engineering Ratio
- 7:11Early Production Engineering Teams
- 8:57Production Engineers
- 10:00The Big Fat No
- 10:57Step 1 Skill Set
- 12:38Step 2 Understand the Service
- 14:53Step 3 Level of Engagement
- 16:15Assigning the Most Suitable Engineers
- 16:49Sitting the Engineers and Developers Together
- 17:45Splitting Tasks and OnCall Work
- 18:17Maslows Hierarchy of Needs
- 19:12Service Pyramid
- 19:43Security
- 20:50OnCall
- 21:47OnCall Load
- 22:38Mixed Rotation
- 24:25Separate Rotations
- 26:20Dont Be On Call
- 27:41Integration Challenges
- 28:58Disbanding Teams
- 29:56Things We Failed
- 31:32Successes
- 33:25Skill Set Assessment
related talks
28mFrom Startup to Scale Up: How to Scale Engineering teams
23mBuild & Manage Engineering Team
16mEnlarge your team!
32mStarting and Scaling a Platform Engineering Team
26mScaling engineering organizations
30mHow we built a Product Engineering culture at Great Expectations
55mA Decade of Progress: The Evolution of Production Engineering and Reliability
43mEngineering Platforms Evolved