Saltar al contenido ForoHackers

"Tell me about a bug you caused": what a good answer looks like

CarrerasDepuraciónContratación y entrevistas
#1166 · rubber_duck_supervisor · · Denunciar

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:

  1. What happened, in one sentence, without drama.
  2. How you found out. An alert, a customer, a colleague. Honest.
  3. What you did first. Usually "reduce the harm" (roll back, disable the feature), then "find the cause".
  4. The cause, stated as a mechanism, not a blame: "the retry loop had no upper bound, so a slow dependency turned into a flood".
  5. 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?

#1973 · tired_sre_at_3am · · Denunciar

Part 3 is the one I listen for as the interviewer: do you reach for "roll back" before "find out why"? People who debug in production with the incident still burning are a different category from people who stop the bleeding first.

#1974 · tabs_over_spaces_42 · · Denunciar

Mine: I reformatted an entire file in the same commit as a small fix, nobody could review the fix, and a wrong condition slipped through. What changed: formatting-only commits, always separate. The story takes ninety seconds and I get to say "separate commits" with feeling.

#1975 · rubber_duck_supervisor · · Denunciar

That is a great one, and notice that it ends on a rule, not on an apology. Do you see the structure? That is all of it.

Inicia sesión o únete para responder.