# Tell me about a time you made a mistake: answers with examples

Choose a real, specific work mistake that was yours, caught in time and fixable, not a disaster. Say what you got wrong in one sentence, how you noticed, what you did to fix it, and the check or habit you added afterwards. Spend most of the answer on the fix and the check, and keep it to about a minute.

By the Speaking Coach team at Sodhera Intelligence. Updated 2026-10-22. Source: https://www.orecci.com/speaking-coach/interview-questions/tell-me-about-a-time-you-made-a-mistake/

## What the interviewer is checking

Everyone makes mistakes at work. The interviewer wants to know what happens next when you do. They're listening for:

- **Ownership.** Do you say "I", or does the mistake somehow belong to the system, the client or a colleague?
- **Speed.** Did you raise it quickly, or hope nobody noticed?
- **Repair.** Did you fix the damage, not just apologise?
- **Prevention.** Did you change something so it doesn't happen again?

The last one is what separates a good answer from an average one. Most candidates stop at "and I learned to be more careful". "Be more careful" is not a change. A checklist, a second pair of eyes or a calendar reminder is.

## Mistake or failure: pick the right size

This question is smaller than "Tell me about a time you failed". A failure is a goal you didn't reach, often over weeks. A mistake is a specific error: a wrong number, a missed email, a misread instruction. If you bring a huge failure to a mistake question, you'll spend the whole minute on damage control. For the larger version, see [how to answer the failure question](/speaking-coach/interview-questions/tell-me-about-a-time-you-failed/).

| Good size for this question | Too big | Too small |
| --- | --- | --- |
| Sent a client the wrong price list; caught it the same day | Lost the company's biggest account | A typo in an internal email |
| Booked a meeting room for the wrong date | A safety incident that hurt someone | Being five minutes late once |
| Pushed a code change without testing one edge case | A legal or compliance breach | A mistake someone else made |
| Miscounted stock before an order | Anything you'd still be defensive about | A "mistake" that's really a strength |

## The four-part answer

1. **The mistake (one or two sentences).** State it plainly. "I sent our biggest client last year's price list."
2. **How you caught it (one sentence).** You spotted it, a colleague did, or the client did. Be honest; it's fine if someone else noticed.
3. **The fix (20–30 seconds).** What you did in the next hours: who you told, what you corrected, how you handled the person affected.
4. **The check you added (15–20 seconds).** The specific change, and ideally proof it worked: "We haven't sent a wrong file since."

That's about 60 seconds, roughly 130–160 words at a normal speaking pace.

## Example answers

These use made-up details to show the shape. Swap in your own mistake.

### Example answer for an office or admin role

> "In my second month as an office coordinator, I booked a 40-person training day at our usual venue but put the wrong date on the booking. I noticed when the venue's confirmation email arrived a week later. I called them straight away. That date was full, so I told my manager the same morning, found two alternatives, and the venue moved us to a room that was available on our date at the same price. Since then, I read every confirmation against the original request the day it arrives, and I've added a booking checklist to our shared drive that the whole team now uses."

### Example answer for a software developer

> "I once shipped a change to our checkout page that broke the discount code field for customers on older phones. A support colleague flagged it two hours after release. I rolled the change back within twenty minutes, then told the team in our channel what happened and which orders were affected, so support could contact those customers. The cause was that I'd only tested on my own phone. I added an older-device check to our release list and wrote a test for that field, and it caught a similar issue three months later."

### Example answer for a retail or hospitality role

> "At the restaurant, I once took a table's order and missed that one guest said she had a nut allergy. I realised when I read the ticket back to myself before sending it to the kitchen, which is the only reason it didn't reach her. I told the chef, the dish was remade without the garnish, and I explained to the guest what had happened. After that I started writing allergies at the top of every ticket in capitals and repeating them back to the guest before I leave the table."

## Mistakes to avoid when answering

| Mistake | Why it hurts | Try instead |
| --- | --- | --- |
| "I can't think of one" | Sounds dishonest or unaware | Have a real one ready |
| A fake mistake ("I worked too hard") | Interviewers see through it | Pick a genuine, modest error |
| Blaming the system or a colleague | Fails the ownership test | Say "I" for the error, even if others contributed |
| Long setup, rushed fix | The fix is the point | 10 seconds of setup, 40 on fix and check |
| "I learned to be more careful" | Not a real change | Name the specific check you added |
| A mistake that matches a core job skill | Raises a red flag for this role | Choose one from a less central task |

## Practise the hard part: saying "I got it wrong"

Many people rush or soften the first sentence. They say "there was a bit of a mix-up with the pricing" instead of "I sent the wrong price list". Say the plain version out loud until it feels normal. It sounds confident, not weak. Recording yourself helps; the [interview answer review](/speaking-coach/tools/interview-answer-review/) shows your pace and filler words, which often spike right at the admission.

If you want to rehearse the follow-ups ("How did your manager react?", "What would you do if it happened tomorrow?"), Speaking Coach has an **Explain a mistake** scene where the other side asks about what you just said.

## Questions people ask

### Should I pick a mistake that cost the company money?

It can be fine if the cost was small and you limited it quickly. Avoid stories where the loss was large or where you can't show what you changed.

### What if someone else noticed my mistake first?

Say so. "My colleague spotted it" is honest and still lets you show a good fix and prevention. Pretending you caught it yourself is risky if they ask follow-ups.

### Can I use a mistake from school or an internship?

Yes, if you have little work experience. A wrong figure in a group report or a missed deadline at an internship works, as long as there's a fix and a check.

### How recent should the mistake be?

Within the last two or three years is best. Very old mistakes can sound like you've avoided thinking about recent ones.

### What's the difference between this and "Tell me about a time you failed"?

A mistake is a specific error you fixed; a failure is a goal you didn't reach. Prepare a different story for each, because some interviews ask both.

---
Speaking Coach on the App Store: https://apps.apple.com/app/id6767124039
Speaking Coach on Google Play: https://play.google.com/store/apps/details?id=com.sodhera.speakingcoach