Nobu Sato

Telling failure as evidence

Telling failureas evidence

The interviewer says: tell me about a time you failed. Most people have an answer ready in the shape of: 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. It can only be checked 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 is packaged. "I learned the importance of communication" is a sentence everyone says; it carries no information. "It took me two weeks to tell my boss, because I thought I could still save it" carries plenty: under pressure you pull inward, and you're too optimistic about your own judgment.

The retrospective· I learned the importance of communication· Afterwards I improved the process· The experience helped me growWhat you did at the time· Took two weeks to tell my boss· Quietly asked a colleague first· Didn't sleep the night I realizedThe right side carries information

Fig.1Two ways to tell it. The left is a packaged conclusion anyone can say. The right is actions and emotions at the time, which the interviewer matches against patterns.

Seven patterns, and which one they're matching

There are seven common derailment patterns 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. Everyone has one or two; so does the interviewer. What they're judging isn't whether you have one, but whether yours resonates with a risk the team already carries. A team that already has two avoiders can't take a third; a perfectionist would actually balance it.

So saying clearly 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, not the "I'm too much of a perfectionist" kind.

Tell it in time order, not logical order. What happened, what you did, what happened next.

Include the emotion. "I was panicking" is more credible than "I calmly assessed the situation."

The lesson is the last sentence, one sentence, and specific to a behavior: "Since then I have a rule: three days without progress and I escalate."

Where I'm not sure

Some Japanese interviewers still score against the "failure, reflection, growth" template, and the real version may not earn you points. Then the question is whether you want to join a company that interviews by template. If you 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 what you thought afterwards?


Shorter notes that don't make it into a full article go on LinkedIn. Follow me there.

Writing about launching in Japan, in three languages.