Interview preparation guide
SRE Interview Questions With Reliability Scenarios
Practice SRE interview questions by explaining the model, working through a small problem and checking failure cases. These original exercises test reasoning rather than recall of a claimed employer question list.
Scope and assumptions
The exercise uses a request-based availability SLO with a fixed evaluation window. It is distinct from a time-based uptime calculation, and it does not describe a particular employer’s policy.
Confirm the version, deployment model and permissions in the interview. The examples use fictional data and are deliberately small. A snippet demonstrates one idea; it is not a complete production system.
How do an SLI and an SLO differ?
An SLI is a defined service indicator, such as the fraction of valid requests meeting a success condition. An SLO sets the target for that indicator over a period. Define the denominator and exclusions explicitly.
What is an error budget?
It is the allowed unreliability implied by the chosen objective and window. It supports decisions about reliability and change, but it is useful only when the indicator reflects the user experience that matters.
What makes a useful incident response?
Clear roles, impact assessment, communication and safe mitigation matter. Preserve evidence and avoid several uncoordinated changes. A postmortem should explain contributing conditions and useful follow-up actions.
When is automation worth building?
Consider repetition, risk and maintenance cost. Automate a well-understood process with observable outcomes and a recovery path. Unattended automation can amplify a poorly understood failure.
Worked exercise
A service handles 2,000,000 eligible requests in a window. Its success-rate SLO is 99.9%, and 1,500 requests fail. Calculate the allowed failures and remaining budget.
Allowed failures = 2,000,000 * (1 - 0.999) = 2,000
Observed failures = 1,500
Remaining budget = 500 failures
Budget consumed = 1,500 / 2,000 = 75%Expected result and explanation
The service has used 75% of the request-based error budget, leaving 500 failures for the stated window. This is not 500 minutes of downtime. A practical alert policy also needs the rate of consumption and a precise definition of eligible and successful requests.
Before changing the example, predict the result. Then vary one input or constraint and explain why the behavior should change. Keep the distinction between a measured result and an assumption clear.
Debugging and follow-up
If a dashboard shows healthy infrastructure while users report failures, inspect the indicator’s coverage. A server-up check may miss a broken user journey or a failing dependency.
- What evidence would distinguish your first explanation from an alternative?
- Which boundary, permission or failure case should be checked?
- How would you reproduce the issue without affecting live users?
Practice checklist
Explain one design decision aloud and support it with the worked example. Use the official documentation below to check version-specific behavior.
- I stated the relevant version and environment.
- I can explain the expected result and an edge case.
- I can separate correctness, performance and security concerns.
- I know which parts require a real runtime or service to verify.
Questions, answered
Are these questions used by a particular employer?
No. They are original practice questions. Employers can assess different tools, versions and levels of depth.
How should I verify the exercise?
Use an isolated local or sandbox environment with the stated prerequisites. Compare the expected result, then test an edge case. Do not run service commands against a shared or production system.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.