面試被問到失敗經歷：為何迴避問題總會適得其反

Originally published at https://easedit.co/blog/005-tell-me-about-a-time-you-failed

Tell Me About a Time You Failed — Why the Dodge Always Backfires

"I once stayed too late trying to perfect a project, and I suppose that was a mistake."

That's not a failure story. The interviewer knows it. You know it. And the moment that sentence ends, the interview takes a turn you can't recover from.

Why People Dodge It (And Why That's Worse)

The instinct is understandable. You're trying to make a good impression. Describing something that went wrong feels like handing them a reason to reject you.

But interviewers aren't asking this question because they think you've never failed. They're asking because everyone has, and how you respond to failure tells them more about you than most other questions.

Evasion — choosing something trivially small, framing a success as a mistake, or describing a situation where nothing was really your fault — doesn't protect you. It signals a lack of self-awareness and an inability to take ownership. Both are bigger concerns than the actual failure would have been.

What a Strong Answer Demonstrates

Three things:

Ownership. You can say "I made a mistake" clearly, without passive framing, without distributing the blame to circumstances or colleagues.

Recovery. You didn't stop at the failure. You took specific steps to address it. The interviewer wants to know what you did after things went wrong — that's the part of the answer that earns their respect.

Learning applied. The lesson didn't just stay as a lesson. You changed something about how you work, and you can point to where that change has shown up since.

Using STAR to Structure the Answer

STAR works well here because the four parts map cleanly onto what the interviewer needs:

Situation: What was the project, role, or context? One or two sentences — don't dwell here.

Task (what went wrong): What specifically failed, and what was your role in it? Be honest. "I underestimated the time needed" or "I made a call that turned out to be wrong" is clear and direct.

Action — the recovery: This is the main event. What did you do once you recognised the problem? Did you seek feedback? Rebuild the process? Bring in support? The more specific the steps, the stronger the answer.

Result + lesson: What was the outcome? What did you take away, and how have you applied it?

Choosing the Right Story

The failure should be real — but sized appropriately. Not a catastrophic mistake that cost a company significantly. Not something so minor that it barely counts. Something genuine, with enough weight that recovery took real effort, and with a lesson that actually changed how you work.

If you're an early-career candidate, failures from university, internships, or independent projects all qualify.

A Benchmark Answer

"In my previous role as a product manager, I led the launch of a new software feature. I underestimated how long users would need to get comfortable with it — I hadn't resourced the training materials properly. The result was a spike in support requests in the first two weeks, and a number of frustrated users who felt unprepared.

When I realised what had happened, I gathered feedback from the support team and ran three additional training sessions myself. I also rewrote the documentation from scratch with practical examples instead of technical explanations.

Support requests dropped 40% over the following month. Since then, user preparation is one of the first things I scope in any product launch — it's now built into the timeline from day one, not added at the end."

The One Thing to Remember

The failure is not the answer. The recovery is.

Practise your interview with easedit.co — voice AI, from $29, no data stored.

Want to put this into practice?

easedit.co lets you run a full AI-powered mock interview, get scored feedback on your answers, and track your improvement over time. No signup required to try your first session.