Behavioral questions (answer with STAR)

How to Answer "Tell me about a time you failed." (With Sample Answers)

By Andrew Johnson · Updated October 5, 2026

The interviewer wants proof that you can own a real setback without excuses and that you changed how you work because of it.

In short: Pick a genuine, work-related failure with moderate stakes — a missed goal, a project that fell short, a plan that didn't work. Tell it with STAR, spend most of the answer on what you did and what you learned, and finish with how you work differently now. The lesson is the point; the failure is only the setup.

Also asked as: “Describe a time you failed.” · “Tell me about a time you didn't meet a goal.” · “Give an example of a project that didn't go as planned.” · “What's your biggest failure?”

Why do interviewers ask “Tell me about a time you failed”?

This is a behavioral question — CareerOneStop describes behavioral interviews as questions about how you have handled challenging work-related situations. Everyone fails at something, so the interviewer isn't checking whether you have failed. They are checking self-awareness, honesty, and whether you learn — and whether you'll take a risk without hiding the result when it goes wrong.

How to answer: the STAR + Lesson formula

MIT's career office defines STAR as Situation, Task, Action, Result and suggests spending most of the answer on your actions. For a failure question, add one closing line on what you changed.

Step	What to say	Example line
Situation (≈20%)	Set the scene in one or two sentences: the goal and why it mattered.	'I was leading our team's first webinar series, and the goal was to generate new leads for sales.'
Task (≈10%)	State what you were personally responsible for.	'I owned the topics, the speakers, and the promotion plan.'
Action (≈60%)	Say what you did, where it went wrong, and what you did once you saw it going wrong. Use 'I', not 'we'.	'I chose topics I found interesting instead of asking sales what prospects asked about. When registrations stayed low, I interviewed three account reps and rebuilt the schedule.'
Result + lesson (≈10%)	Admit the outcome honestly, then name the habit you changed and a later moment it paid off.	'The first series missed its goal. Now I validate every campaign idea with the people closest to customers first — and the next series did much better.'

Sample answers to “Tell me about a time you failed” by job type

Illustrative answers — swap in your own experience. An answer you can back up with a real story beats a polished one you can't.

Entry-level / new graduate

Interviewing for a junior project coordinator role.

“In my final year I led a four-person capstone project, and I failed to get it delivered on time. I assumed everyone would flag problems on their own, so I didn't set check-ins. Two weeks before the deadline I found out one part hadn't been started. I reorganized the remaining work, took on part of it myself, and we asked our professor for a one-week extension, which cost us a grade penalty. Since then I set a short weekly check-in on any group project, even when things seem fine. In my internship that habit caught a missing approval early enough to fix it.”

Career changer

Former retail manager applying for an HR coordinator position.

“When I managed a retail store, I tried to fix high turnover by redesigning our new-hire schedule, and it didn't work. I had assumed people were leaving because of hours, so I never asked them. A few months later turnover was just as bad. I started doing short exit conversations and learned that new hires felt thrown onto the floor without training. I built a simple first-week buddy system with my senior associates, and people started staying longer. The lesson I carry into HR is to ask people before designing a solution for them.”

Nurse / healthcare

Registered nurse applying to an outpatient clinic.

“As a newer nurse I volunteered to lead a patient-education project on our unit: a discharge handout for heart failure patients. I wrote it in clinical language I thought was clear, and our follow-up calls showed patients still weren't sure about their daily weight checks. That one was on me. I asked our educator for help, rewrote the handout at a plainer reading level, and tested it by having patients explain it back to me before discharge. Now I use teach-back with every patient, not just on handouts, and I check understanding instead of assuming it.”

Sales / customer service

Applying for an inside sales role.

“In my second year in sales I lost a large renewal I had assumed was safe. The account had been happy, so I only checked in near the renewal date. By then a competitor had been working with their new operations lead for months, and I didn't even know the contact had changed. I tried to win it back with a discount, but they had already decided. Since then I map every key account's decision-makers twice a year and set check-ins well before renewal. I haven't been surprised by a contact change since.”

Tech / analyst

Software developer interviewing for a mid-level role.

“I once shipped a feature that broke checkout for some mobile users for most of an afternoon. I had tested it thoroughly on desktop and skipped testing on older mobile browsers because the deadline was close. When support tickets came in, I rolled the change back, wrote up what happened, and fixed the bug the next morning. Then I added automated tests for the browsers we support so nobody would have to remember to do it by hand. My takeaway was that skipping a check under deadline pressure is a decision, and I now say it out loud to my lead instead of making it quietly.”

What to avoid

A fake failure ('I worked too hard'). Interviewers hear it constantly and read it as evasion, which costs you the trust the question is testing.
Blaming teammates, a manager, or bad luck. The question is about ownership. If the failure was someone else's, it's the wrong story.
A failure that disqualifies you for this job. Don't choose a story that touches the core skill of the role, like a safety or ethics lapse.
Stopping at the failure. Without the lesson and what changed, the answer ends on a negative note.

How to prepare

Choose a story from the last few years so the 'what I do now' part is current.
Medium stakes work best: a real consequence, but not one that harmed people or the business badly.
Practice saying the failure in one plain sentence — no softening words — before moving on to the lesson.

Say your answer out loud

Practice this question with a live AI interviewer that listens, asks a follow-up, and gives feedback.

Practice my interview

Make your resume tell the same story

Interviewers read your resume before they ask this. Tailor it to the job so your answer and your resume match.

Tailor my resume

FAQ

What is a good answer to 'Tell me about a time you failed'?

A real work failure with moderate stakes, told with STAR: what the goal was, what you were responsible for, what you did when it went wrong, the honest outcome, and the habit you changed afterwards.

Can I say I've never failed?

No. It reads as a lack of self-awareness or a lack of challenge. If you're early in your career, use a school, volunteer, or part-time job example.

How is 'tell me about a time you failed' different from 'tell me about a mistake'?

A failure is usually a goal you didn't reach, often for several reasons. A mistake is a specific error you made. For failure, focus on what you learned about your approach; for a mistake, focus on how you caught it and fixed it.

How long should my failure story be?

Around one to two minutes. Keep the setup short and spend most of the time on your actions and what changed.

This question in role-specific interviews

Project manager interview questions Software engineer interview questions Account executive interview questions Registered nurse interview questions