"Tell me about a failure."

As a candidate, I gave the standard answer. 

You pick something that looks like failure but isn't really — a project that went a little sideways but still delivered, a deadline you missed but had a good reason for. You dress it up with a lesson you haven't actually learned yet, something tidy and forgettable like "I learned to communicate better." Then you move on. The interviewer nods. You get the job.

But you carry the real failure, the one you didn't really look at or talk about, unexamined right into the next role.

That's the trap this question sets for you. 

What most people do

Usually they go with the safe answer. "I underestimated the launch timeline and had to push back two weeks. I learned to build in more buffer." Tells me nothing about you.

Or the humble success dressed as failure: "I pushed the team too hard. We were all stressed. But we hit the number." That's not a failure, it’s a flex with an apology attached.

Or the deflection: "The brief wasn't clear. The data was wrong and the market shifted." Circumstances take the blame. The person stays clean.

I've sat through enough interviews to know that interviewers spot these in the first two sentences.

A structure that works

Challenge. Decision. Lesson.

Notice what's not there: recovery. The lesson doesn't have to redeem the failure. It just has to be true.

Now here's the same kind of situation, told honestly. This one actually happened to me.

Challenge Early in my career, a visiting CEO sat across from our chairman and said, "If there's anything we can do to strengthen this partnership, let us know." For months, his team had stonewalled me. They didn’t return emails nor give me time. And here he was, asking.

Decision I took his offer as my cue. Told him truthfully and bluntly that his own people had been blocking me for six months. Even as I spoke, I saw the shock in my CEO's eyes. I'd put my foot in my mouth. Nobody had told me this was not the moment for real issues.

Lesson I kept going till my chairman stepped in and smoothed things over.  I was lucky I didn't get fired. That was the last day I spoke without reading the room. I learnt an invitation is not the same as an actual opening. These days, I ask myself: is this the moment, or am I just wound up?

What they're testing

It's not just honesty. It's whether you know yourself well enough to describe what happened — not the version you wish had happened.

Also this: can you sit with a bad outcome without trying to make it sound better? Hiring managers notice. Because one day you'll walk into their office with news they don't want to hear.

Try This Week

Start by scanning the last year for moments that still bother you. Not the catastrophic failures — those are easy to spot. The smaller ones. The meeting where you knew you should have said something and didn't. The email you sat on for three days because you didn't want to send it. The conversation you replayed in the car afterward.

That discomfort is your marker. If you're still turning it over in your head, there's something there.

Write it in three parts — Challenge, Decision, Lesson. When you get to Decision, don't explain it kindly. Just say what you did.

Say it out loud. Notice where you soften the edges. That's the part worth working on.

Interview storytelling
This is part of an ongoing series. See also Issues #66, #70, #26, and #34.

From Elsewhere

The Italian concept of la dolce vita — "the sweet life" — is about finding beauty and pleasure in simple, everyday moments. Slowing down. Savoring what you have. Focusing on what actually matters. But the original Fellini film that gave us the phrase had something darker in mind: emptiness, denial, a society without a moral center. This piece from The Stanford Daily walks through the gap between the modern mindset and the original film. Worth a read!