# "Tell me about the hardest bug you fixed": how to tell a debugging story

> A debugging story shows how you think when you do not know the answer. Tell it in five beats: the symptom, what you ruled out, the turning point, the cause, and what you changed afterwards.

Source: https://hintvo.com/blog/hardest-bug-you-have-fixed | Last updated: November 20, 2026 | Reviewed: 2026-11-20

This question is the closest an interview gets to watching you work. The interviewer does not care much which bug it was. They want to hear how you think when you do not know the answer. Choose a bug where the method mattered, and tell it in five beats.

## Choose the right bug

- One you investigated yourself, not one you watched.
- One where the first theory was wrong. A bug found in five minutes is not a story.
- One whose cause you can explain in two sentences to someone outside the project.

## Five beats

1. **The symptom.** What users or the team saw, and why it mattered.
2. **What you ruled out.** The first theories, and how you showed each one was wrong.
3. **The turning point.** The observation or the experiment that changed your mind.
4. **The cause.** In plain words.
5. **What you changed afterwards.** The fix, and the thing that stops it from coming back: a test, an alert, a check in review.

## An example

"About once a week, a customer was charged twice, and we could never reproduce it. I first suspected the payment provider, and ruled that out by matching their logs with ours: each double charge was two separate requests from us. Then I suspected a double click, but the two requests were always thirty seconds apart. Thirty seconds was our timeout. The first request was timing out on our side while it succeeded on theirs, and our worker was trying again. I added a unique key per order, so a repeat counts as the same charge, and an alert on any order with two charge attempts."

## What makes it good

- Each step says how you knew, not only what you did.
- The wrong theories are in it. They are the evidence of method.
- It ends with prevention, which is what a senior engineer is expected to add.

## Expect these follow-ups

- How long did it take, and what would have made it faster?
- How did you know the fix worked?
- Why was it possible in the first place?
- What would you do differently now?

## If the hardest bug was your own mistake

Tell it anyway. Finding and fixing your own error, and saying so plainly, is a stronger story than a bug in someone else's code.

> **Where Hintvo fits:** with your CV added, answers to questions about your experience are built from the work you actually did. The CV step of an interview session says it plainly: questions about you are answered from your CV, and never go beyond what it says. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no. See [the interview copilot](https://hintvo.com/interview-copilot).

## Related

- [AI interview copilot that answers from your CV](https://hintvo.com/interview-copilot.md): How does Hintvo AI help in a job interview, and how do I practice with it?
- [Debugging interviews: finding a bug in code you have never seen](https://hintvo.com/blog/debugging-interview-find-the-bug.md): How do I find a bug quickly in a debugging interview?
- [How to explain a past project in an interview](https://hintvo.com/blog/explain-a-past-project-in-an-interview.md): How do I explain a past project clearly in a job interview?
