How do you answer tell me about a time you made a mistake

Name the error in one sentence, then spend the rest of the answer on the timeline. When you knew, who you told, how long that took. The correction matters less than the disclosure, because the disclosure is the behaviour the interviewer is deciding whether to hire.

Should I pick a small mistake or a serious one

Pick one with real consequences that you disclosed quickly. A trivial mistake reads as evasion and invites a harder follow-up. A serious mistake you reported within the hour is a stronger answer than a minor one you sat on, because the size of the error is not what is being scored.

What if somebody else discovered my mistake before I did

Say so plainly and early in the answer. Interviewers assume it anyway when the story goes vague, and admitting it costs far less than being caught hiding it under a passive sentence. What you did in the hour after you were told is the part that recovers the answer.

Tell Me About a Mistake You Made (Answer Examples)

Why interviewers ask this

When an interviewer says tell me about a mistake you made at work, the mistake itself is the least interesting part of what you are about to say, and they have already decided that before you open your mouth. What they are measuring is a gap. Specifically the gap between the moment you knew something was wrong and the moment somebody else knew, because that distance is the only part of the story that predicts what you will do once you are inside their company and the mistake is theirs. Someone who closes it in an hour is a different hire from someone who closed it over a weekend, and almost nobody asked to tell me about a time you made a mistake volunteers which one they were. Most candidates arrive having rehearsed the repair and the process they put in afterwards, and they leave the disclosure to be inferred, which is the one part of the story an experienced interviewer refuses to infer.

An answer that sounds fine

I was putting together the quarterly performance report for one of our largest accounts, and it went out to the client on the Thursday. There was an error in how I had joined two of the data sources, and the engagement numbers came out overstated by around fifteen percent across every section of the report. Not a rounding issue. Once it came to light we issued a corrected report and I walked the client through exactly what had changed and why. I felt awful about it. Since then there is a review step in the process where a second analyst checks the joins before anything client-facing goes out, and we have not had a repeat in two years. It taught me to slow down on the parts of the job that feel routine, because those are the ones where I stop checking.

Where it breaks

The answer turns on four words with nobody inside them. Once it came to light. Errors do not come to light on their own. Somebody finds them, on a particular day, and this sentence has been built so that the person who found it never appears and the day they found it never gets named. Everything around that phrase is precise, the fifteen percent, the second analyst, the two years without a repeat, which makes the one vague patch louder rather than quieter. An interviewer who has sat through a few hundred versions of this interview question about a mistake you made hears the passive construction, and understands that what is being protected in that sentence is the timeline rather than the client. Anyone asked to describe a situation where you made a mistake will reach for the same phrasing, because it is the only part of the story where being vague feels like modesty.

The follow-up

How did you find out, and who did you tell first?

So the client's analyst emailed on the Monday morning asking why engagement had jumped so much, and that is when it was, I mean that is when it got confirmed. I had a feeling on the Friday that the join looked off. I told my manager Monday afternoon. Or Tuesday, before the call. I would have to go back and check the thread to be honest.

Three days moved from nowhere into the middle of the story. The candidate suspected the error on Friday, said nothing, and the client found it before anyone internally did, which is the sequence every hiring manager is listening for and the reason the question gets asked in this order. The first version described a data problem. The second describes a judgment problem, and judgment problems are the ones that follow people between jobs. The correction, the second analyst, the two clean years, all of it now sits on the far side of a weekend the candidate spent hoping to be wrong about the number.

An answer that holds up

I sent a quarterly report to a client with engagement overstated by fifteen percent, because I had joined two data sources on a key that had duplicates in it. On the Friday afternoon I noticed the totals looked high and told myself I would check on Monday. The client's analyst emailed before I got to it, which means they caught my error before I did, and that is the part I would change. I told my manager within the hour, we issued a corrected report that afternoon, and I called the client myself rather than letting her hear it from account management. Now anything that looks off gets checked the day it looks off, even when checking it means saying out loud that I might have got something wrong in front of people who have not noticed yet. The second analyst on the review step came later, and it matters much less than the change in when I speak up.

The interviewer asks the same two things, how she found out and who she told first.

The client found it, on the Monday. I had seen the number and left it over the weekend. My manager heard from me an hour after that email landed, and the client heard it from me directly before the end of that same day rather than from her account manager.

Practice this question

Say your answer to this question out loud, then get asked when you knew and who you told. Answer it now, free, no account.

Tell Me About a Mistake You Made