How to Answer 'Tell Me About a Time You Failed' in a Job Interview

A structured way to pick a real failure, explain what you changed because of it, and still leave the interviewer room to ask follow-up questions.

By Tobias Lindqvist · Oct 26, 2026 · 8 min read

Featured image for "How to Answer 'Tell Me About a Time You Failed' in a Job Interview"

Interviewers ask about failure to find out whether you can name a mistake plainly, explain what caused it, and show what you do differently now. The strongest answers describe a real, recent failure you personally caused, the specific correction you made, and a measurable result afterwards.

Avoid disguised brags like "I care too much about quality" — they read as evasion, and most interviewers will push back on them.

Why Interviewers Ask This

This question tests accountability and coachability — whether you can describe a decision you got wrong without blaming a manager, a vendor or "the process", and whether the failure actually changed how you work.

Interviewers listen for three things: that the failure is real and yours, that you understood the cause rather than the symptom, and that you can name the specific change you made afterwards. The red flags are easy to spot once you know them: "I can't think of one", a failure that is secretly a compliment, a story where everyone else is at fault, or a failure with no correction attached.

How heavily it is weighted varies by employer and field. Hiring managers in engineering, healthcare, aviation and finance often probe hardest, because those industries run formal post-incident reviews and want to hear you speak that language. A first-round recruiter screen may simply be checking that you do not get defensive.

Sample Questions & Answers

Tell me about a time you failed.

Marketing coordinator, B2B software

"As a marketing coordinator at a software company, I owned the monthly customer newsletter. I was asked to launch a win-back campaign to 40,000 lapsed users in two weeks. I built the segment myself and skipped the seed test to make the date. The main call-to-action link pointed to a dead page, and 12,000 emails went out broken. I stopped the send, shipped a corrected version within three hours, and wrote a two-step pre-send check that requires a seed test and a link click. Win-back signups still finished the month at 310, and no campaign has gone out untested since."

What's the biggest mistake you've made in your career?

Shift supervisor, distribution center

"As a shift supervisor at a regional distribution center, I was responsible for staffing holiday peak. I hired six seasonal pickers in one week without asking the standard working-at-height question, because I wanted people on the floor fast. Two of them couldn't safely work the mezzanine, so my shift ran short for three weeks and we missed daily pick rate seven times. I told my operations manager the day I realised, rebuilt the interview checklist to include the physical requirements, and ran the remaining hires through it. The next peak we filled 14 roles with no mismatches."

Tell me about a project you led that missed its goal.

Product manager, healthcare software

"I was the product manager for a scheduling tool used by medical clinics. My target was 50% of clinic customers on the new booking screen within a quarter. I relied on in-app prompts and a release note instead of talking to the practice managers who actually control rollout, and we finished the quarter at 18%. I called 15 practice managers myself, learned they needed a printed staff guide and a scheduled switchover date, and built both. Adoption reached 64% the next quarter, and I now start every rollout with five customer calls."

Describe a time your team failed. What was your part in it?

Project engineer, commercial HVAC

"On a commercial HVAC retrofit, I was the project engineer responsible for submittals. The team agreed informally that someone would confirm the rooftop unit dimensions, and I assumed it had been done. It hadn't. Two units arrived four inches too wide for the curb, and installation slipped 11 days, which cost the job its early-completion bonus. My part was never writing that check down as an owned task. I built a one-page responsibility matrix for long-lead equipment and walked it through the next kickoff. On the following three retrofits, nothing slipped."

Tell me about feedback you disagreed with and later accepted.

Support team lead, e-commerce

"My director told me my support team's replies were too long. As the support team lead at an e-commerce retailer, I believed detail prevented repeat tickets, so I pushed back and changed nothing for two months. First-response time drifted from under two hours to over five. I pulled 50 tickets, read them end to end, and found she was right — most replies buried the fix in the third paragraph. I rewrote our macros so the answer comes first, coached the team for a week, and first-response time was back under two hours within a month."

Sample Answer Script

Full spoken answer — staff accountant, manufacturing

"In my second year as a staff accountant at a manufacturing company, I owned the fixed-asset schedule for month-end close.

When my senior left, I was asked to take over the quarterly close workpapers on top of my regular work, with the quarter ending three weeks later.

I decided I could absorb it without asking for help. I didn't reconcile the construction-in-progress account before handing the file to the controller, because I was out of hours and assumed the balance hadn't moved. It had — around $240,000 of completed projects were still sitting in it. The error went into the draft statements, our external auditors caught it, and I had to restate the schedule and explain the variance.

I told the controller the same morning the auditors flagged it, instead of waiting for the review meeting. Then I rebuilt the close checklist into a 12-item list with a sign-off line for every reconciliation, and I started flagging capacity in writing on the Monday of close week.

The next three quarterly closes went through with zero audit adjustments, and that checklist is still what the team uses. The bigger change for me is that I now say out loud when a deadline and my capacity don't match, instead of hoping I can make up the difference."

Before You Walk In

  1. Choose one failure from the last five years and write the one-sentence version of what went wrong.
  2. Write down the single number that shows the result after your fix — a percentage, dollar amount, count, or time period.
  3. Read your answer aloud once with a timer and cut it to under 90 seconds.
  4. Check that no former colleague is named or identifiable in the story.
  5. Write one sentence answering the likely follow-up: "What would you do differently now?"
  6. Underline the competency in the job posting your failure maps to, such as deadline management for a project coordinator role.
  7. Draft a second, shorter failure story in case the interviewer asks for another example.
  8. Print two copies of your resume and mark the bullet point your failure story connects to.

Frequently asked questions

What if I've never had a big failure at work?

You do not need a catastrophe. A missed deadline, a report you sent with the wrong figures, a client call you handled badly, or a hire that did not work out are all usable. Interviewers are testing whether you can own a mistake and name the correction, not how dramatic the mistake was. Saying "I can't think of one" reads as low self-awareness.

Can I use a failure from school or an internship?

Yes, if you have little work history. A failed group project, a lab result you had to redo, or a campus event that under-attended all work, provided you explain what you changed afterwards. If you have two or more years of full-time experience, interviewers generally expect a workplace example instead, and some hiring managers will ask you for one directly.

Should I bring up being fired or laid off?

Not as your answer to this question. A termination is a separate conversation, usually prompted by a question about why you left a role. For "tell me about a time you failed", pick a contained incident you fixed while still in the job, so the story ends with the improvement rather than with your departure.

How long should my answer be?

Aim for 60 to 90 seconds. That is enough for situation, task, action and result without the interviewer losing the thread. Spend the least time on the failure itself and the most on the correction and the outcome. If the interviewer wants more detail on what went wrong, they will ask, and that follow-up is a good sign.

Is it a mistake to use the same story for 'What's your biggest weakness?'

It is usually better to have separate stories. A weakness is an ongoing tendency you are managing; a failure is a specific event with a date and an outcome. Reusing one story for both can make your experience sound thin, especially in panel interviews where different people ask each question. Prepare at least two distinct examples from different roles or projects.

Written by

Tobias Lindqvist

Tobias writes on trades, apprenticeships, and the kinds of careers that don't start with a resume. He's interested in skill as a form of dignity, and in how little the discourse around work usually accounts for hands.

More in Job Search & Interviews

Featured image for "How to Write a Resume for a Government Job"
Job Search & Interviews

How to Write a Resume for a Government Job

A government resume is judged against a written standard, not against other candidates' design sense. For federal jobs, that standard now includes a hard length limit: a federal resume must be two pages or less and must explain why you are qualified for the job (U.S. Office of Personnel Management, USAJOBS Help Center, undated), and USAJOBS will not let you upload or build a resume longer than two pages (U.S. Department of the Treasury, undated).

Harlan Voss · 8 min read

Featured image for "How to Negotiate a Job Offer You Weren't Expecting to Get"
Job Search & Interviews

How to Negotiate a Job Offer You Weren't Expecting to Get

An offer you didn't expect is still an offer, and it is negotiable on the same terms as one you chased for months. The order of operations is the same: ask for the full terms in writing, ask for a few business days to review, check the role's pay range against public data for your metro area, then make one or two specific asks rather than a vague request for "more".

Marisol Teague · 6 min read

Featured image for "How to Answer 'What Are Your Salary Expectations' in a Job Interview"
Job Search & Interviews

How to Answer 'What Are Your Salary Expectations' in a Job Interview

Answer with a researched range for your job title and your metro area, a one-line reason for that range, and a signal that you'll weigh the whole package. A single number boxes you in; "whatever you think is fair" tells the interviewer you did no homework.

Priya Nandakumar · 8 min read

Featured image for "How to Write a Cover Letter for a Career Change"
Job Search & Interviews

How to Write a Cover Letter for a Career Change

A career-change cover letter does the work a resume cannot: it explains why someone who spent six years managing a retail store is applying for an operations analyst opening, and which parts of that experience transfer. Build it around the employer's problem rather than your biography, and name two or three measurable results from your old field that map directly onto the new one.

Tobias Lindqvist · 7 min read