Reliability Engineering: What we learnt so far
summary
Netquest runs seven engineers responsible for 90 production platforms across six Kubernetes clusters and ~100–150 autoscaling groups, supports ~70 product engineers in six dev teams, and pushes reliability goals up to near five nines where needed. Practices include SLOs/SLIs, MTTR/MTTA tracking, blameless postmortems, chaos/game days and a Terraform-first infra-as-code migration plus automation and auto-remediation experiments. Outcome: attrition drops from ~1 loss/year to a much happier platforms team, stronger developer trust, and measurable observability and incident-response improvements.
AI-written summary · about
chapters (9)
- 0:00Introduction to SRE journey
- 3:34Defining SRE goals and metrics
- 7:12Cultural pillars for SRE success
- 10:27Building trust and feedback loops
- 13:01T-shaped expertise and team structure
- 15:10Anti-fragility in teams and systems
- 18:01Formula for effective SRE implementation
- 20:31Future roadmap and improvements
- 22:00Q&A session
related talks
55mA Decade of Progress: The Evolution of Production Engineering and Reliability
29mThe Curious SRE: Cultivating a Mindset for System Resilience
20mBuilding a Culture of Reliability
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
34mReliability and Engineering Requirements
35mThe Best SREs Seem to Be the Ones without an SRE Title—And What We Can Do
07mIGNITE: Metrics, Margins, Mutiny – How to make your SREs (not) run away
27mThe Perverse Incentives of Reliability