When an interviewer asks about a failure, you may start editing the story before you have said a word. How much should you admit? Will a missed deadline sound careless? That hesitation is a good reason to choose an example before the interview, while you have time to think clearly.
To answer "Tell me about a time you failed," choose a real incident you can discuss honestly. Explain what you were responsible for, the mistake you made, its impact, and what you did afterward. Finish with a specific change in how you work, including evidence of improvement if you have it.
What is the interviewer actually trying to figure out?
A useful way to approach this question is to show how you respond when your work falls short. Give the interviewer enough detail to understand your decisions. Saying "I learned to communicate better" leaves them to guess what went wrong and whether you would handle it differently now.
UC Berkeley's interview guidance recommends drawing on your own experiences for behavioral questions and giving enough detail to be clear without monopolizing the conversation. For a failure answer, that means spending less time explaining the project background and more time on the decision you got wrong.
You can own your part without taking responsibility for everything. If a supplier missed a date, explain what you knew and what you did with that information. Perhaps you committed to a launch before confirming delivery. Perhaps you had confirmation, but waited too long to flag the delay. Those are different mistakes, and your answer should make the distinction clear.
What is a good sample answer?
The following is an illustrative example, not a reported experience. Use its level of detail to prepare your own account; do not present the incident as something that happened to you.
"I was coordinating a vendor onboarding and committed to a date before I had written confirmation of a dependency. When a warning email came in on Monday, I read it but didn't act on it. The onboarding slipped by two weeks, and our warehouse lead had already scheduled receiving staff around the original date.
"Once I understood the impact, I called the warehouse lead, acknowledged that I had left them planning around an unreliable date, and worked through a revised schedule. Our team had to absorb the overtime cost. I couldn't undo that.
"I changed how I handle external dependencies. I now ask for written confirmation before treating a date as firm. If that confirmation is missing at the agreed checkpoint, I flag the risk and agree on the next step instead of assuming the date will hold."
The uncomfortable detail is the email the candidate read but did not act on. They had information and failed to use it. That makes the change in working habits relevant. The answer also leaves the cost in the story. It does not claim that a revised schedule erased the disruption.
If your later work gives you evidence that the change helped, add it. Be precise about what you can support. A later project meeting its deadline is worth mentioning if that happened; a made-up percentage improvement adds nothing you can defend when the interviewer asks a follow-up.
Compare that account with "I overcommitted, missed a deadline, and learned to communicate better." The shorter version may be true, but it ends before the interviewer can understand your contribution to the problem. Explain which commitment was premature or which warning you left unanswered.
How do you choose a failure you can discuss?
Look for an incident where your actions affected an outcome and you can explain what happened afterward. A missed handoff, an assumption you did not check, or a poorly scoped piece of work can give you plenty to discuss. Choose something relevant to the responsibilities of the role.
You do not need to volunteer your most painful experience. You do need to answer honestly. Keep client names, private employee information, and confidential figures out of the account. You can describe a scheduling problem without identifying the customer or exposing an internal budget.
Be careful with a story about an unresolved problem central to the job. If you repeatedly miss deadlines and have not changed how you plan, claiming that one missed deadline taught you the lesson would be misleading. Describe the limits of what has improved. Where safety or integrity is involved, do not minimize the incident or invent corrective action to make the story easier to tell.
A smaller example with a clear account of your responsibility is often easier to explain than a major team failure where you cannot identify your own decisions. The importance of the incident should come from its actual effect on the work.
What if you have never had a full-time job?
Use an experience from study, volunteering, a part-time job, or a project you were responsible for. Say where it happened. There is no reason to dress a class assignment up as client work.
You can prepare with this fill-in template. Replace every bracket with a true detail, and omit anything you cannot honestly complete:
"During [a course, volunteer activity, or project], I was responsible for [your part]. I made the mistake of [specific action or assumption], which meant [actual consequence]. I responded by [what you did]. Since then, I have changed [a specific habit]. In [a later situation], that helped me [an outcome you can support]."
If you have not yet had a chance to test the change, say so. Explain what you would do differently and acknowledge that you have not demonstrated the result yet. A practice plan is useful, but it is not evidence that the problem has been solved.
Can you use STAR for a failure question?
Yes. STAR stands for situation, task, action, and result. Harvard's interviewing guide recommends organizing behavioral answers around a specific situation, your actions, and the result. For this question, make sure the action includes the mistake you made, rather than starting the story only after you began fixing it.
Keep the setup brief enough that you reach the failure early. Then describe the consequence and your response. You can discuss what changed afterward alongside the result. The headings are preparation notes; you do not have to announce "situation" and "task" while you speak.
Do not rewrite the result into a success if it was a loss. A project can remain late even after you handle the recovery responsibly. Explain the remaining impact and what you could still influence.
Answers that leave too much unexplained
"I'm a perfectionist" gives a personality label when the question asks for an incident. If excessive checking really caused a problem, describe the work you delayed and what you changed. Otherwise, choose a different example. The related greatest weakness question needs its own preparation.
Blaming a colleague creates another gap. Other people may have contributed, but the interviewer asked about you. State the shared context briefly, then explain your own responsibility. Equally, avoid turning the answer into a story about how you rescued everyone else. If your actions did not contribute to the failure, it may be the wrong example.
A long career summary can also carry you away from the incident. If you catch yourself doing that, pause and return to the relevant decision. Prepare your "Tell me about yourself" answer separately so you have somewhere appropriate for the broader career story.
Be ready for the follow-up
You can use the same truthful incident in a recruiter screen and a later interview. Adjust the amount of explanation to the question and the time available. There is no reliable rule that every screen needs a small failure or every final round needs a bigger one.
Practice answering "Why didn't you raise it earlier?" without repeating the whole story. Name the assumption or hesitation that affected your decision. For "What would you do differently now?", identify the point where you would act sooner. If asked how you know the change worked, give a real later example or acknowledge that you are still testing it.
When there is time for your questions, you might ask, "How does the team review a project that misses its target?" Listen for an example of how the team handles mistakes. If your failure story involved a budget, keep that explanation focused on the work; a conversation about your own salary can wait for the appropriate question.
Rehearse aloud once with someone who can interrupt you. Ask them which detail they still do not understand. If you cannot explain why you made the original decision, work on that part before polishing the opening sentence.