SRE Engagement Model Transition in Building and Expanding SRE Team
summary
SRE engagement model evolves from Launch, Specialization, Expansion to support a 400‑person org and 20 teams by building JDEP on Google Cloud with GKE, Google managed service mesh, Terraform and Kubernetes manifests, GitHub Runner CR/CD, Datadog and PagerDuty. Embedded SREs shift into two teams — a Chef COE that fixes cross‑org problems (150+ issues solved in six months) and Diplomats that execute SRE for services — then into SRE promotion using a 30‑checkpoint maturity assessment and gamedays to scale to 14 services with 8 diplomats.
AI-written summary · about
chapters (11)
- 0:00JCB and NTT Data partnership
- 2:33Digital transformation challenges
- 6:24Launching SRE at JCB
- 7:07SRE engagement model evolution
- 8:10Phase 1: Embedded SRE model
- 9:14Phase 2: Sheriff and Diplomat teams
- 11:47Phase 3: SRE promotion model
- 13:12SRE promotion standardization
- 14:38SRE maturity assessment
- 16:01Future reliability plans
- 17:29SRE engagement model summary
related talks
27mHow Google SRE and developers work together
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
25mSRE in the Third Age
32mHow Google SRE and Developers Work Together
40mHow Google SRE and developers work together
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
41mBuilding an SRE Capability Inside a Large Organization
28mEvolution of SRE and Rising Need of SRE Catalyzers
