Code Room
On-callMedium
Question
A junior engineer ran a manual command in production that caused an outage, and they're shaken. As the senior on-call and reviewer, how do you handle the incident and the aftermath?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
Learn the concepts
Loading whiteboard…
Run or narrate your approach, then ask the coach.