"Tell Me About a Time You Made a Mistake": How to Answer + 6 Examples
A five-step framework for turning an honest error into proof of accountability and judgement, with six worked answers and the traps that make this question go wrong.
Why Interviewers Ask About Mistakes
Almost every behavioural interview includes some version of this question: "Tell me about a time you made a mistake", "Describe an error you made at work" or "What is the biggest mistake of your career so far?" Interviewers do not ask it to catch you out. Everybody makes mistakes, and a candidate who claims never to have made one is either inexperienced, unreflective or not being honest.
What the question really measures is how you behave after things go wrong. A hiring manager is trying to predict how you will act on the day a client report goes out with an error or a deadline slips because of a decision you made. They are listening for four signals: whether you take ownership, whether you act quickly to limit damage, whether you communicate openly, and whether you change something so it does not recur.
| What the interviewer hears | What it signals |
|---|---|
| "It was my responsibility" | Accountability — you will not hide problems or blame others |
| "I told my manager the same day" | Transparency — problems surface early, when they are cheapest to fix |
| "I fixed it by…" | Problem-solving under pressure and bias to action |
| "Since then I always…" | Learning — the mistake produced a lasting improvement |
| "It was the team's fault" or "I can't think of one" | Red flags: deflection, low self-awareness or evasiveness |
The two overlap heavily. If you have already prepared for "Tell me about a time you failed", you can reuse the structure, but a mistake story is usually smaller and more contained: a specific error with a clear cause, rather than a project that did not succeed.
The 5-Step Framework for a Strong Answer
The classic STAR method (Situation, Task, Action, Result) works for mistake questions, but it needs one extra ingredient: reflection. Use this five-step version instead, and spend your time where the interviewer is listening hardest.
1. Situation and stakes (10–15 seconds)
Set the scene in two sentences: your role, what you were working on, and why it mattered. Keep it short. Long context is the most common way candidates run out of time before reaching the interesting part.
2. The mistake itself (15 seconds)
State the error plainly and in the first person: "I sent the wrong version of the pricing sheet to a client." Do not bury it in passive language such as "an error occurred". Ownership is the whole point.
3. How you responded (40–50 seconds)
This is the heart of your answer. Describe what you did in order: how you noticed it, who you told and when, how you contained the damage, and how you fixed it. Concrete actions beat general statements about "being proactive".
4. The outcome (15 seconds)
Say what happened. Ideally the situation was recovered, but an honest partial recovery is fine. Do not exaggerate a happy ending.
5. What you changed (20–30 seconds)
Close with a specific, durable change: a checklist, a second review step, a new template, a habit. Then, if you can, add a short example of using it since. This final step separates a good answer from a forgettable one.
Around 60% of your time should be steps 3 and 5 (response and learning). If you find yourself spending most of your answer describing how the mistake happened, you are telling the wrong story.
Choosing the Right Mistake to Talk About
The story you pick matters as much as how you tell it. A good mistake is real, moderate in size, and clearly your responsibility. It should have a visible recovery and a lasting lesson.
| Good choice | Poor choice |
|---|---|
| A missed detail in a report that you caught and corrected before wider harm | A trivial slip ("I once arrived two minutes late") that sounds like a dodge |
| Underestimating how long a task would take, then renegotiating and recovering | A serious ethical or safety breach that raises integrity concerns |
| A communication gap that caused rework, which you fixed with a new process | A mistake that was mostly someone else's fault |
| A judgement call that did not pay off, where you escalated quickly | A "strength disguised as a weakness" such as "I care too much" |
Where to find your story
- Work: missed deadlines, data or calculation errors, miscommunication with a client or colleague, an assumption you did not check.
- University: a group project where you took on too much, left a task late or misread the brief.
- Part-time jobs and volunteering: till errors, rota mix-ups, an event detail you overlooked.
- Sport or societies: a decision as captain or treasurer that backfired.
Interviewers hear "I work too hard" and "I'm a perfectionist" constantly. They read it as evasion. Choose a genuine, specific error and be prepared for follow-up questions about it.
Six Worked Sample Answers
Use these as models for structure and tone, not scripts. Your own details will always be more convincing.
Example 1 — Data error in a report (analyst / graduate)
"In my internship I prepared a weekly sales summary for a team of six. One week I copied a formula down incorrectly and the regional total was overstated by about 8%. A colleague spotted it the next morning, after the report had been circulated. I told my supervisor straight away, sent a corrected version within the hour with a short note explaining what had changed, and checked the previous four weeks to make sure nothing else was affected. Nothing had gone to a client, so the impact was limited. Since then I reconcile every total against the source data before sending and I built a simple checks tab into the template, which my team adopted."
Example 2 — Misjudged a deadline (project role)
"I agreed to deliver a project plan in three days without checking dependencies. On day two I realised I needed input from finance that would not arrive in time. Rather than hoping for the best, I told my manager that afternoon, proposed delivering a draft on the original date with the finance section flagged, and the full version two days later. She agreed. I now break any estimate into steps and check dependencies before committing to a date."
Example 3 — Customer-facing slip (retail / hospitality)
"I once gave a customer the wrong size of an item and they only noticed at home. I apologised, arranged a free exchange and checked my other recent orders. I realised I had been rushing during a busy period, so I started reading orders back to the customer before bagging them. My error rate dropped and a manager asked me to show new starters the same habit."
Example 4 — Group project at university
"As group lead I assumed everyone had read the marking criteria and did not check. Two days before submission we found one section did not meet the brief. I took responsibility, called a short meeting, reassigned the work and rewrote part of it myself. We submitted on time. I now run a criteria check at the start of every project and ask each person to confirm their section against it."
Example 5 — Communication error (professional)
"I forwarded an internal email thread to a supplier without noticing it contained a pricing discussion. I realised within minutes, recalled the message where possible and told my manager immediately. We contacted the supplier, who confirmed they had not relied on it. I now check threads before forwarding and use a clean summary email instead."
Example 6 — Judgement call that went wrong (experienced hire)
"I decided to launch a campaign to a wider audience before the test results were conclusive. Engagement dropped and we had to pause. I presented the data to my director that day, owned the decision and proposed a revised test plan. Since then I define success criteria and a minimum sample size before any launch, and I have used that approach on the last three campaigns."
Every answer names the error plainly, shows speed and honesty in response, and finishes with a changed behaviour. None blames someone else, and none is dramatic. Calm, specific, accountable is the tone to aim for.
Seven Ways This Answer Goes Wrong
- Claiming you have never made a mistake. This is the single worst response.
- Blaming others. Even if others contributed, describe only your part.
- Choosing a trivial or fake mistake. It signals you are avoiding the question.
- Skipping the fix. A story that ends at the error shows no recovery.
- No lesson, or a vague one. "I learned to be more careful" is not a change. Name the specific system or habit.
- Over-apologising or self-flagellating. Stay factual and composed.
- Picking a story that undermines the role. Do not describe a careless numerical error if you are applying for a role built on accuracy. Choose a different, equally real example.
If you are applying to a company with stated values, such as Amazon ("Ownership", "Learn and Be Curious") or Google, frame your lesson in terms of those values without quoting them mechanically.
Follow-Up Questions to Expect
Strong interviewers probe the story. Prepare short, honest answers to these.
| Follow-up | What they want to know |
|---|---|
| "What would you do differently?" | Whether your lesson goes beyond "be more careful" |
| "How did your manager react?" | Whether you told them promptly and how you handle feedback |
| "What was the impact?" | Whether you understand consequences and can quantify them |
| "Has it happened again?" | Whether the change you described actually worked |
| "Who else was involved?" | Whether you will stay accountable when others are named |
Related behavioural prompts you can prepare alongside this one include disagreeing with your manager, "What are your weaknesses?" and resilience questions. They draw on overlapping stories.
How to Prepare Your Answer
- Write down three real mistakes from work, study or volunteering and pick the one with the clearest recovery and lesson.
- Outline it with the five steps and cut anything that does not serve steps 3 and 5.
- Say it aloud and time it. Aim for around two minutes. For a video format, see our video interview tips.
- Prepare a one-sentence version in case the interviewer wants a quick answer in a competency-based interview.
- Have a backup story in case the interviewer follows up with "Another one?"
For the wider picture, see our guides to behavioural interview questions and how to prepare for a job interview.
Frequently Asked Questions
Ready to Practise Your Interview Answers?
Sharpen your accuracy and speed with free timed practice tests, then rehearse your stories using our behavioural interview guides.
Keep reading
- Guide · Strategy & Scoring"Tell Me About a Time You Led a Team": Answer Guide & 6 Examples
- Article · Strategy & ScoringTell Me About a Time You Went Above and Beyond: Answer Framework and Examples
- Guide · Strategy & ScoringSTAR Interview Technique: Complete Guide with Worked Examples
- Guide · Strategy & Scoring"Tell Me About Yourself": Best Answer Structure & Examples
- Guide · Strategy & Scoring"Why Do You Want to Work Here?": Answer Guide & Examples
- Article · Strategy & ScoringHow to Pass the SHL Numerical Reasoning Test: 12 Expert Tips