How to Answer 'Tell Me About a Time You Failed': 15 Sample Answers

Last updated: November 2026

Quick Answer

To answer “Tell me about a time you failed,” pick one real, past failure that you caused or owned, say plainly what went wrong and why, spend most of the answer on what you did to recover, and end with the habit you changed and proof it worked. The interviewer is testing accountability and learning, not whether you have ever failed. Keep it under two minutes. Rehearse the story with follow-up questions in OphyAI Interview Practice, and in live video rounds OphyAI Interview Copilot suggests answer points in real time.

Top 10 versions of the question	What they really want to know
Tell me about a time you failed.	Do you own outcomes and learn?
What is your biggest failure?	Scale of responsibility, and honesty about it
Tell me about a mistake you made at work.	Integrity: do you report and fix errors?
Tell me about a project that failed.	Your share of a team failure, not the team’s
Tell me about a time you missed a deadline.	Planning, and how early you raised the flag
Describe a decision you regret.	Judgment and how you weigh information
Tell me about a setback you faced.	Resilience and recovery
Tell me about a time you were wrong.	Openness to being disproven
What would you do differently?	Whether the lesson is real or rehearsed
How do you handle failure?	Your process, backed by one story

Why Interviewers Ask About Failure

Interviewers ask about failure because how you handle a setback predicts how you will handle the next one in their job. Arizona State University’s Fulton Schools career center puts it directly: “‘Tell me about a time you failed’ is your opportunity to demonstrate resilience,” and employers “want to hear about the plan that did not work,” then “how you reacted, what you learned and how you kept on going.” The University of Warwick careers service makes the same point from the other side: “the interviewer is really assessing how you respond to failure, not the failure itself.”

Some employers write the trait into their hiring criteria. Amazon’s Earn Trust leadership principle says leaders “are vocally self-critical, even when doing so is awkward or embarrassing,” and its Ownership principle says leaders “never say ‘that’s not my job.’” A failure story is the cleanest way to show both.

What they test:

1. Accountability. Do you say “I” when describing what went wrong?
2. Judgment. Can you explain the real cause, not just the bad luck?
3. Recovery. What did you do in the hours and weeks after?
4. Learning. Did your behavior change, and can you prove it?

Red flags that fail candidates:

• The humblebrag. “I failed because I cared too much” or a story that ends in a promotion with no real loss.
• Blame. The client, the timeline or a coworker caused it. Brandeis International Business School’s career team advises taking responsibility for what you could have done differently instead of blaming others.
• A pattern, not an incident. Brandeis also warns against stories that make you sound like someone who makes “many mistakes in general”; pick a one-time event.
• No lesson, or a vague one. “I learned to communicate better” with no new habit attached.
• A core-competency disaster. An accountant whose failure is fudging numbers, or a nurse whose failure harmed a patient through carelessness, raises a question you cannot answer in two minutes.
• “I’ve never really failed.” Everyone has; this reads as either low self-awareness or low ambition.

How to Choose Your Failure Story

The right story is real, owned by you, from the past, recoverable, and not about the job’s core skill. Run every candidate story through this filter:

Test	Keep the story if…	Drop it if…
Real	Something measurably went wrong (a missed date, lost client, failed launch)	It is a strength in disguise
Owned	Your decision or action was a main cause	It was mostly someone else’s fault
Past	You have since applied the lesson at least once	It happened last month and is still unresolved
Sized right	The stakes match your level (bigger for senior roles)	It is trivial, or it would end a career in this field
Clean	No ethics, safety or legal breach	It involves dishonesty or a harmful shortcut

Build a small failure bank. Write down three to five candidates: one missed deadline, one project or launch that underperformed, one decision you got wrong, one mistake you caught and reported, and one time you were wrong about a person or a plan. Most failure variants below map to one of those five, so a bank lets you match the story to the exact wording you are asked. For how to build a full set of reusable stories, see our STAR method complete guide.

Match the size of the story to the job. An intern’s failure can be a group project or a missed class deadline. A director’s failure should involve a budget, a team, or a strategic bet. A tiny failure from a senior candidate suggests they are hiding the real ones.

The 4-Part Structure: Setup, Ownership, Recovery, Change

Every sample answer below uses the same four parts. It is the STAR method with the weight shifted toward what happened after the failure, which is what interviewers score.

Part	What to say	Rough share of the answer
1. Setup	The situation and your responsibility, in one or two sentences	Short
2. Ownership	What went wrong and the specific thing you did or missed	One or two sentences, said plainly
3. Recovery	What you did next: who you told, what you fixed, what you saved	The longest part
4. Change	The habit or system you now use, and one time it worked	Two sentences, with a result

Our rule of thumb (a writing guideline, not research): if Setup and Ownership take longer than Recovery and Change, the answer will sound like a confession instead of a comeback.

Three phrasing tips make the structure land:

• Use “I” in the Ownership part. “I assumed,” “I skipped,” “I didn’t check.” Save “we” for the recovery if it was a team effort.
• Name the cause, not the feeling. “I didn’t confirm the new permit rule” beats “I was overwhelmed.”
• End on a number or a repeat. “The next three launches hit their dates” proves the change stuck.

For more fully worked STAR stories across other behavioral themes, see our STAR method examples and behavioral interview questions and answers.

The Questions, With Sample Answers

The sample answers are original illustrations written by OphyAI. Replace every detail and number with your own; the numbers inside them are examples, not statistics.

1. “Tell me about a time you failed.”

Why they ask it: the base version, testing all four signals at once: accountability, judgment, recovery and learning.

Sample answer: “As an operations coordinator, I owned the move of our team’s scheduling onto a new software tool. I set a go-live date without running a test week, because I was confident the import would be clean. It wasn’t: on day one, about a third of shifts showed the wrong times, and two clinics were short-staffed that morning. I told my manager within the hour, called every affected supervisor myself, and rebuilt the schedule by hand that afternoon. Then I ran a proper one-week parallel test before switching again. Since then, every rollout I lead has a test period written into the plan, and the last two went live with no scheduling errors.”

Weak answers: a failure with no consequence, or a story where the software vendor gets all the blame.

Prepare the base version first: run it in OphyAI Interview Practice, where the follow-up questions will ask what you would do differently.

2. “What is your biggest failure?”

Why they ask it: “biggest” asks for scale. They want the failure that cost the most and to see whether you can discuss it calmly.

Sample answer: “My biggest failure was a customer retention program I designed at my last company. I was sure a discount for annual renewals would cut churn, and I convinced leadership to launch it to all customers at once instead of testing it on a segment. Churn barely moved, and we gave away margin on customers who would have renewed anyway. I owned the call in our quarterly review, pulled the offer after one quarter, and ran exit interviews that showed the real issue was onboarding, not price. We rebuilt onboarding, and churn in the next cohort dropped noticeably. Now I pilot any program on a small segment before a full launch.”

Weak answers: picking something small for a “biggest” question, which sounds evasive.

3. “Tell me about a mistake you made at work.”

Why they ask it: a mistake is smaller and more specific than a failure, so this is often an integrity check: did you catch it, report it and fix it? Deloitte and Delta Air Lines both list this wording in our guides.

Sample answer: “In my first year as a staff accountant, I posted a vendor invoice to the wrong cost center during month-end close. I noticed it two days later while reconciling, after the department report had already gone to its manager. I told my supervisor that morning, posted the correcting entry, and emailed the department manager a one-line explanation with the corrected numbers before she used them. Afterward I added a cost-center check to my posting routine and suggested a dropdown with only valid codes, which our controller adopted. I haven’t had a miscoded invoice since.”

Weak answers: a mistake you hid, or one you only fixed after someone else found it, unless you say so and show what changed.

4. “Tell me about a project that failed.”

Why they ask it: team failures are easy to hide inside “we.” They want your share of it.

Sample answer: “I was the analyst on a four-person team building a sales forecasting model for our regional offices. The project was cancelled after three months because the regional managers never used it. My part of that: I built what the brief asked for without ever sitting with a regional manager to see how they actually planned. When we did a post-mortem, they told us the model needed weekly numbers, and we had built monthly. I proposed and led a two-week rebuild around a weekly view, and three of five offices adopted it. Now I schedule user interviews before I write a line of a model.”

Weak answers: “The project failed because leadership changed priorities,” with nothing about your role.

5. “Tell me about a time you missed a deadline.”

Why they ask it: to test planning and, above all, how early you raised the flag. A missed deadline reported early is a very different story from one reported on the day.

Sample answer: “As a marketing coordinator, I committed to delivering a product launch email series in two weeks, before I’d confirmed when legal could review the copy. Legal needed five business days, which put us three days past the launch. I made it worse by waiting until day eight to say so. When I did, I offered my manager two options: send the first email on time with pre-approved copy, or delay the series. We sent the first email on time and the rest followed. Now I confirm every approver’s turnaround before I commit to a date, and I flag risks the day I see them.”

Weak answers: a deadline you missed because of someone else, or one with no cost.

Missed-deadline stories invite the follow-up “How do you prioritize?”, so practice both together in OphyAI Interview Practice.

6. “Describe a decision you made that you regret.”

Why they ask it: this is a judgment question. University of Massachusetts Amherst HR’s interview question bank uses a version of it: “Give me an example of a business decision you made that you ultimately regretted. What happened?”

Sample answer: “As a shift manager, I promoted a high-performing associate to team lead based on her sales numbers alone. I didn’t ask how she handled coaching or conflict. Within two months, two people on her team asked to transfer. I owned that it was my decision, met with her weekly to coach her on giving feedback, and paired her with an experienced lead. She improved, but I learned that strong individual results don’t predict leadership. Now I use a short trial period, where candidates run huddles and train a new hire before any promotion.”

Weak answers: a regret that is really about someone else’s decision, or a personal life choice.

7. “Tell me about a setback you faced. How did you deal with it?”

Why they ask it: a setback does not have to be your fault, so this version tests resilience more than ownership. UMass Amherst’s bank lists “Tell me about a particular work-related setback you have faced. How did you deal with it?” under resilience.

Sample answer: “I spent four months preparing a grant application for our nonprofit’s after-school program, and we were turned down. I asked the funder for reviewer feedback, which said our outcome measures were vague. I was disappointed, but I treated the feedback as a checklist: I worked with our program lead to add attendance and reading-level data, and I found two smaller funders with spring deadlines. We won one of those grants that year and reapplied to the original funder the next cycle with the stronger measures. Our proposals now start from the outcomes section, not the story.”

Weak answers: dwelling on how unfair the setback was.

8. “Tell me about a time you were wrong.” (Amazon-style)

Why they ask it: at companies with written values, this tests a named trait. At Amazon it maps to Earn Trust and Are Right, A Lot, which says leaders “seek diverse perspectives and work to disconfirm their beliefs.” See our Amazon interview guide for how the loop scores principles.

Sample answer: “As a product manager, I pushed to cut a feature our support team kept asking for, because the usage data showed few customers touched it. I was wrong about why. When the support lead pressed me, I looked again and found the people who used it were our largest accounts. I reversed my recommendation in the next planning meeting and said publicly that I had read the data too narrowly. We kept the feature and redesigned it. Since then I segment usage by account size before any cut, and I ask support to review roadmap changes before they’re final.”

Weak answers: “I was wrong to trust my team,” which turns your error into theirs.

9. “Tell me about a time you failed.” (Student or new grad)

Why they ask it: entry-level interviewers expect school, sports, part-time work or volunteering. They want the same four signals at a smaller scale. Our entry-level interview questions guide covers the rest of that round.

Sample answer: “In my sophomore year I failed my first organic chemistry exam. I had studied the way I did in high school, by rereading notes, and it didn’t work for problem-based exams. I went to office hours the next week, asked the professor to walk through what I got wrong, and joined a study group that worked practice problems under time limits. I finished the course with a B-plus. More importantly, I now study by doing problems, not rereading, and I used the same method to pass my statistics and accounting courses on the first try.”

Weak answers: “I got an A-minus instead of an A,” which is not a failure.

10. “Tell me about a time you failed.” (Software engineer)

Why they ask it: engineers ship bugs; interviewers want to see blameless post-mortem thinking and a fix to the system, not just the code. More examples in our software engineer behavioral interview questions.

Sample answer: “I shipped a database migration that locked a busy table for several minutes during business hours, and our checkout page timed out for customers in that window. I had tested it on a staging database that was a fraction of production’s size, so I never saw the lock. I rolled it back, posted an incident summary in our team channel within the hour, and wrote the post-mortem. The fix went beyond my migration: I added a check to our deploy pipeline that flags migrations on large tables and requires an off-peak window. That check has caught two risky migrations from other engineers since.”

Weak answers: “QA should have caught it.”

If a live coding round follows the behavioral round, OphyAI Coding Interview runs as Coding Copilot in the desktop app.

11. “Tell me about a mistake you made.” (Nurse or healthcare)

Why they ask it: healthcare interviewers want to know you follow reporting procedures and learn from near misses. Choose a caught error or a process failure, never carelessness that harmed a patient. See our registered nurse interview questions for related questions.

Sample answer: “As a new grad on a med-surg unit, I was about to hang an IV antibiotic when my barcode scan flagged a mismatch. I had grabbed the bag for the patient in the next room, whose name was similar. Nothing reached the patient, but it was my error: I had pulled two patients’ meds at once to save time. I told my charge nurse right away and filed a near-miss report through our unit’s safety reporting system. I stopped batching meds for different patients, and our unit added name-alert stickers for similar names after several of us raised it. I’ve had no near misses since.”

Weak answers: a story that skips reporting, or one where the patient was harmed through a shortcut.

12. “Tell me about a time you failed to hit a target.” (Sales)

Why they ask it: every salesperson misses sometimes. They want to hear whether you diagnose the miss or just blame the territory. Our sales representative interview questions cover the rest of a sales loop.

Sample answer: “In my first full year as an account executive, I missed my third-quarter quota by a wide margin. Looking back at my pipeline, I had put most of my time into two large deals and let my smaller accounts go quiet. Both large deals slipped to the next year. I owned that in my review with my manager, rebuilt my week so that mornings went to pipeline generation no matter what, and set a rule that no single deal would be more than a third of my forecast. I hit quota in each of the next four quarters.”

Weak answers: “The market was down,” or a miss you never explain.

13. “Tell me about a time you let a customer down.” (Retail or customer service)

Why they ask it: customer roles test recovery: what you did once you knew. Our customer service representative interview questions guide covers related questions.

Sample answer: “At a furniture store, I promised a customer her sofa would arrive before a family event without checking the warehouse schedule. It was due three days after. She called upset, and she was right to be. I apologized, told my manager, and called the warehouse to ask if any floor model or incoming truck could cover it. A matching floor model was available, so we delivered that on time and swapped in her new sofa the next week. Since then I never quote a date until I’ve checked the delivery system with the customer standing there.”

Weak answers: blaming the warehouse, or a story with no fix for the customer.

14. “Tell me about a time your team failed.” (Manager)

Why they ask it: managers own their team’s results. They want to hear you take the blame publicly and fix the process. See our manager interview questions for the rest of a management loop.

Sample answer: “My team of six support agents missed our response-time target for an entire quarter after we took on a new product line. I had agreed to the extra volume without asking for headcount or retraining time, so the miss started with my planning. I told my director that directly in our quarterly review, then did three things: cross-trained two agents as product specialists, built a triage queue so simple tickets didn’t wait behind complex ones, and made a staffing case with the volume data. We were back on target within two months, and I now model ticket volume before agreeing to any scope change.”

Weak answers: naming the agent who “dropped the ball.”

15. “What’s the biggest professional failure in your career?” (Senior or executive)

Why they ask it: at senior levels, they want a strategic bet with real stakes and evidence that you changed how you decide. Palantir, for example, probes your biggest failure in the hiring manager round, per our Palantir interview guide.

Sample answer: “As head of product at a mid-size software company, I championed expanding into a new customer segment. I committed a full team for a year based on a handful of enthusiastic prospects, without testing whether they would pay at our price. We signed far fewer customers than planned and wound the effort down. I presented the post-mortem to our board myself and helped move the team onto our core product, where they shipped two features customers had requested for a year. The lesson I now apply is a staged bet: a small team, a paying pilot and a clear stop rule before any big investment.”

Weak answers: a failure that cost little, or one blamed on the board or the market.

Follow-Up Questions to Expect

Strong interviewers dig after your first answer, and the follow-ups are where rehearsed stories fall apart. Prepare a one-line answer for each:

Follow-up	What a strong answer includes
What would you do differently?	The specific step you skipped, not “communicate more”
How did your manager react?	Honest description, without casting them as the villain
Has it happened again?	A clear no, or a time the new habit caught it
What did others on the team learn?	The process change you drove, if any
Why didn’t you see it coming?	The assumption you made and why it seemed reasonable then
Tell me about another one.	A second story from your bank, ideally a different type

How to Practice These

Pick two stories from your failure bank, write the four parts for each in bullet points, and say them aloud until each runs under two minutes and survives the follow-ups above.

• OphyAI Interview Practice runs voice or text mock interviews with follow-up questions, a transcript and per-answer feedback, so you can check that your Recovery and Change parts carry the answer; the free plan’s 5-credit grant covers one session capped at 15 minutes.
• OphyAI Interview Copilot gives real-time answer suggestions and a live transcript during Zoom, Microsoft Teams and Google Meet interviews, in 35 languages, which can help you keep your story on structure when the question arrives in an unexpected form.

There is no $9 OphyAI plan: the Basic plan was retired in July 2026, and Pro is $29 a month.

Start practicing →

Frequently Asked Questions

What is the best answer to “Tell me about a time you failed”?

The best answer describes one real failure you owned, states the cause in plain words, spends most of the time on how you recovered, and ends with a habit you changed and evidence it worked. Interviewers remember the recovery and the change, so those parts should be the longest and most specific.

What failure should I talk about in an interview?

Choose a one-time failure where your decision was a main cause, the stakes fit your level, and you have since applied the lesson. Avoid anything involving dishonesty, safety or legal problems, and avoid a failure in the core skill of the job you want, because it raises doubts you cannot resolve in one answer.

Can I say I have never failed?

No. Claiming you have never failed reads as low self-awareness, low ambition, or evasion, and interviewers will usually press until you name something. Everyone has missed a deadline, misjudged a decision or seen a project underperform. Prepare a real story in advance so you are not forced to improvise one under pressure.

How long should my failure answer be?

Aim for about 90 seconds to two minutes when spoken. Keep the setup to one or two sentences and the admission to one or two more, then give the recovery and the lasting change most of the time. If the interviewer wants more detail, they will ask follow-up questions, which is better than a long confession.

Is “biggest failure” different from “a time you failed”?

Slightly. “A time you failed” lets you choose any real failure, while “biggest failure” asks for scale, so a small story can sound evasive. For “biggest,” pick the failure with the highest stakes you can discuss calmly, and make sure the change at the end is equally substantial, such as a new process others now use.

Can I use a personal or school failure instead of a work one?

Yes, if you are a student, a new graduate or changing careers, or if the interviewer does not specify work. Use a class, sport, campus job or volunteer project with a clear loss and a clear change. Experienced candidates should usually pick a work story, because interviewers want to see how you behave on the job.

How does OphyAI help with this question in a live interview?

Interview Copilot listens through a live transcript and suggests answer points in real time during Zoom, Microsoft Teams and Google Meet interviews, which can remind you of your Setup, Ownership, Recovery, Change structure when the question comes in a variant you did not expect. Rehearse your stories first in Interview Practice so the suggestions point to a story you already own.

Related Guides

This question, or a “mistake you made” variant, shows up in behavioral rounds at these employers:

• Amazon interview guide
• Google interview guide
• Microsoft behavioral interview guide
• Procter and Gamble interview guide
• Deloitte interview guide
• Johnson and Johnson interview guide
• Delta Air Lines interview guide
• Palantir interview guide

More single-question and pillar guides:

• Top 50 interview questions and answers
• How to answer “What is your greatest weakness?”
• How to answer “How do you handle stress?”
• Common behavioral interview questions

Sources and verification notes

Checked November 2026. Sample answers are original illustrations written by OphyAI, not quotes from employers or candidates, and the figures inside them are examples, not statistics. The Muse blocked our fetch, so it is not cited.

• Arizona State University, Fulton Schools Career Center, “Talking about failure” (Joyce Donahue): published August 2018, updated June 2023; the resilience framing and the “plan that did not work” quote.
• Brandeis International Business School, Career Strategies and Engagement, Answering “Tell me about a time when you failed”: October 2022; choosing a minor, fixable, one-time mistake, not blaming others, and the “many mistakes in general” warning.
• University of Warwick Careers, How to answer “Tell me about a time you failed at something”: revised April 2025; “assessing how you respond to failure, not the failure itself.”
• Amazon Leadership Principles: the Ownership, Earn Trust and Are Right, A Lot wording quoted above.
• University of Massachusetts Amherst Human Resources, Behavioral Interview Questions: Decision Making and Resilience: the employer question bank behind variants 6 and 7.