How Google SRE and developers work together
summary
Google runs more than two billion lines of code and splits reliability and velocity by funding dedicated SRE teams that pair with devs in three engagement types: baseline, assisted, full support. SREs push automation to eliminate toil, aim to “automate themselves out of the job,” and share on‑call across continents while devs remain responsible for ownership. Success is measured with SLOs and error budgets, incident response teams and “code yellow” escalations handle major outages, and engagements regularly re‑evaluate scope.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Complexity at Google scale
- 3:54Reliability vs velocity
- 7:09SRE organization structure
- 9:20SRE engagement model
- 12:37SRE mission and value
- 17:17SRE not just Ops
- 20:08Tracking SRE success
- 23:23Standardizing solutions
- 26:55Types of SRE engagements
- 36:13Handling operational overload
- 38:01SRE principles summary
related talks
32mHow Google SRE and Developers Work Together
27mHow Google SRE and developers work together
41mAn Introduction to SRE at Google (with DevOps Focus)
05mHow do Devops and SRE relate?
22mSRE for Enterprises
18mSRE Engagement Model Transition in Building and Expanding SRE Team
25mSRE in the Third Age
08mSRE vs DevOps: The Difference & Why It Matters