On-callMediumoc-p020

Subject Incident responseLevel Mid–Senior~20 minCommon in Reliability & on-call interviewsIndustries Technology

Question

Error rates jumped but there was no code deploy — though someone mentions a config / feature-flag change went out around that time. How do you proceed?

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

Diagram & narrate the incident

Loading whiteboard…

Run or narrate your approach, then ask the coach.