Tell me about a time you made a mistake and how you handled it
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess self-awareness, accountability, and whether you can turn an error into improved judgment. They are usually less interested in the mistake itself than in how honestly you describe it, how clearly you understood its causes, and whether your behavior actually changed afterward. At higher levels, they also look at whether your response matched the scope of your role and protected others from repeat failures.
Key Insights
- Pick a real mistake with some consequence. If you choose something trivial or try to disguise a strength as a weakness, you usually lose the main signal this question is designed to reveal: honest self-assessment.
- You should spend at least as much time on diagnosis and follow-through as on the mistake itself. Strong answers explain how you realized what went wrong, what you changed, and how you know the fix actually worked.
- Own your part cleanly without over-dramatizing it. The best answers neither get defensive nor become self-flagellating; they show mature accountability and a reliable learning loop.
What interviewers probe atlevel
Top Priority
At junior level, interviewers mainly want to see that you can admit a genuine mistake without blaming others or hiding behind your inexperience.
Good examples
🟢I pushed code without fully testing an edge case because I assumed a helper function covered it, and that assumption was mine.
🟢I estimated a task too confidently, got stuck, and waited too long before asking for help, which delayed the handoff.
Bad examples
🔴I wouldn't call it a mistake exactly, but one time I cared too much about quality and spent extra time polishing a feature.
🔴My lead changed the requirements late, so the work had to be redone, and I learned that communication from the top is important.
Weak answers avoid vulnerability or shift responsibility; strong answers name a credible mistake and the candidate's specific contribution to it.
Valuable
Example answers atlevel
Great answers
In my first few months, I shipped a small API change and assumed the existing validation covered all inputs. It worked in my local testing, but a teammate found that one edge case caused bad data to be saved, which blocked their work for part of the afternoon. I owned it right away, fixed the bug, added test cases for the inputs I had missed, and asked the teammate to review the fix since their workflow was the one affected. When I looked at why it happened, I realized I had only tested the happy path and was filling in some requirement details instead of asking. Since then, I use a short checklist for input handling on similar tasks and I ask clarifying questions earlier, which has helped me avoid repeating that kind of mistake.
During a campus recruiting event project, I was responsible for updating a spreadsheet that tracked interview time slots and candidate names. I copied over the schedule from an email but accidentally left one row duplicated, which meant two candidates were told to arrive at the same time. As soon as I realized it, I told my lead what happened, corrected the schedule, and personally called both candidates to apologize and explain the new times. I also checked every other row against the source email and asked another teammate to do a quick review before we sent anything else out. What I took from it was that even small administrative mistakes can affect people’s experience, so I now slow down on work that looks simple and build in a quick verification step before sharing it with others.
Poor answers
One mistake I made was spending too much time polishing a feature because I care a lot about quality. The deadline moved a little, but the end result was much cleaner and people were happy with it. After that I kept the same standards, but I tried to move a little faster when timelines were tighter. Overall it showed me that I set a high bar for my work.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid July, 2026
Late June, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.