Tell Me About a Failure: How to Answer in Consulting

An interviewer asking about failure is not trying to find a disqualifying flaw. They are testing three things simultaneously.

First, candor. Can you talk about a professional setback without managing the narrative so aggressively that the "failure" disappears? A candidate who cannot acknowledge a real failure raises a flag about how they will handle bad news with clients.

Second, self-awareness. Do you understand why things went wrong, and is that understanding causal or just descriptive? "The project failed because the timeline was unrealistic" is descriptive. "The project failed because I was conflict-averse and did not push back on a timeline I knew was unrealistic" is causal.

Third, growth. Did you behave differently in a subsequent similar situation? This is the most important part of the answer, and the part candidates most often undermine by over-coaching.

The failure you choose needs to sit in a specific zone: real enough to be credible, proportionate enough to be discussable in a first interview.

A failure that is too small ("I missed a deadline by a day because I overcommitted") reads as a humble-brag or as an unwillingness to share something genuine. A failure that is too large ("I lost a company $10 million") may make the interviewer wonder about your judgment in choosing to disclose it.

The right failure is one where you made a specific, identifiable wrong call, where the consequences were real and visible, and where you can trace a direct line from the failure to a change in how you now approach similar situations. It does not have to be from work. A failure in an academic or personal leadership context works equally well if the self-awareness is genuine.

What to avoid: failures that are actually successes in disguise ("I failed to meet my own impossibly high standard"), failures that blame the environment or other people without owning your role, and failures that are so well-packaged they feel fabricated.

The framing failure almost every candidate makes is spending too much time contextualizing the environment and too little time on their specific wrong call.

Interviewers do not need to understand every factor that contributed to the failure. They need to understand what you did or did not do that made the difference. Keep the context to two or three sentences. Get to your specific call quickly.

Name the decision that was wrong. "I decided to X when I should have Y" is the sentence that makes or breaks the answer. It takes honesty and precision to get there, which is why most candidates avoid it and substitute something vaguer. Using the STAR method can help you keep this sentence in the Action section where it belongs, rather than letting it drift into the preamble.

Practice this on a real case: the WeWork IPO case on BoardroomIQ is a study in what happens when leaders consistently choose narrative over diagnosis. Working through it gives you a clear-eyed framework for identifying genuine failure moments in your own experience.

The sentence "I decided to X when I should have Y" is the only thing standing between a genuine failure story and a managed impression.

This is where over-coaching destroys otherwise good answers. Candidates are told to always end with the lesson, so they add a paragraph that begins "And what I learned from this experience was..." in a tone that sounds like a career coach wrote it.

The growth element works best when it shows rather than tells. Describe a subsequent situation where you faced a similar dynamic and made a different call. Let the interviewer draw the conclusion that you grew. "Six months later I was in a similar situation, and this time I pushed back on the timeline in the first meeting. The client was frustrated initially, but we delivered on time." That is the lesson shown, not stated.

If you do not have a subsequent similar situation to reference, be honest about what you changed in your process or thinking. "I now ask the question I was afraid to ask in that situation before the first week of any new project" is specific and believable. "I learned to communicate more proactively" is generic and forgettable.

The failure question always generates follow-up. Be ready for "Could you have seen this coming?" and "What would you tell your past self?"

"Could you have seen this coming?" is the interviewer checking for rationalization. The honest answer is usually yes, you could have seen some warning signs. Acknowledge them without turning the answer into an extended self-flagellation.

"What would you tell your past self?" is the growth check. Your answer should be specific and behavioral, not philosophical. "I would tell myself to have the uncomfortable conversation in week one rather than waiting for the situation to resolve itself" is specific. "I would tell myself to be more courageous" is not.

Write the failure out completely. Before you can answer this question fluently, you need to understand it fully. Write a one-page account of the failure as if you were writing it for yourself, with no audience. Include every decision you made, every warning sign you saw and ignored, and every thing you would do differently. The interview answer comes from this, but it is not this.

Test for ownership. Read what you wrote and count how many times external factors appear as the cause of the failure. Every time you reference an external cause, ask: "What did I do or not do that made this factor decisive?" This reframing takes the failure back into your hands, which is where it needs to be. The most common fit interview mistakes all come from the same root cause: candidates externalizing what should be owned.

Deliver without the word "learn." Practice telling the story without using the word "learn" or "lesson." This forces you to show the growth through behavior rather than stating it through narration. It is harder and more effective.

The best way to practice the failure question for consulting interviews is under realistic pressure, with a case that fights back.