Role Pack · Mid to Senior
SRE Reliability Engineering Pack
SLOs, error budgets, incident response, capacity and the reliability engineering mindset.
The SRE-specific loop: SLO design, on-call, incident command, capacity planning and reliability culture.
- Questions
- 360
- Topics
- 20
- Pages
- 248pages
- 360 questions, every one with a model answer
- SLO & error-budget lab
- Incident command playbook
- Capacity planning math
- Reliability culture questions
Get the SRE Reliability Engineering Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- SLIs, SLOs and SLAs
- Choosing measurement that matters
- Error budgets and burn rate
- Releasing under an error budget policy
- Toil and its hidden cost
- Toil reduction and infrastructure automation
- Alerting that pages a human
- On-call rotations, handover and sustainability
- Incident response and incident command
- Incident communication and stakeholder updates
- Postmortems without blame
- Turning postmortem action items into work
- Capacity forecasting and headroom
- Change management and release safety
- Runbooks and operational readiness
- Multi-region resilience
- Dependency failure and cascading failure
- Chaos engineering and resilience testing
- Reliability culture and the SRE role
- Load testing and performance engineering
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- An SLI is a measurement, an SLO is a target over a window, and an SLA is a contractual promise with consequences.
- Instrument the user-visible boundary, not every internal function, or the dashboard becomes unreadable.
- The error budget is the allowed bad events in the window: total requests multiplied by the failure allowance.
- A budget policy is a pre-agreed rule, so the freeze decision is made before the incident and is not argued during it.
- Toil is manual, repetitive, automatable and of no lasting value; all four must hold for something to count as toil.
- Automate the trigger as well as the fix, or the alert still reaches a human every time.
Questions this pack covers
- How do you tell an SLI apart from an SLO?
- Why does an SLA usually differ from the internal SLO?
- Where do you draw the boundary for instrumentation?
- How do you keep metric cardinality under control?
- How do you compute an error budget from an SLO?
- What does a burn rate of 14 mean operationally?
- What exactly does a feature freeze block?
- Who is allowed to grant a freeze exception?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 248 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
