Code Room
On-callMedium
Question
A feature suddenly broke with no deploy on your side, and you trace it to a third-party (or internal) dependency that silently changed its API/behavior. 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.
Learn the concepts
Loading whiteboard…
Run or narrate your approach, then ask the coach.