To answer “tell me about a time you made a mistake,” pick a real error that was clearly yours, describe it in one or two sentences, then spend most of the answer on how you caught it, fixed it, told the right people and changed your process so it wouldn’t happen again. Keep it to about 90 seconds and say “I,” not “we,” when you describe the error.
This guide explains what the question tests, how a mistake story differs from a failure story, a four-step structure, six example answers from different jobs, and the follow-up questions to prepare for.
What the interviewer is checking with “tell me about a time you made a mistake”
Everyone makes mistakes at work. The interviewer wants to know what you do after one:
- Ownership. Do you say “I made an error” plainly, or blame the process, the tool or a coworker?
- Speed and judgment. Once you noticed, did you act quickly and limit the damage?
- Honesty. Did you tell your manager or the affected people yourself, or hope nobody noticed?
- Prevention. Did you change something — a checklist, a review step, a habit — so it wouldn’t happen again?
Some employers spell this out. As of October 2026, Amazon’s Leadership Principles say under Earn Trust that leaders “are vocally self-critical, even when doing so is awkward or embarrassing,” and under Ownership: “They never say ‘that’s not my job.’” Most interviewers listen for the same qualities even when they don’t write them down.
You’ll hear the question as “tell me about an error you made,” “describe a time you got something wrong,” “tell me about a mistake and how you handled it” or “what’s the biggest mistake you’ve made at work?”
A mistake is not the same as a failure
Interviewers often ask both questions, and the best answers are different stories:
| “Tell me about a time you made a mistake” | “Tell me about a time you failed” | |
|---|---|---|
| What happened | You did something wrong: an error, an oversight, a bad assumption | A goal wasn’t reached, often despite reasonable decisions |
| Whose fault | Clearly yours | Can be shared or partly outside your control |
| Focus of the answer | Owning it, fixing it, telling people, preventing a repeat | What you learned and what you do differently on the next big effort |
| Typical size | A specific moment with a clear fix | A project, goal or longer effort |
If you need a failure story too, our guide to tell me about a time you failed covers how to choose and tell one.
How to choose the right mistake
A good mistake story is real, clearly your fault, meaningful enough to matter, and fixed. Look for:
- A data, number or calculation error you caught and corrected.
- Sending something to the wrong person, or with the wrong information.
- A missed step in a process: a check you skipped, an approval you didn’t get.
- A wrong assumption about what a customer or manager wanted.
- Committing to a deadline without checking with the people who had to do the work.
Avoid mistakes that caused serious harm to people, broke the law or a safety rule, or that suggest a pattern of carelessness in the core skill of the job. Also avoid trivial ones (“I once forgot to cc someone”) — if nothing was at stake, there’s nothing to show. And don’t pick a mistake you never fixed.
The four-step structure: own it, fix it, tell, prevent
| Step | What to say | Time |
|---|---|---|
| 1. Own it | The context in one sentence, then the mistake in plain words: “I sent the wrong file.” | About 15 seconds |
| 2. Fix it | How you noticed, and what you did right away to limit the damage. | About 25 seconds |
| 3. Tell | Who you told, when and how: your manager, the customer, the team. | About 15 seconds |
| 4. Prevent | The specific change you made so it wouldn’t happen again, and how it has held up. | About 30 seconds |
This is the STAR method (Situation, Task, Action, Result) reshaped for mistakes; our explainer on what the STAR method is has the basics. The prevention step is what separates a strong answer from an adequate one — it shows the mistake made you and your team better.
Example answers to “tell me about a time you made a mistake”
These are example answers we wrote to show the structure in different jobs; they are not real candidates’ stories. Use your own mistake and only numbers you can back up.
Example (new grad / entry level): a data error
“In my first month as an operations assistant, I built a weekly inventory report and pulled numbers from the wrong date range, so one product looked overstocked. My manager almost canceled an order based on it. I noticed the next morning when the totals didn’t match the warehouse count, told her right away, and sent a corrected report within the hour, so the order went through. Since then I add a check row that compares my totals to the source system before I send anything, and I note the date range at the top of every report.”
Example (customer service): a wrong promise
“I told a customer they’d get a full refund on an annual plan, but our policy only allowed a partial refund after the first month. I realized it when I processed the request. I called the customer back that afternoon, apologized, explained the actual policy and asked my lead whether we could honor what I’d said. We did, once. Then I made a one-page sheet of the refund rules I was least sure about, and I now check it before promising anything. My lead later shared it with the whole team.”
Example (marketing): an email to the wrong list
“I sent a discount email meant for our loyalty members to our full customer list, so thousands of people got an offer we hadn’t planned for. I spotted it within minutes, paused the rest of the send, and told my manager immediately. We decided to honor the code rather than confuse customers, and I wrote a short note to finance explaining the cost. Afterward I added a step to our launch checklist: a second person confirms the audience before any send above a set size. We haven’t had a wrong-list send since.”
Example (finance): a spreadsheet formula
“While preparing a monthly budget review, I copied a formula down a column without locking a cell reference, which understated one department’s spending. The director caught a number that looked too low in the meeting. I owned it on the spot, found the error that afternoon and sent a corrected file with a note on exactly what changed. I now run a quick reconciliation of totals against the general ledger before I share any report, and I added that step to our team’s month-end checklist.”
Example (project coordinator): a deadline I couldn’t meet
“A client asked if we could deliver a set of drawings a week early, and I said yes without checking with the design team. When I told them, they explained it wasn’t possible without dropping other work. I called the client the same day, explained that I’d committed too quickly, and offered a realistic date with a partial delivery in between. They accepted. Now I never commit to a date change without a quick check with the people doing the work, even if it means telling a client I’ll confirm within the hour.”
Example (manager): a hiring decision
“Early as a manager, I hired someone mainly because they interviewed well, without checking references closely, and the role turned out to be a poor fit for their skills. That was my mistake, not theirs. I worked with them on a development plan, and when it was clear the fit wasn’t there, I helped them move to a role on another team that suited them better. Since then I use a short work sample and structured reference questions for every hire, and I involve a second interviewer from the team.”
Follow-up questions to expect
- “How did you find out about the mistake?” Ideally, you caught it yourself. If someone else did, say so and explain how you responded.
- “What was the impact?” Be honest and specific, without exaggerating or minimizing.
- “How did your manager react?” Focus on what you did, not on their mood.
- “Has it happened again?” If your fix worked, say so. If it happened once more, say what you changed the second time.
- “What would you do differently?” Usually: the prevention step you added, earlier.
- “Tell me about another mistake.” Have a second, smaller one ready.
Mistakes to avoid when answering
- Blaming someone else. If the story starts with what a coworker did wrong, pick a different story.
- The disguised strength. “My mistake was working too hard on the project” isn’t a mistake.
- Too small or too big. Choose something that mattered but didn’t cause serious harm.
- Too long on the setup. One sentence of context is usually enough.
- No prevention. Fixing the one instance isn’t enough; show what changed.
- Getting defensive. Explaining why it was understandable undercuts the ownership.
How to practice this answer out loud
- List two or three real mistakes from the last few years where you made a clear fix.
- Choose one main story and one backup. Check that neither involves serious harm or a core-skill weakness.
- Draft the four steps with the free STAR story builder, keeping “fix” and “prevent” longer than the setup.
- Say it out loud and time it. Aim for about 90 seconds.
- Get scored feedback. A free AI mock interview asks behavioral questions like this one. In the CoPilot Interview desktop app, Mock Interview builds questions from your résumé and the job description and scores each spoken answer out of 10 with what to fix and a model answer.
Prepare related questions at the same time: tell me about a time you received critical feedback, what is your greatest weakness and how do you handle pressure. For a full story bank, see how to prepare for a behavioral interview and our behavioral interview help.
Practice your mistake story out loud
Answer “tell me about a time you made a mistake” in a free AI mock interview and get a score out of 10, what to fix and a model answer. Free plan: 15 minutes a day, no credit card.
Try a free AI mock interviewFAQ
What kind of mistake should I talk about in an interview?
A real, work-related error that was clearly yours, mattered enough to need fixing and did not cause serious harm. Data errors, wrong assumptions, a missed process step or committing too fast are good choices, as long as you fixed it and changed something afterward.
How long should my answer be?
About 90 seconds. Spend about 15 seconds on the mistake and most of the rest on how you fixed it, who you told and what you changed so it would not happen again.
What is the difference between a mistake and a failure question?
A mistake is an error you made, with a clear fix. A failure is a goal you did not reach, often with shared causes. The mistake answer focuses on ownership and prevention; the failure answer focuses on what you learned for the next big effort.
Is it OK to talk about a big mistake?
Yes, if it was handled well and did not involve harm to people, a legal or safety breach, or a pattern of carelessness in a core skill. A meaningful mistake you owned and fixed is more convincing than a trivial one.
What if I can’t think of a mistake?
Look back at reports you had to correct, emails you followed up on, deadlines you renegotiated or feedback from a manager. Saying you have never made a mistake signals low self-awareness, which is what this question tests.
Should I say what happened to the person who caught my mistake?
Only briefly, and positively. If a coworker or manager caught it, credit them and focus on how you responded. The story should be about your ownership, not about anyone else.