Opscraft
Observability & reliability

SRE & incident management

New7 lessons · 25 min · 3 tests ·

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.

Stage 4 · Senior skills

Know these first

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

  1. 1Reliability language: SLIs, SLOs, SLAs 4 min read
    • Definitions
    • Choosing good SLIs
    • Availability nines
  2. 2Error budgets and policies 3 min read
    • Using the budget
    • Burn rate
  3. 3Incident management 4 min read
    • Severity levels
    • Roles (ICS-style)
    • The incident lifecycle
    • Metrics for incident response
  4. 4Postmortems and learning 3 min read
    • Blameless postmortems
    • Example root-cause chain (5 whys)
  5. 5On-call, toil and operational excellence 3 min read
    • Sustainable on-call
    • Runbooks
    • Toil
  6. 6Designing for reliability 4 min read
    • Resilience patterns
    • Safe change management
    • Capacity planning and load testing
    • Chaos engineering
  7. 7Interview questions and model answers 4 min read
    • "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?"