“Tell me about a time you failed” (or “Tell me about a mistake you made”) is a standard behavioural question, and one that many candidates dread. The interviewer is not trying to find a reason to reject you. They want to see whether you can be honest about a setback, take responsibility for it, and learn from it — qualities every team needs.
What the interviewer is testing
- Honesty: will you describe a real failure, or dodge the question?
- Ownership: do you take responsibility, or blame others and circumstances?
- Learning: what did you change afterwards?
- Judgement: is the failure you chose a sensible one to share?
Choosing the right failure
The best failure for this question is:
- Real — something that actually went wrong, not a disguised success.
- Moderate — serious enough to matter, not so serious that it raises doubts about your integrity or basic competence.
- Yours — you made a decision or a mistake that contributed to it.
- Behind you — you learned from it and can show what you do differently now.
Good sources: a missed deadline, a project that did not deliver what was expected, a wrong assumption, a team that did not work well under your coordination, an exam or interview you were underprepared for.
A structure: STAR plus the lesson
Use the STAR method, with extra weight at the end:
- Situation — the context, in one or two sentences.
- Task — what you were responsible for.
- Action — what you did, including the mistake.
- Result — what went wrong, stated plainly.
- Lesson — what you learned and, most importantly, what you have done differently since.
Spend about a third of your answer on the lesson and the change. That is the part interviewers remember.
Example: a fresher
In my third year I led a team of four for a mobile app project in our software engineering course. I was confident about the technical side, so I spent most of my time coding and assumed everyone else was on track.
Two weeks before the deadline I found that the database part, which one teammate was handling, was only half done. We submitted a working app, but without the offline feature we had promised, and we lost marks for it.
The mistake was mine: as the lead I should have been checking progress, not only writing code. Since then I hold a short weekly check-in on any group work, with a shared list of tasks and dates. In my internship I suggested the same for our small team, and it helped us catch a delay early.
Example: an experienced professional
In my previous role I launched an email campaign to around 20,000 customers without testing the link on mobile. It turned out the landing page broke on smaller screens, and most of our customers open email on their phones. We lost a good part of the campaign’s first day.
I fixed the page within a few hours and sent a short follow-up email, but the damage was done for that launch. I owned it with my manager straight away.
Afterwards I created a pre-launch checklist for the team that includes testing every link on two phones and one laptop. We’ve used it for every campaign since, and we haven’t had a similar issue.
The numbers here are illustrative; use real details from your own experience.
Failures to avoid
- Disguised successes: “I failed to take a holiday because I was so dedicated.”
- Blaming others: “The project failed because my teammates didn’t do their part.”
- Serious ethical problems: dishonesty, safety violations or anything that suggests poor integrity.
- A failure with no lesson: if you cannot say what you changed, choose a different story.
- Something core to the job: for an accountant, a story about getting the accounts wrong repeatedly will worry the interviewer.
Frequently asked questions
What if I genuinely cannot think of a failure?
Think of a time something did not go as planned: a lower mark than you expected, a project that ran late, feedback that surprised you. Everyone has these. Saying you have never failed comes across as a lack of self-awareness.
How long should the answer be?
About 90 seconds to two minutes, with the lesson taking a good part of that time.
Can I use a college example as an experienced candidate?
It is better to use a work example if you have one. Recent, professional examples are more relevant.
Practise it out loud
Talking about failure out loud is uncomfortable, and that discomfort can make the answer either too short or too long. Add “Tell me about a time you failed” to a set in the practice room and let the virtual interviewer ask it while you answer on camera. Check that you own the mistake clearly and that the lesson takes a third of the answer. The behavioural interview questions include similar questions worth preparing, such as how you handle pressure.