Failure and Mistake Interview Questions
Last updated 2026-11-19
Questions such as tell me about a time you failed, or describe a mistake you made, are among the most feared in HR rounds. Candidates worry that admitting a failure will cost them the job, and so they either say they have never failed or tell a story that is secretly a success. Interviewers see both quickly.
What they actually want is evidence that you own mistakes, learn from them and do not repeat them. This page shows how to choose a failure of the right size, how to tell it in the STAR structure, and gives fourteen related questions with sample answers for freshers and experienced candidates. See the STAR method guide and how to crack the behavioural interview.
| Right size | Real but recoverable |
|---|---|
| Core signal | Ownership, learning, changed behaviour |
| Time split | Spend most of the answer on what you did after |
What the interviewer is checking
They want honesty, accountability and learning. Someone who blames others, or cannot name a mistake, may repeat the same errors and will be hard to coach. In engineering roles, the ability to speak plainly about a bug or a missed estimate is part of a healthy team culture.
Choosing the failure
- Pick one that really was your responsibility, not a disguised success.
- Avoid anything that signals dishonesty, safety risk or an inability to do the core job.
- Prefer a failure with a clear before and after: what you did differently since.
- For freshers, academic or project failures are fine. For experienced candidates, use work.
A shape for the answer
Describe the situation briefly, say what you did wrong without excuses, then spend the middle of the answer on how you fixed the impact. End with the specific change you made and, if possible, a later example where it helped. If you can say I now do X every time, the story has a believable lesson.
Failure and Mistake Interview Questions: questions with worked answers
1 Tell me about a time you failed.
mediumSample for a fresher: In my third year, I led a team for a hackathon and did not set up version control. Two of us overwrote each other's work and we lost four hours. I took responsibility, we recovered the code from a laptop, and finished a smaller version. Since then I set up Git on day one of every project. We did not win, but I have not lost work since.
2 What is the biggest mistake you have made at work?
hardSample: I deployed a configuration change to production without a second review, and it disabled email notifications for about two hours. I noticed from a support ticket, rolled back, and informed my manager at once. We added a review step and I wrote a short postmortem. I never skip review on production changes now.
3 Tell me about a project that did not go as planned.
mediumSample: Our team estimated a migration at four weeks and it took seven because I did not test the data volumes early. I told the manager as soon as I saw the slip, we cut a reporting feature, and completed the core migration. Now I run a data-volume test in the first week. Early disclosure is part of the lesson.
4 Describe a time you missed a deadline.
mediumSample: I missed a report deadline by a day because I waited for data from another team instead of following up. I apologised, delivered the next morning and now chase dependencies two days before. The cost was small because I communicated early about the delay.
5 Tell me about a time you got negative feedback.
mediumSample: My lead said my status updates were too long. I thought detail was helpful, but he wanted a summary in three lines. I changed the format, with details linked below. He later thanked me. See strengths and weaknesses questions.
6 Have you ever failed an exam or an interview? What did you do?
mediumSample: I failed my first campus technical interview because I could not explain my own project in depth. I asked for feedback, spent a month rebuilding the project with tests, and practised explaining it. In my next interview I was able to answer follow-ups. Do not hide the failure, show the rebuild. See explain your project.
7 What did you learn from your biggest failure?
easySample: That asking early is cheaper than fixing late. When I delayed asking about a requirement, I built the wrong feature for two days. Now I confirm the requirement in writing before I start. State one concrete rule.
8 Tell me about a time you made a wrong decision.
hardSample: I chose a library with poor documentation because it was fast, and the team struggled with it. After three weeks I admitted this to the lead, we replaced it and I wrote a short evaluation checklist for later choices. Admit the wrong call and show what changed.
9 Describe a time you let a teammate down.
hardSample: I promised to review a teammate's code by Monday and forgot because of another task. He lost a day. I apologised, did the review that evening, and now I put review requests on my calendar. Own it without excuses.
10 How do you handle failure?
easySample: I try to separate the disappointment from the analysis. I first fix the impact, then ask what in my process allowed it, and then make a small change. After missing a bug in testing, I added a checklist for edge cases. Show a process.
11 Have you ever disappointed a client or customer?
hardSample: Once a client received a report with wrong totals because of a date filter I had missed. I called them the same day, explained, and sent the corrected report within two hours. I added a test for that filter. Speed and honesty protect trust.
12 What was a time you were not selected, and what did you do?
mediumSample: I was not shortlisted in a company's first campus test. I analysed my score and saw that aptitude was weak. I practised 30 minutes a day for two months and cleared the next company's test. Rejection became a plan.
13 Tell me about a mistake you caught before it caused damage.
mediumSample: Before a release I reran my migration on a copy of production data and found that it dropped a column used by a report. I fixed it before deploying. Since then I always rehearse migrations on a copy. A near miss shows carefulness.
14 Do you think failure is a bad thing?
easySample: Not necessarily. Failures that are small and quickly noticed teach quickly, and my best habits came from them. Repeated failures from carelessness are a problem, and I try to avoid those by reviewing my own work. Avoid sounding philosophical without an example.
Frequently asked questions
Is it risky to admit a real failure?
A real but recoverable failure with a clear lesson helps you. Avoid failures that suggest dishonesty or inability to do the job.
Can I say I have never failed?
No. It sounds either unreflective or untrue. Use a small real example.
What if my only failure is academic?
That is fine for freshers. Explain what you changed and how it affected later results.
Should I name who was responsible?
Focus on your own part. Blaming others, even if partly true, weakens the answer.
Related guides
More in HR Interview Questions
- HR Interview Questions for Freshers With Answers
- Internship Experience Interview Questions and Answers
- Leadership Interview Questions and Answers
- Managerial Round Interview Questions and Answers
- Notice Period and Offer Questions: How to Answer
- Questions to Ask the Interviewer at the End
- Relocation and Shift Interview Questions
- Salary Expectations Interview Questions: How to Answer
- Situational Interview Questions and Answers
- STAR Method: Behavioural Interview Questions and Answers
- Strengths and Weaknesses Interview Questions
- Stress Interview Questions and How to Handle Them