Tell Me About a Time You Failed: Example Answers for Students
“Tell me about a time you failed” is not the resilience question wearing a different hat, although it is often answered as if it were. Resilience is about what you did after something went wrong. Failure is about the thing that went wrong being your fault, and the answer is scored on how honestly you own it, how precisely you can say why it happened, and what is different now. Students dodge all three, and the dodge is audible in a ninety-second Kira recording.
What the interviewer is listening for
Students hear “failed” and either reach for a disaster that was nobody’s fault (the venue cancelled, the teacher was unfair) or for a failure so small it is really a humblebrag (I got 89 instead of 95). Both miss. The interviewer is not scoring the size of the failure. They’re listening for three things:
- Ownership, stated plainly. A sentence where you say what you did wrong, in the first person, without a “but” attached. Not “mistakes were made,” not “the group didn’t communicate,” but “I didn’t check.”
- A real diagnosis. Why it happened, one level deeper than the obvious. “I ran out of time” is a symptom. “I started the week before because I thought it was a two-day job, and it was a ten-day job” is a diagnosis.
- What changed, specifically. A rule, a habit or a decision you now make differently, with a way to tell it took. “I learned a lot” is nothing. “Now I ask for the rubric on day one” is something.
The STAR structure still works, with one change: the Result is the failure itself, told without softening, and the reflection after it carries more weight than in any other question. Put a number on the failure, too. “It didn’t go well” is the same gap we see in most first runs, a result with no weight; “it lost forty dollars” or “we got 71” tells the interviewer exactly how big it was, and makes the ownership sentence that follows sound like it cost something.
Failure versus resilience: which story goes where
The two questions share a story bank, which is why they get confused. The difference is where the weight sits. In a resilience story, the setback can be anyone’s fault, and the interviewer is listening for the second day: the concrete thing you did next. In a failure story, the setback has to be yours, and the interviewer is listening for the autopsy: what you did wrong, why, and what is different. A resilience story that ends “and then I made the team” is finished. A failure story that ends there has skipped the part that was asked for.
Practically: if your best story involves something going wrong that you caused, keep it for the failure question and tell it with the cause in the front. If your best story involves something going wrong that happened to you, it is a resilience story, and telling it as a failure will sound like you are apologising for weather.
Three example answers
In Grade 11 I ran a bake sale and raffle for our school’s Terry Fox week, and it lost about forty dollars. I’d done the raffle prizes first because that was the fun part, and I spent about $180 on them before I’d worked out how many tickets we could realistically sell in a school of six hundred. We sold ninety-two. The honest reason is that I never made a budget, because a budget felt like something adults do and I assumed enthusiasm would cover it. The part I’m least proud of is that when the council president asked how it went, my first instinct was to say “the turnout was low,” which is true and also not the reason. I went back the next day and told her the real one. Since then I don’t spend anything on an event until I’ve written down the break-even number, and for the spring dance that number was 140 tickets, and we sold 170. I still think the raffle prizes were good. That was never the problem.
Last year I was in a group of three for a history presentation and I volunteered to build the whole slide deck because I thought I was the best at it, which I probably was. Then I got a shift added at work and a chemistry test moved, and I didn’t say anything to the group because I figured I’d catch up. The night before, the deck was eleven slides out of twenty and the other two found out at about ten p.m. We presented something pretty rough and got 71, and one of them had a 90 average and was genuinely upset. What I got wrong wasn’t the deck. It was that I had about four days of warning that I was in trouble and spent all four of them not telling anyone, because telling them felt like admitting I couldn’t handle it. The rule I made is that if I’m going to be late on something that other people are counting on, they hear it the day I know, not the day it’s due. I’ve had to use that rule twice since, and both times the reaction was basically “okay, thanks for saying,” which is not what I had been afraid of.
I worked at a day camp last summer, and one Wednesday I miscounted my group getting back on the bus from the pool. I had thirteen kids and I counted twelve, then counted again and got thirteen and decided the first count was the wrong one. It was the second count that was wrong. A kid was still in the change room, and another counsellor found him about five minutes later. Nothing happened to him, but it was the worst five minutes of my summer. The camp director sat me down and I told her exactly what I’d done, including the part where I’d chosen the count I liked better. What I understood afterwards is that I’d been treating the headcount as a box to tick rather than as the actual point of my job. For the rest of the summer I counted by name, out loud, every time, which the kids thought was funny and which took about forty seconds. I’d rather be the counsellor who is a bit annoying about the count than the one who got lucky.
Picking the failure: too small, too big, just right
- Too small. A mark that dropped from 94 to 88, a race you came second in, a club you did not get elected to. These read as a student who has never actually failed, or as a student who did and is hiding it. Either way the interviewer learns nothing.
- Too big. A failure that hurt someone badly, involved dishonesty, or that you are clearly still in the middle of. The interviewer cannot probe it without feeling cruel, and an admissions interview is not the place to work it through. If it is still raw, it is not ready.
- Just right. Something you were responsible for that went visibly wrong, that cost something real (money, a mark, someone else’s trust, a scary five minutes), that is over, and where you can name the cause without pointing at anyone else. All three examples above sit here.
The one that quietly backfires
The story that goes: I failed, but actually it turned out to be the best thing that ever happened to me, because it led directly to this great success. Told that way, the failure evaporates about twenty seconds in and the interviewer is left listening to a success story they did not ask for. It also signals something they notice: that you could not stand to leave a failure on the table as a failure.
The other version blames the weather. The group didn’t communicate, the teacher changed the rubric, the venue fell through. Some of that may be true, and a sentence of context is fine. But if the cause of the failure lives entirely outside you, you have told a resilience story badly, and the interviewer has learned that when things go wrong you look outward first.
Other ways the question gets asked
- Tell me about a mistake you made and what you learned.
- Describe a time you let someone down.
- Tell me about a time you were wrong.
- What is your biggest regret from high school?
- Tell me about a time you did not meet a goal you set.
- Describe a time you received criticism you deserved.
Same story bank, same three parts. “Let someone down” wants example two: the cost is to another person, so name them by role and say what it did to them. “A time you were wrong” wants the diagnosis to be about a belief, not a task: what you thought was true, what turned out to be true, and the moment you found out. “Criticism you deserved” is the same story told from the moment someone else said it to you, and the ownership beat is agreeing with them. Prepare one story with a clean cause and a clean change and you can bend it to any of these inside a thirty-second prep window.
Where to go from here
If your story is about something that went wrong but not about your fault, it belongs in the resilience guide, which shows how to tell it from the second-day angle. If the failure was a group one, the teamwork guide explains how to keep the “I” in it without turning the others into villains, and the greatest weakness guide is the same honesty test asked in a different way. If you cannot yet say the ownership sentence out loud, build the story first: AcceptMe’s Story Bank coach asks about the failure, has you relate it to something that really happened, and follows up on the cause until it is in your words; most students are surprised that rough, half-finished answers are all it needs to work with. Then put the story under a clock: AcceptMe’s interview tool will ask you one of the variations above unseen, one take, and show you the transcript with the coach’s notes on whether the ownership sentence was actually in it or whether you talked around it, which is much easier to see on paper than to hear in your own head.
Keep reading
- Tell Me About a Time You Showed Resilience: Examples Three example answers to 'tell me about a time you showed resilience' for students, the story shapes that work, and the one that quietly backfires.
- Greatest Weakness: How to Answer in a University Interview An honest weakness with evidence and a fix already running: three student answers, the ones to avoid, and how it fits a 60-second Kira clock.
- The STAR Method for University Interviews (With Examples) How the STAR method works in a university interview, two full worked examples, and why most student answers get the 'A' wrong.