How to Answer "Tell Me About a Time You Made a Mistake"

Interviewers ask this question to see three things: whether you can own an error without getting defensive, whether you fixed it quickly, and whether you changed how you work afterwards. A polished answer that hides the mistake fails all three.

Pick the right mistake

A simple structure

  1. Context (one or two sentences). What were you working on and what was at stake?
  2. The mistake, stated plainly. "I shipped the change without testing it on the older API version."
  3. Immediate fix. What you did in the first hours: told your lead, rolled back, contacted the customer.
  4. Root cause. Why it happened, in terms of your process, not bad luck.
  5. Lasting change. The habit, checklist, or test you added, and evidence that it worked since.

Example answer

"In my second year as a backend developer I changed a date-parsing function and only tested it against our newest client. The next morning a partner's import job failed. I told my lead within ten minutes, rolled the change back, and helped the partner re-run their import. The root cause was that I trusted the unit tests without checking which formats they covered. I added fixtures for every client format we supported and started writing a short 'who could this break' note in each pull request. We haven't had a parsing regression since."

Common mistakes with this question

Practice it out loud

Say the answer aloud three times and time it; aim for 60 to 90 seconds. If you want feedback while you practice, an AI interview assistant such as Linkjob can listen to your answer and suggest tighter wording based on your resume.

Disclosure: I work on Linkjob AI.