Sample interview answers

Tell me about a time you made a mistake: sample answers

In my first week as a receptionist, I booked two clients into the same meeting room. I noticed when the second group arrived, apologised, found them another room within five minutes and told my manager. Since then, I check the room calendar before confirming any booking, and it hasn't happened again.

To adapt it, keep the mistake real but not central to the job, say “I”, and spend most of the time on the fix and what you changed.

Mock Interview Copilot practice room: an AI interviewer asks a follow-up question while the candidate's spoken answer and pace appear in the transcript
Practising answers out loud in Mock Interview Copilot: the interviewer follows up when an answer is vague, and your pace and pauses are measured.

Sample answers by job and experience

Intern in an office role, first job

During my internship, I was asked to tidy a shared spreadsheet of client contacts. I sorted one column without selecting the others, so names no longer matched phone numbers. I didn't notice until a colleague rang the wrong person that afternoon. I told my manager straight away rather than trying to fix it quietly, and we restored the morning's version from the history. Then I re-entered by hand every change made since, so nobody's work was lost. Now I always work on a copy and check a few rows against the original before saving. Small mistake, but it taught me to own things early.

Why it works: Low-stakes for a fresher, and it shows the key habit: telling someone at once.

Fast-food crew member in the US, applying for shift lead

On one of my first closing shifts, I did the end-of-day stock count and forgot to log that we were down to our last cases of buns. The order went in without them, and the next day lunch ran out by one o'clock. When my manager asked what happened, I checked the count sheet and told her it was my miss. She arranged a transfer from another location, and I came in early to help with prep. Afterwards, I suggested we circle anything running low in red so whoever orders can't miss it. We still do that, and I haven't had a stock-out on my shifts since.

Why it works: Clear ownership and a practical fix that fits a shift lead's job.

Staff nurse, ward setting

On a busy late shift, I didn't record a patient's fluid intake for most of the afternoon. I'd given drinks but meant to write them up later. At handover, the night nurse couldn't tell whether intake was adequate, and the patient was on a fluid balance chart for a reason. I told the nurse in charge straight away, gave my best estimate and said clearly it was an estimate, and we reviewed the patient together. No harm came of it, and I completed an incident report as our trust expects. I now record intake when I give it, and I teach new starters the same.

Why it works: Safe behaviour after a mistake: escalate, be honest about uncertainty, document, learn.

Accounts payable or junior accountant

Early in my career, I paid a supplier invoice twice. It arrived by post and by email with slightly different reference numbers, and I processed both in the same payment run. I spotted it two weeks later during the supplier statement reconciliation. I told my manager, contacted the supplier that day, and they credited it against their next invoice, so we lost nothing. Then I looked at the cause: our system only flagged duplicates with identical references. I proposed an extra check on same supplier, amount and date, and the systems team added it. It has caught several duplicates since.

Why it works: It turns a personal error into a process improvement, as accountants are expected to.

Software developer, a few years' experience

I once deployed a change to our sign-in page on a Friday afternoon that broke login for anyone on an older browser. Our tests passed because they only ran in one browser. Our support team raised it within half an hour and I rolled it back immediately, so the outage lasted about forty minutes. I posted an update in the incident channel explaining the cause, then wrote a blameless review. I added cross-browser tests for sign-in and proposed no non-urgent deploys on Friday afternoons, which the team adopted. The lesson: passing tests only mean something if they test what users actually do.

Why it works: Specific without jargon, with calm incident handling and a lasting fix.

Call center agent in a BPO

I quoted a customer the wrong cancellation fee. He was on an older phone plan with different terms, and I answered from memory instead of checking. I realised the next morning when I reviewed my notes. I told my team leader, then called the customer back before his bill was produced, apologised and explained my error. My team leader approved waiving the difference once, and the customer thanked us for calling before he found it himself. Since then, I open the plan details on screen before quoting any fee, even when I'm sure, and my accuracy score went up the following month.

Why it works: Honest with the customer and the team leader, plus a habit that protects quality.

Secondary school teacher

In my second year of teaching, I entered predicted grades for my Year 10 class into the wrong column of our tracker, so some reports went home showing the wrong targets. A puzzled parent emailed two days later. I checked, found the mistake was mine, and told my head of department. I corrected every report, sent a short letter home explaining and apologising, and phoned the two families whose children had been upset by a lower target. Now I check a sample of reports against my mark book before they go out, and I proof-read for colleagues too. Data I enter affects real families.

Why it works: Open with parents and leaders, and clearly cares about the impact on pupils.

Team leader in retail or operations

When I first became a team leader, I approved annual leave first come, first served without checking the overall rota. In August, three people from the same small team were off in the same week, and we were short on our busiest days. I owned it rather than asking anyone to cancel: I covered two shifts myself and borrowed a colleague from another team. Then I built a shared leave calendar showing how many people could be off each week, and explained the rule at our team meeting. We haven't been that short-staffed since, and the team says it feels fairer.

Why it works: A manager owning a planning mistake and fixing the system, not blaming the team.

What makes these answers work

The interviewer is checking whether you will tell them when something goes wrong. Someone who claims never to make mistakes is a risk; someone who owns one quickly and fixes the cause can be trusted with responsibility.

Each sample states the mistake plainly with “I”, says who the candidate told, the fix, and a habit that stuck. For choosing your story, see the full guide to “Tell me about a time you failed”.

A fill-in template

Aim for about ninety seconds, with most of it on the fix and the change.

Mistakes to avoid

Frequently asked questions

What is a good mistake to talk about?

A real, work-related mistake you owned quickly, fixed and learned from, which is not central to the job you want.

Is this the same as “Tell me about a time you failed”?

Very close. A mistake is usually smaller, but the shape is the same: own it, fix it, show what changed.

Can freshers use a mistake from university?

Yes. An internship, part-time job or group project works, as long as you show what you did about it.