I coach people for interviews, and the question that makes confident people go quiet is: "tell me about a bug you caused."
They are usually afraid there is a wrong answer. There is, but not the one they fear. The wrong answers are:
- "I have never caused one." (Not credible, and a little worrying.)
- A story where the real culprit was someone else's code, configuration or spec.
- A story that stops at the apology and never reaches the fix.
A good answer has five parts, in about two minutes:
- What happened, in one sentence, without drama.
- How you found out. An alert, a customer, a colleague. Honest.
- What you did first. Usually "reduce the harm" (roll back, disable the feature), then "find the cause".
- The cause, stated as a mechanism, not a blame: "the retry loop had no upper bound, so a slow dependency turned into a flood".
- What changed afterwards. A test, a guard, a review checklist, a dashboard. This is the part interviewers remember.
Practise saying it aloud once. Then, and this is my usual move, I ask the person to answer the question again as if they were the colleague who found the bug. It reveals what the story leaves out.
What is a bug story you tell without flinching now?