On-Call Practices and Runbook Design Questions

Running a sustainable on-call function: rotation design, production-readiness handoffs, and authoring runbooks that let responders act quickly. Covers runbook automation, on-call culture, escalation-ready documentation, and readiness reviews before a service takes production traffic. The operational-preparedness discipline that makes incidents survivable.

HardBehavioral
49 practiced

During a postmortem, the incident commander singles out one engineer as the cause of the outage. How do you respond in the moment to preserve a blameless culture, without letting accountability for the fix slide?

EasyTechnical
89 practiced

How do you define severity levels for production incidents (say Sev1 through Sev4), and how does severity map to expected response time and who gets notified?

HardTechnical
54 practiced

Your organization's average time to resolve incidents has been stuck around 90 minutes for months. How would you design a program over the next couple of quarters to meaningfully bring that down, and how would you know it's actually working rather than teams gaming the metric?

MediumTechnical
40 practiced

How would you decide whether a runbook is actually ready for on-call use, not just written? What would you check before trusting it during a real incident?

MediumTechnical
49 practiced

During a P1 outage, the first responder doesn't restore service within a few minutes and doesn't acknowledge the page. Walk through what happens next: escalation timeouts, who gets paged, which channels you use, and who ultimately declares a major incident.

Unlock Full Question Bank

Get access to all On-Call Practices and Runbook Design interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.