Tell Me About a Time You Made a Mistake

“Tell me about a time you made a mistake” is one of the most common behavioural questions in graduate and experienced-hire interviews, and one of the most misunderstood. Candidates often treat it as a trap and respond with either a fake flaw (“I once worked too hard”) or a mistake so trivial it says nothing. Interviewers know that everyone makes errors. What they cannot see from your CV is how you behave after you realise something has gone wrong.

That is the real subject of the question. A mistake in a graduate role could mean a wrong figure in a spreadsheet, a missed deadline, a miscommunication with a client or an incorrect assumption in a project. Employers need to know that you will spot problems, tell people promptly, fix what you can and change your process so it does not recur. People who hide errors or blame others create far more damage than the original slip.

The question also appears in many disguises: “What is the biggest mistake you have made at work?”, “Describe a time you got something wrong,” “Tell me about a time you made an error and how you handled it,” and “When have you let someone down?” All of them ask for the same thing: a genuine, specific example with honest ownership and a clear lesson. This is a close relative of the failure question, which we cover in our guide to telling me about a time you failed, but a mistake is usually smaller, more specific and more about accountability than outcome.

The best example sits in a narrow sweet spot: real enough to matter, small enough to be forgivable, and recent enough to remember in detail. A mistake that caused genuine inconvenience or cost, such as a delayed report, a wrong number sent to a customer or a double-booked room, shows that you understand stakes. A mistake that was catastrophic, illegal or involved dishonesty is a poor choice, because it raises doubts about your judgement rather than building trust.

Avoid two traps. The first is the humble-brag: “I once spent too long perfecting a presentation.” Interviewers have heard it hundreds of times and it signals evasion. The second is the blame-shifter: a story where the “mistake” was really somebody else’s fault. Pick something where you genuinely made the decision or took the action that went wrong.

Graduates sometimes worry they lack work experience. University, part-time jobs, society roles, volunteering and group projects all supply legitimate examples. Missing a coursework deadline because of poor planning, miscalculating a budget as society treasurer, or giving a customer the wrong information in a shop are all fair material, provided the story includes a fix and a lesson.

Use STAR (Situation, Task, Action, Result) for the overall shape, but give the Action and Result sections a more specific structure here. We use a four-step pattern called OFCL: Own it, Fix it, Change it, Learn from it. It keeps the answer honest and forward-looking.

Own: say plainly what you did

State the mistake in one sentence without padding. “I sent the client last month’s figures instead of this month’s” is stronger than “There was a bit of a mix-up with some data.” Ownership language includes “I,” “my error” and “I should have checked.” Avoid passive phrases such as “the wrong file got sent.”

Fix: describe the immediate response

Explain when you noticed, who you told and what you did to limit the damage. Speed and transparency matter. “I realised within an hour, told my manager straight away and sent a corrected version with a short explanation” shows the right instincts.

Change: describe the process you adjusted

This is where many candidates fall short. Saying “I will be more careful” is not a change. A real change is specific and repeatable: a checklist, a second review, a calendar reminder, a template, an earlier check-in with a stakeholder.

Learn: connect the lesson to the role

Close with what you now do differently and, ideally, a later example of it paying off. A brief sentence linking the lesson to the job you are applying for finishes the answer neatly.

These condensed examples show OFCL in different settings. Treat them as patterns rather than scripts. Interviewers can tell when an answer has been memorised, and your own details will always sound stronger than borrowed ones.

1. A wrong figure in a client report (internship)

Own: “During a finance internship I copied a revenue figure from an outdated tab into a client summary.” Fix: “I spotted it when double-checking before the meeting, told my supervisor immediately and sent a corrected version with a one-line note.” Change: “I now reconcile every number in a summary against the source file and tick each one off.” Learn: “The next three reports went out without corrections, and my supervisor asked me to share the checklist with other interns.”

2. A missed task in a group project (university)

You assumed a teammate was writing the methodology section and so nobody did. Two days before submission you noticed, owned the assumption in the group chat, reorganised responsibilities and wrote the section yourself that evening. Afterwards you introduced a shared task tracker at the first meeting of every project.

3. Giving incorrect information to a customer (part-time retail)

You told a customer an item could be returned within 30 days when the policy was 14. You corrected it the same day by phoning them, offered the manager-approved goodwill option and then wrote the policy on a card by the till. The customer stayed loyal and the card became standard practice.

4. A double-booked room (society or volunteering)

As events secretary you booked a hall for two activities on the same evening. You notified both organisers the moment you found out, secured an alternative venue within a day and added a booking calendar that all committee members could see.

5. Misreading an assessment brief (academic)

You answered the wrong question in a coursework assignment and lost marks. You asked for feedback, compared your reading against the marking criteria and began highlighting the command words in every brief. Your next two assignments improved. This works best for early-career candidates with little workplace experience.

Two candidates can describe the same event and receive very different scores. The difference lies in ownership, specificity and the quality of the lesson. Compare these two versions of the same story.

Weak: “In my last job I made a small mistake with a spreadsheet. It was not a big deal and my manager was fine about it. I learned to be more careful and always double-check my work.”

Strong: “In a retail analytics placement I filtered a sales table incorrectly and sent a weekly summary that understated one region’s results by about eight percent. I noticed it the next morning when the totals did not match the till reports. I told my manager before anyone else spotted it, sent a corrected summary within the hour and explained exactly what had changed. I then added a totals check against the till report to my weekly routine, and a colleague later adopted it. In the following six months I had no corrections to report.”

Interviewers usually probe after your first answer, both to check depth and to test whether the story is genuine. Prepare short, specific responses to the likely follow-ups and make sure that every detail you mention can be explained confidently.

Common probes include “How did your manager react?”, “What would have happened if you had not caught it?”, “Could you have prevented it?” and “Has anything similar happened since?” The last question matters most. A truthful answer shows the lesson stuck, and “No, because I now do X” is far more persuasive than a general reassurance. If something similar did recur, say so and describe how you adjusted again.

Some employers, including assessment-centre and panel interviewers, may ask a second mistake question later in the process to check consistency. Keep your facts the same each time and consider having two prepared examples from different areas, such as one technical and one interpersonal.

The most frequent error is minimising: choosing a mistake so small that it carries no stakes, then describing it in vague language. The second is blame, even subtle blame. Phrases such as “the instructions were unclear” or “my team did not tell me” make an interviewer wonder how you will behave when something goes wrong in their organisation.

Other pitfalls include choosing a mistake that reveals a serious integrity or safety problem, taking too long to reach the fix, ending with a platitude, and presenting the story as a disguised strength. Nervous candidates also over-apologise. A brief acknowledgement is enough; interviewers want accountability, not self-criticism.

Last-minute checklist

• Example chosen: a genuine mistake with real but modest stakes.
• Own: a first-person sentence naming exactly what you did.
• Fix: how quickly you noticed, who you told and what you did next.
• Change: a specific process, checklist or habit, not “be more careful.”
• Timed: about two minutes spoken, with 70% on the response and lesson.