Definitions, differences, simple examples, basic workflow, and common mistakes.

A clear 90-second answer

Say this first: SRE principles should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply SRE principles, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: SLI SLO SLA is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply SLI SLO SLA, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Choose the option that fits the workload and constraints; do not present one option as universally superior.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: An SLO is a reliability target for a user-visible service. Its error budget is the amount of unreliability allowed before reliability work takes priority over further change.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply error budget, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: “toil reduction is the part of the system that helps us deliver the intended outcome safely and predictably. I would explain it using a small customer scenario, then show the check that proves it worked.”

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply toil reduction, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about observability pillars is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply observability pillars, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: golden signals should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply golden signals, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: alert design is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply alert design, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Choose the option that fits the workload and constraints; do not present one option as universally superior.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: incident response should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply incident response, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: “postmortem culture is the part of the system that helps us deliver the intended outcome safely and predictably. I would explain it using a small customer scenario, then show the check that proves it worked.”

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply postmortem culture, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about on-call readiness is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply on-call readiness, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: capacity planning should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply capacity planning, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: load shedding is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply load shedding, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Choose the option that fits the workload and constraints; do not present one option as universally superior.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: rate limiting should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply rate limiting, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: “circuit breaker is the part of the system that helps us deliver the intended outcome safely and predictably. I would explain it using a small customer scenario, then show the check that proves it worked.”

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply circuit breaker, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about graceful degradation is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply graceful degradation, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about Kubernetes troubleshooting is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply Kubernetes troubleshooting, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Concrete check

kubectl rollout status deployment/<service> --timeout=90s

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: latency debugging is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply latency debugging, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Choose the option that fits the workload and constraints; do not present one option as universally superior.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: availability design should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply availability design, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

request or change → guardrail / validation → availability design → observable result → owner review

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: “DR and failover is the part of the system that helps us deliver the intended outcome safely and predictably. I would explain it using a small customer scenario, then show the check that proves it worked.”

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply DR and failover, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about automation for reliability is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply automation for reliability, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: release risk management should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply release risk management, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: chaos engineering is a choice between approaches with different strengths. The useful answer is the decision rule, not a dictionary definition.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply chaos engineering, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Choose the option that fits the workload and constraints; do not present one option as universally superior.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: runbooks should be explained through its purpose, the boundary where it applies, and the evidence that shows it is working.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply runbooks, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: “service ownership is the part of the system that helps us deliver the intended outcome safely and predictably. I would explain it using a small customer scenario, then show the check that proves it worked.”

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply service ownership, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• State the constraint that could change your decision, such as scale, data sensitivity, recovery target, or team ownership.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.

A clear 90-second answer

Say this first: The important point about reliability governance is how an engineer recognizes the unsafe path early and prevents it from becoming customer impact.

Use a real scenario

Imagine a customer-facing API that must survive a regional dependency failure. The team must decide how to apply reliability governance, verify the result, and explain the user impact. For a Site Reliability Engineer, attach the explanation to a runbook and recovery test result.

Show judgment

• name the concept, give one concrete use, and say how you would check the result.
• Start with containment and evidence. Changing several variables at once makes the incident harder to understand.
• Call out a broad outage or an untested recovery path and the control that reduces it.

Evidence to mention

Track availability, recovery time, and cost per request. Say what baseline you compared against, what would trigger a rollback or escalation, and who owns the follow-up.

Practice prompt: Keep the scope small. Do not claim production ownership you have not had.