When an interviewer asks about a mistake, the error itself deserves one or two sentences. The rest of your answer should cover what happened next: how you noticed it, who you told, how you limited the damage and what you changed so it would not happen again. Career advisers at UCSF put it simply: “the employer is usually more interested in how you recovered from the mistake than the mistake itself.”
This guide shows how to build that recovery story, how to pick a mistake that helps rather than harms you, and what changes if you work in a regulated field such as healthcare.
A mistake is not the same as a failure
The two questions are often treated as one, but they ask for slightly different stories. A failure is an outcome that fell short, such as a missed target or a lost bid, and it usually has several causes. A mistake is narrower: something you did, or didn’t do, that was wrong.
That narrowness makes the question harder, because there is no market downturn or late supplier to share the blame. It also makes the answer easier to structure: one action, one consequence, one fix, one change. If you have already prepared a failure story, check whether it contains a specific error of your own. If it doesn’t, prepare a separate example for this question.
The five things your answer should show
Behavioural questions are built on what the US Office of Personnel Management calls “the premise that the best predictor of future behavior on the job is past behavior under similar circumstances”. In a structured interview, panels often rate your answer against example responses agreed in advance for each level of performance. An answer that skips a stage gives them less to compare. Cover these five stages in order.
1. How you noticed
Say how the error came to light. If you caught it yourself through a check, that tells the interviewer something good about your habits. If a colleague or customer found it, say so plainly. Hiding who found the mistake is the quickest way to lose credibility if the interviewer asks a follow-up.
2. How you owned it
Name who you told and how quickly. “I told my manager within the hour” is far stronger than “it was dealt with”. This is the part of the answer that shows integrity, and interviewers listen for whether you reported the problem or waited to see if anyone would notice.
3. How you contained it
Describe the immediate steps you took to stop the damage spreading: recalling an email, pausing a process, warning the people affected, putting a temporary fix in place. Containment is often where the real skill shows, because it happens under pressure.
4. How you corrected it
Explain the actual fix and the end result. Be specific about what was put right and what, if anything, could not be undone.
5. What you changed
This is the stage most candidates rush. “I learned to be more careful” is not a change; it is a hope. A strong answer names a cause and a change to how the work is done: a checklist, a second review, an automated check, a different handover.
A quick way to find the cause is the “5 Whys” technique, which the Lean Enterprise Institute defines as “the practice of asking why repeatedly whenever a problem is encountered.” Ask why the error happened, then why that happened, until you reach something you could actually change. “I was rushing” usually leads to “the report was always prepared on the morning it was due”, which leads to a real fix: preparing it the afternoon before.
MIT’s career advisers suggest giving about 60% of a STAR answer to the actions you took. For this question, those actions are stages two to five. Keep the situation short.
Choosing your mistake: a five-question filter
| Ask yourself | Keep the example if | Choose another if |
|---|---|---|
| Was it clearly my error? | You made the decision or did the work | It was mainly someone else’s mistake that you happened to fix |
| Was it resolved? | The damage was contained and corrected | It is still unresolved, under dispute or under investigation |
| How serious was it? | It had real consequences that were recoverable | It caused harm to someone, a legal breach or a large financial loss |
| Did I change something? | You can name a lasting change and, ideally, evidence it worked | The only lesson is “be more careful” |
| Can I tell it safely? | You can describe it without names or confidential details | It depends on client data, patient details or internal disputes |
Avoid anything involving dishonesty. A mistake is an error; covering up an error, falsifying a record or knowingly breaking a rule is a different kind of story, and it is not one to tell in an interview.
A mistake in a core skill for the new job is not automatically off-limits. A software engineer whose configuration change caused a short outage that they rolled back and then prevented with a new review step can tell that story well. What matters is the severity and how strong the response was.
What kinds of mistake tend to work, by type of role
The examples below are illustrative, not drawn from real cases. They show the size and shape of mistake that usually fits, and the kind of change that makes the answer credible.
- Office and administration: sending a meeting invitation with an internal attachment to an external guest list. Containment: recall request and a direct call to the recipients. Change: a separate template for external invitations.
- Customer service: quoting an out-of-date refund policy to several customers. Containment: contacting each customer to honour or correct the information. Change: flagging the old policy document for removal from the shared drive and checking the policy page at the start of each shift.
- Sales: sending a quotation with the wrong volume discount. Containment: telling the client before they accepted. Change: a pricing calculator or a second sign-off above a certain value.
- Software and IT: applying a change directly to a live system without peer review. Containment: rollback and a status update to users. Change: making review a required step.
- Hospitality: double-booking a function room. Containment: offering the second group an alternative space with an upgrade the manager approved. Change: a single booking calendar instead of two.
- Data and finance: a filter error that left part of the data out of a report. Containment: a correction notice to recipients. Change: reconciling totals against a second source before release.
A worked answer, annotated
This illustrative answer is for a data analyst role. It runs to roughly 90 seconds when spoken.
“In my last role I produced a weekly sales dashboard for the regional managers. One week I changed a date filter to fix a reporting lag, and without realising it I excluded returns for one region. Its sales looked about 8% higher than they really were.
I caught it the next morning when I compared the dashboard total with the finance team’s figure, which I did every Monday. I told my manager straight away, explained what had gone wrong and suggested a correction note. Within the hour I had emailed the regional managers with the corrected figure and asked them not to use the earlier version. One manager had already shared it with his team, so I sent him a short note he could forward.
Then I worked out why it had happened. I’d edited the filter directly in the live dashboard with no test step. I started making changes in a copy first and added an automatic check that compares the dashboard total with the finance total and flags any gap above 1% before it publishes. In the following six months that check caught two more discrepancies, neither of them mine, before anyone saw them.”
Why it works:
- The error takes two sentences and states the consequence with a number, without dwelling on it.
- Detection came from a habit (the Monday comparison), which already says something about how the candidate works.
- Ownership is explicit and timed: “straight away”, “within the hour”.
- Containment handles the awkward detail of a figure that had already spread, rather than pretending it hadn’t.
- The change is a system, not a resolution to try harder, and there is evidence it worked.
If the role you are applying for is analytical, the same habits belong on your CV. The data analyst resume builder shows how to phrase accuracy and quality-control work as achievements rather than duties.
If you work in healthcare or another regulated field
In some professions, how you respond to a mistake is set out in professional guidance, and interview panels may listen for it. In the UK, joint guidance from the General Medical Council and the Nursing and Midwifery Council on the professional duty of candour says health and care professionals must:
- “tell the person (or, where appropriate, their advocate, carer or family) when something has gone wrong”;
- “apologise to the person (or, where appropriate, their advocate, carer or family)”;
- “offer an appropriate remedy or support to put matters right (if possible)”;
- explain the short and long-term effects of what happened.
The same guidance says professionals must be open and honest with colleagues, employers and relevant organisations, and take part in reviews and investigations when asked. Requirements differ by country and regulator, so check the guidance that applies where you are licensed.
In practice, candidates in clinical roles often choose a low-harm incident or a near miss, describe reporting it through the organisation’s incident system, and explain the change that followed. Never include details that could identify a patient. The same logic applies in finance, aviation and engineering: name the reporting route you used, because using it is part of the answer.
Phrases that weaken the answer
- “I’m a perfectionist, so I took on too much.” This is a disguised strength, and interviewers recognise it.
- “It wasn’t entirely my fault.” Others may have contributed, but the question asks about your part.
- “Luckily nobody noticed.” This suggests you would have stayed quiet if you could.
- “I learned to double-check everything.” Too vague to believe. Say what you check, when and how.
- Long technical detail. Explain the error in terms a non-specialist on the panel can follow.
Follow-up questions to prepare for
- “How did your manager react?” Answer factually, without exaggerating praise or criticism.
- “What did it cost?” Have a rough figure or consequence ready if there was one.
- “What would you do if you found the same error today?” Describe your current process, which should reflect the change you made.
- “Tell me about a mistake you didn’t catch.” Have a smaller second example ready.
- “Have you ever seen a colleague make a mistake? What did you do?” This tests whether you would raise a concern. Keep it factual and respectful.
Mistake stories are among the examples worth keeping in a written bank alongside your other interview answers. The resume and interview questions hub collects related questions you can prepare for in the same way.
Frequently asked questions
Is a near miss a good enough example?
Often, yes. A near miss is an error that was caught before it caused harm, and it still covers all five stages if you can show how it was noticed, who you told and what changed. It is a sensible choice in safety-critical or regulated roles, where the reporting route is part of what the panel wants to hear.
Should I talk about a mistake nobody else knew about?
Only if you disclosed and corrected it once you found it. A mistake you noticed, reported and fixed before it caused harm is a good example. A mistake you quietly fixed and never mentioned may raise more questions than it answers.
What if they ask for my “biggest” mistake?
Choose one with real consequences that you were able to put right. “Biggest” does not require a disaster; it requires an honest example that is clearly more than a typo.
Sources
- In an interview, how do I talk about a mistake I made? (UCSF Office of Career and Professional Development)
- Using the STAR method for your next behavioral interview (MIT Career Advising and Professional Development)
- Structured interviews: a practical guide (US Office of Personnel Management)
- 5 Whys (Lean Enterprise Institute)
- Openness and honesty when things go wrong: the professional duty of candour (General Medical Council and Nursing and Midwifery Council)