How to answer "Describe a time you made a mistake" — catch it, own it, fix it

This question is narrower than it sounds. It's not asking for your life's biggest regret — it's asking about a specific, ordinary error: a wrong assumption, a missed step, a message sent too fast. What the interviewer actually cares about is what happened in the ten minutes after you realized it. Candidates who freeze, minimize, or blame someone else in that moment are the ones who struggle here — not the ones who made the mistake in the first place.

Why interviewers ask it

Everyone makes mistakes on the job; the question isn't a trap looking for a reason to disqualify you. It's checking three things a clean résumé can't show: honesty (will you actually admit an error, or quietly bury it?), speed of response (how fast did you catch it and say something?), and whether it changed anything (did the mistake actually teach you something durable, or did it just happen and get forgotten?). An interviewer who's managed people for any length of time has learned that the employees who hide mistakes are far more expensive than the ones who surface them fast.

The framework: Catch → Own → Fix → Prevent

1. Catch. How you noticed the mistake — ideally you caught it yourself, or caught it early, rather than being told by someone else after the damage had spread.
2. Own. What you actually said and to whom, and how fast. This is the beat that proves honesty — naming that you flagged it directly rather than letting it surface on its own.
3. Fix. The concrete steps you took to correct it, in order. Specifics here are what separate a real story from a vague one.
4. Prevent. The lasting change in how you work now because of it — a checklist, a habit, a review step you didn't have before.

Most candidates cover Catch and Fix well enough, then rush past Own and skip Prevent entirely. Those two beats are where the answer is actually won — Own proves you're trustworthy with bad news, and Prevent proves the mistake left a mark instead of just passing through.

A worked example

"I was updating a client-facing report and misread which quarter a column referred to, so the numbers I sent out overstated our growth for the period. I caught it myself the next morning doing an unrelated check, and the first thing I did was flag it to my manager and the client contact within the hour, rather than quietly sending a 'corrected version' and hoping nobody compared the two. We sent a clear correction the same day with an explanation, and the client appreciated that it was caught and owned fast rather than found later. Since then, I don't send anything with quarter-over-quarter numbers without a second person doing a five-minute sanity check against the raw source — it's caught two smaller errors since, before they ever left my inbox."

Catch (found it yourself, quickly) → Own (flagged it immediately, to the right people) → Fix (a fast, clear correction) → Prevent (a specific, still-active habit). Nothing here is dramatized, and nothing is glossed over.

What if the mistake genuinely hurt something or someone?

Tell it honestly, without either minimizing the impact or drowning the story in self-criticism. State plainly what the consequence was, then put most of your remaining words into the Fix and Prevent beats — that's where the interviewer learns whether you're someone who compounds a bad situation or contains it. If you're not sure how a specific mistake will sound out loud, working through the wording once — the same way you would for a greatest weakness answer you're not used to telling honestly — tends to catch phrasing that reads as defensive before it reaches the real interview. A tool like an AI interview copilot can help with exactly that: finding the grounded, accurate version of what actually happened, not a scrubbed one.

Common mistakes to avoid

• Picking a fake mistake. "I double-checked something that turned out to be fine" isn't a mistake — interviewers can tell when there was no real error or consequence.
• Blaming the process, a tool, or another person. If the story is really about someone else's error, it doesn't answer what was asked.
• Skipping Own. Jumping straight from the mistake to the fix, without saying you told anyone, leaves out the hardest and most telling part.
• No lasting change. Ending at "and I fixed it" wastes the strongest beat — a real answer names something concrete that's different now.
• Over-apologizing. Spending the whole answer on how bad you felt, instead of what you did, shifts focus away from the substance that actually matters.

The bottom line

"Describe a time you made a mistake" rewards fast, honest ownership over a spotless track record. Pick a real error, show you caught and flagged it quickly, walk through exactly how you fixed it, and name the specific way it changed how you work now. That combination reads as far more trustworthy than any story engineered to make the mistake look smaller than it was.

Related: Greatest weakness · A time you went above and beyond · How do you prioritize your work?