Code Room
On-callMediumoc-p084
Subject Incident responseLevel Mid–Senior~20 minCommon in Reliability & on-call interviewsIndustries Technology, Software development

Question

One service is pinning CPU at 100% on every instance, and it started right after a deploy. You suspect a hot loop or pathological code path. How do you respond?

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.

Diagram & narrate the incident
Loading whiteboard…
Run or narrate your approach, then ask the coach.