Observability & reliability
SRE & incident management
Senior DevOps roles are increasingly "DevOps/SRE" in practice: you're expected to define reliability targets, run on-call, lead incidents, write blameless postmortems, plan capacity and reduce toil. Interviewers ask behavioural questions ("tell me about an outage you handled") alongside concepts like SLOs, error budgets and burn-rate alerting. This topic gives you the vocabulary, the maths and the structure for strong answers.
After this topic you can
- Define SLIs, SLOs and error budgets
- Run an incident as commander and write a blameless postmortem
- Reduce toil and noisy alerts
Lessons
-
1Reliability language: SLIs, SLOs, SLAs
- Definitions
- Choosing good SLIs
- Availability nines
-
2Error budgets and policies
- Using the budget
- Burn rate
-
3Incident management
- Severity levels
- Roles (ICS-style)
- The incident lifecycle
- Metrics for incident response
-
4Postmortems and learning
- Blameless postmortems
- Example root-cause chain (5 whys)
-
5On-call, toil and operational excellence
- Sustainable on-call
- Runbooks
- Toil
-
6Designing for reliability
- Resilience patterns
- Safe change management
- Capacity planning and load testing
- Chaos engineering
-
7Interview questions and model answers
- "What's the difference between SLI, SLO and SLA?"
- "How would you alert on an SLO?"
- "Walk me through how you handle a major incident."
- "Tell me about an outage you handled." (structure)
- "What's an error budget policy and how do you get product to agree?"
- "How do you reduce toil?"
- "Why are retries dangerous?"
- "How do you prepare for a big sale day?"