How to Answer 'Tell Me About a Time You Failed' in an Interview
Choose a failure you can discuss honestly. Explain what you were responsible for, what went wrong, and what you did afterward. You don't need to turn the mistake into a disguised success. A clear account of what changed in your work is more useful than a claim that the experience made you a better person.
When asked about failure, interviewers want to see self-awareness, accountability, and growth, not perfection. Choose a genuine professional failure, take clear ownership, and spend the majority of your answer on what you learned and how you applied that lesson. Use the STAR method to keep your answer structured and concise.
Why Interviewers Ask This Question
A failure question gives you room to explain responsibility, judgment, and what changed afterward. A useful answer does more than admit a mistake: it shows how you understood the problem and responded to it.
Here's what interviewers are specifically evaluating:
Self-awareness
Can you honestly assess your own performance? Do you recognize when something went wrong and understand why?
Accountability
Do you own your mistakes or deflect blame? Taking responsibility signals maturity and integrity.
Growth mindset
Did the failure make you better? Interviewers want evidence that you learn from setbacks rather than repeating them.
Emotional maturity
Can you talk about failure without becoming defensive, dismissive, or overly self-critical? This reveals how you’ll handle adversity on the job.
Choose a real mistake you can discuss. It does not need to be dramatic: a missed assumption, a decision you had to reverse, or a goal you did not meet can give you enough to explain your responsibility and response.
What Makes a Good Failure Story
Not every failure is interview-worthy. The story you choose matters as much as how you tell it. A strong failure story has four characteristics:
It's a genuine failure
Avoid disguised humble brags like “I worked too hard” or “I cared too much about quality.” Interviewers see through these instantly, and they signal that you're not comfortable being honest. Choose something where you genuinely fell short, a missed deadline, a project that didn't hit its goals, a miscommunication that caused real consequences.
You take clear ownership
Even if external factors contributed, your answer should center on your role in the failure. Saying “the timeline was unrealistic” shifts blame. Saying “I underestimated the scope and didn't flag the risk early enough” shows ownership. Interviewers are looking for candidates who own outcomes, not just successes.
The lessons are concrete
“I learned to communicate better” is vague. “I learned to send weekly status updates to stakeholders and flag risks as soon as I see them, rather than waiting until they become blockers” is specific and actionable. The more concrete your takeaway, the more believable it is.
There's evidence of growth
The most compelling failure stories include a follow-up, a later situation where you applied the lesson and got a better outcome. This closes the loop and proves the growth was real, not just theoretical. If you can connect the failure to a subsequent success, your answer becomes a story about resilience, not just a setback.
The STAR Framework for Failure Questions
For a failure question, leave room to explain both what went wrong and how you responded. Use the sections below to organize the answer, without trying to hit a fixed percentage for each part.
Situation
The context
Set the scene briefly. Provide the context: the project, your role, the stakes. Keep it to 2–3 sentences. The interviewer needs enough background to understand the failure, but not so much that you're delaying the point.
Task
Your responsibility
Clarify what you were responsible for. This establishes that the failure was within your scope of accountability, which makes the ownership in the next section more meaningful.
Action
Your decisions and response
Describe what you did, and specifically where things went wrong. Be honest about the missteps. Did you skip a step? Misjudge a situation? Fail to communicate? This is where your self-awareness shines. Don't rush through this section; the interviewer needs to understand the failure clearly to appreciate the growth that follows.
Result + Reflection
The outcome and what changed
Describe the outcome honestly, then explain what you changed. If you have since used that lesson, give the example. If you have not had the chance yet, say what you plan to do differently without claiming a result.
A Complete Example Answer
Here's a full worked example of how to answer “Tell me about a time you failed” using the STAR framework:
“I was a product manager at a mid-size SaaS company. We were launching a new onboarding flow that was supposed to reduce churn during the first 30 days. It was one of the highest-priority initiatives that quarter, and the VP of Product was personally tracking progress.”
“I owned the end-to-end delivery: research, design, engineering coordination, and launch. My goal was to ship the new flow within six weeks and achieve a 15% reduction in 30-day churn.”
“I was so focused on hitting the deadline that I cut corners on user research. I ran one round of usability testing with just three participants and moved straight into development based on those results. I also didn't loop in the customer success team for their input on the most common onboarding pain points. I assumed I already knew them from looking at support tickets. We shipped on time, but within two weeks, the data showed the new flow actually increased churn by 4%. Users were confused by the new navigation, and the flow didn't address the real friction points that the customer success team could have identified.”
“We had to roll back to the old flow within three weeks, which was embarrassing and cost us about a month of engineering time. I took full responsibility in the retrospective. The core lesson was that speed without adequate research creates more waste than it saves. I established a personal rule: no feature ships without at least five usability participants and a cross-functional input session. On the next major initiative (a pricing page redesign) I followed that process. We ran two rounds of testing with eight participants and brought in customer success, sales, and support early. That project reduced churn by 22% and launched without a single rollback. The failure taught me that doing the upfront work isn't slowing down. It's the fastest path to getting it right.”
Notice how this answer doesn't minimize the failure. It describes the mistake clearly, takes ownership, shares a concrete lesson, and proves the growth with a follow-up success story. That's the formula.
What NOT to Say
Knowing what to avoid is just as important as knowing what to say. These are the most common mistakes candidates make when answering failure questions:
Blaming others
"The project failed because the engineering team didn’t deliver on time" makes you look like someone who deflects responsibility. Even if others contributed to the failure, focus on what you could have done differently.
Choosing a trivial example
"I once forgot to bring copies of my resume to an interview" is too minor to demonstrate real self-awareness. Choose a professional failure with genuine stakes and consequences.
No real lesson learned
If your takeaway is vague (“I learned to try harder”) or missing entirely, the interviewer will question whether you actually grew from the experience. Be specific about what changed in your behavior.
Saying "I can’t think of one"
This signals either a lack of self-awareness or a lack of experience with challenging work. Everyone who has taken on meaningful responsibility has failed at something. Prepare your failure story in advance.
Choosing something too catastrophic
A failure that caused someone to get fired, resulted in a lawsuit, or involved an ethical lapse raises more concerns than it answers. Choose a failure that was significant enough to be meaningful but contained enough to demonstrate learning.
The disguised humble brag
Calling perfectionism a failure avoids describing an actual mistake. Choose an event where you can name what went wrong and your part in it.
Variations of This Question
Listen to the wording. A question about missing a goal is different from one about a decision you later regretted. These examples can help you practice choosing the part of your experience that answers each question.
“What’s your biggest weakness?”
Similar intent, but focused on an ongoing area of development rather than a specific incident. Use a real weakness and show active steps you’re taking to improve.
“Tell me about a mistake you made at work.”
Nearly identical to the failure question. The same STAR structure applies. Focus on what you did wrong and what you learned.
“Describe a project that didn’t go as planned.”
Slightly broader: the failure might not have been your fault. But still focus on your role and what you would do differently.
“What would you do differently if you could go back?”
Explain what you would change with the benefit of later evidence. If you would keep the same decision, explain the reason and the limitation you would still accept.
“Tell me about a time you received negative feedback.”
Similar territory. Show that you listened, didn’t get defensive, and made concrete changes as a result.
“Describe your biggest professional regret.”
More personal than the others. Choose something that demonstrates maturity and growth, not bitterness or resentment.
The good news: if you prepare one strong failure story using the STAR method, you can adapt it to answer most of these variations. The core narrative stays the same. You just adjust the framing to match the specific question.
Tips for Choosing the Right Failure Story
Selecting the right story is half the battle. Use these criteria to evaluate your options:
Keep it professional, not personal
Stick to work-related failures. A personal story about a relationship or health issue is too intimate for an interview setting and doesn’t demonstrate professional growth.
Choose something recent enough to be relevant
A failure from ten years ago at an unrelated job feels disconnected. Aim for something within the last 3–5 years that’s relevant to the type of work you’ll be doing in the new role.
Pick a failure that resulted in genuine learning
The lesson should be specific and actionable, not a platitude like "I learned the importance of teamwork." If you can’t articulate a concrete behavioral change that resulted from the failure, choose a different story.
Avoid failures that caused irreparable harm
Choose an example you can discuss honestly and with appropriate care for confidentiality. Serious consequences may need more explanation, but do not change or hide a relevant fact to make the story easier to tell.
Test it with a trusted friend first
Tell your story to someone you trust and ask: Does this sound honest? Does the lesson feel genuine? Would you want to hire someone who told you this? Their reaction will tell you if the story lands.
Practice with one of your own stories
Save a story from your experience, then practice it with an AI coach using preparation for your chosen company. Check the facts and keep the wording that sounds like you.
Get Pro to practice your stories