What the interviewer is really asking
Everyone fails. The interviewer wants to see how you handle it:
- Self-awareness: can you see your own part in what went wrong?
- Ownership: do you take responsibility, or blame others?
- Learning: did the failure change how you work?
- Judgement: do you pick a sensible example, or one that raises red flags?
A candidate who says “I have never really failed” fails this question.
They are also checking how you talk about pressure. A calm, matter-of-fact tone suggests you can handle setbacks at work without panic or defensiveness. You do not need to sound upset, and you should not joke the failure away either. Treat it like a short case study that you have already reviewed and learned from.
Keep the tone steady and specific.
How to pick the right failure
Good examples are real, work-related and recoverable: a missed deadline, a launch that underperformed, a client you lost, a presentation that went badly, a hire that did not work out.
Avoid failures that involve dishonesty, safety, patient harm, legal breaches or anything that would disqualify you from the role. Also avoid “fake” failures like “I worked too hard on a project”. Interviewers see through them immediately.
Freshers can use college projects, internships, competitions or part-time work.
A quick test: if the interviewer heard only this one story about you, would they still consider hiring you? If yes, it is a safe choice. If you feel the need to add “but I am really not like that”, pick a different example.
Use STAR, weighted towards the lesson
- Situation (10%): where you were and what was at stake.
- Task (10%): what you were responsible for.
- Action and outcome (30%): what you did, and what went wrong. Say “I” not “we”.
- Result and lesson (50%): what you changed, and the next time it worked.
The STAR answer builder helps you fit your story into this shape and trim it to the right length.
Keep the failure part factual: what happened and what it cost, such as a delayed release, an unhappy client or a missed target. Then describe the specific change you made, like a checklist, an earlier review or a new habit of asking questions sooner. Finish with a concrete moment when that change paid off, because that is what makes the lesson believable.
How to adapt by level
- Freshers: a college or internship failure is fine. Show that you now plan, ask for help earlier or test your work.
- Experienced: pick a failure with real stakes, such as a missed target or a project that slipped, and show a process change.
- Senior leaders: choose a decision that did not work: a hire, a strategy, a vendor. Show how you changed how you decide, and how you protected the team.
In every case, match the size of the failure to the level you are applying for. A senior candidate describing a college assignment sounds evasive, and a fresher describing a huge business loss sounds unlikely. Pick something that sits naturally alongside the rest of your resume and the responsibilities you claim.
Related questions you can answer with the same story
The same example often works for “Tell me about a mistake you made”, “Describe a project that did not go as planned” and “Tell me about feedback you disagreed with”. Prepare two failure stories so you are not caught using the same one twice in one interview. Your weaknesses answer should not repeat this story either; see strengths and weaknesses for that one.
Write both stories down in STAR form, practise them aloud and time yourself. If a story runs over two minutes, cut the situation, not the lesson. The interview practice tool lets you rehearse behavioural questions like this one and hear how your answer sounds before the real interview.
Having two ready also helps when a panel asks for “another example”.
Example answers
Sample people — keep the structure, then use your own facts and numbers.
-
Fresher (campus hire)
In my final year I led a four-person team building a college fest registration app. I took on the backend and assumed the payment gateway would take a day to integrate. I did not test it until the week of the fest, and it failed for UPI payments. We had to take registrations on paper for two days. My mistake was not testing the riskiest part first. Since then I list the unknowns at the start of every project and build those first. In my internship, that helped me catch an API limit in week one.
-
Experienced (5 years)
Two years ago I managed the launch of a new savings product for our bank’s branch network. I focused on the marketing material and assumed branch staff understood the product. They did not, and in the first month many customers were given wrong information about lock-in periods. Sales were well below target and complaints rose. I owned that. I ran short training sessions for every branch within three weeks and created a one-page FAQ. For the next launch I trained staff first, and complaints stayed near zero.
-
Senior manager
I once hired a senior sales manager mainly because he had worked for a large competitor. I skipped a proper reference check because we were under pressure to fill the role. Within six months his team had lost two key accounts and three people had resigned. I let him go and spent the next quarter rebuilding trust with the team and the clients. Since then, every senior hire in my team goes through structured reference calls and a case round, even when we are in a hurry.
Common mistakes
- Choosing a “failure” that is really a strength in disguise.
- Blaming a teammate, client or manager for what went wrong.
- Picking a failure serious enough to disqualify you for the role.
- Spending most of the answer on the drama and almost none on the lesson.
- Saying you cannot think of a failure.