Career
Telling failure as evidence
Interviewers read what you did that week, not the lesson
Nobu Sato4 min read
When an interviewer asks about a failure, the useful answer is what you did at the time. The lesson you drew later tells them almost nothing. Yet most people come in with an answer shaped like this: it failed, I learned X, afterwards I improved. That answer is useless, and the interviewer knows it.
What they're looking at
When I ask about failure in an interview, I'm looking at the patterns layer: what you're like under pressure. That layer is invisible when things go well. The only way to check it is through one real failure.
I don't want your retrospective. I want what you did at the time. The week it went wrong, what was your first move? Who did you tell, and who didn't you tell? When did you realize it wasn't going to work, and how long did you wait after that? What were you feeling?
The retrospective comes pre-packaged. "I learned the importance of communication" is a sentence everyone says, and it carries no information. "It took me two weeks to tell my boss, because I thought I could still save it" carries plenty. It says that under pressure you pull inward, and that you're too optimistic about your own judgment.
Interviewers learn from what you did that week, not from the lesson
Answers to “Tell me about a failure,” split into two ways of telling it, using the examples in this article
The interviewer is matching you against seven patterns. Tell them what you did that week, not what you learned.
Seven patterns, and which one they're matching
There are seven common ways people derail under pressure: over-caution, arrogance, mistrust, drama, avoidance, perfectionism, people-pleasing. While you tell your failure story, the interviewer is matching you against them.
You can't hide it, and you shouldn't try. Everyone has one or two of these. So does the interviewer. Having one is fine. What they're judging is whether yours adds to a risk the team already carries. A team that already has two avoiders can't take a third. A perfectionist might actually balance it.
So saying plainly what you did at the time is much safer than a polished lesson. Tell the truth and they judge fit. Tell the packaged version and they judge the packaging.
How to prepare
Pick a real failure. The "I'm too much of a perfectionist" kind doesn't count.
Tell it in the order it happened. Skip the logical structure. What happened, what you did, what happened next.
Include the emotion. "I was panicking" is more believable than "I calmly assessed the situation."
Save the lesson for the end. One sentence, tied to a specific behavior: "Since then I have a rule. Three days without progress and I escalate."
Some Japanese interviewers still score against the "failure, reflection, growth" template, and the real version may not earn you points with them. Then the question becomes whether you want to join a company that interviews by template. If you do get rejected for it, reading a rejection is a separate post.
The failure story you have ready: is it about what you did at the time, or about what you thought afterwards?
What I look for from the interviewer's side, the failure question included, is in After the resume screen: what I look for in an interview.