Executive answering a difficult interview question

How to Talk About Failure in an Executive Interview

September 28, 2026•8 min read

“Tell us about a time something you led did not go to plan.”

It is one of the most common questions in a senior interview, and one of the least prepared for. Many executives freeze, then reach for a story that is either far too small or far too risky. Some try to turn it into a success in disguise.

None of those approaches works well at senior level. Panels ask this question for a reason, and the answer they want is not hard to give once you understand what they are listening for.

Why panels ask about failure

At executive level, the panel is not checking whether you have ever failed. They assume you have. Anyone who has run a function, a business unit or a major program has made calls that did not work.

What they want to know is:

  • Can you see your own mistakes clearly?

  • Do you take ownership, or do you shift blame?

  • How quickly did you notice and respond?

  • What did you learn, and does it still shape how you lead?

  • Will you tell the board bad news early?

That last point matters most for many panels. A CEO or chair wants to know that when something goes wrong on your watch, they will hear it from you first. Your answer to the failure question is their best early test of that.

Why the usual answers fall flat

From my years on the recruiter side, I heard the same weak answers again and again.

The disguised strength. “I worked too hard on a project and burnt myself out.” Panels see through this at once. It suggests you either cannot see your mistakes or will not share them.

The tiny failure. “I once missed a deadline on a report.” For a senior role, this sounds like avoidance. The example should match the level of the job.

The catastrophe. A story where the failure was so large, or so clearly your fault, that it leaves the panel worried. Honesty is good, but you are not in a confession.

The team’s failure. A story where “we” made a mistake and your part is unclear. The panel wants to hear what you did.

How to choose the right failure

The best failure story sits in a middle zone. It needs to be:

  1. Real. Something that actually went wrong, with real consequences.

  2. Significant. Big enough to matter at the level you are applying for.

  3. Yours. A decision or judgement you owned, at least in part.

  4. Survivable. Not so serious that it raises doubts about your fitness for the role.

  5. In the past. Far enough back that you can show what changed afterwards.

Good sources include a hire that did not work out, a project that ran over time or budget, a change you pushed too fast, a risk you underrated, or a stakeholder you failed to bring with you.

Avoid stories that involve legal breaches, safety incidents, integrity issues or anything still unresolved. If in doubt, choose a different example.

Think too about who might be listening. The executive markets in Australia and New Zealand are small, and a panel member may know the people in your story. Keep names out, describe others fairly and make sure the facts would hold up if someone checked. A story you would be comfortable telling in front of your former CEO is usually a safe one.

A structure that works

A good failure answer usually runs for about two minutes and has five parts.

  1. The context, briefly. What you were trying to do and why it mattered.

  2. The call you made. The decision or judgement that turned out to be wrong.

  3. What happened. The impact, stated plainly and without drama.

  4. What you did next. How you responded, repaired and reported it.

  5. What changed. The specific way you work differently now.

The last part carries the most weight. A panel will forget the details of the failure. They will remember whether you learned something real from it.

Our guide to why STAR answers fall flat at executive level explains why a decision-led structure works better than a formula for questions like this.

Owning it without over-apologising

Tone matters as much as content. There are two traps.

The first is defensiveness. Too much context, too many other people to blame, too much explaining. It sounds like you are still arguing the case.

The second is over-apologising. Dwelling on how bad you felt, or talking yourself down. It can make the panel worry about how you will cope under pressure.

The tone to aim for is calm and matter-of-fact. Something like: “That was my call, and it was the wrong one. Here is what I did about it, and here is what I do differently now.” Then move on.

Before and after: one failure, two answers

Here is an illustrative example. The details are made up.

Before: “We had a systems project that went over budget. There were a lot of issues with the vendor and the business kept changing its requirements. In the end we got it done, and I learned that communication is really important.”

After: “Early in my time as COO, I pushed a new rostering system live across all sites in one go, rather than piloting it first. I was confident in the testing and I wanted the savings quickly. It went badly. Two sites had payroll errors in the first fortnight, and we lost trust with staff that took months to rebuild. I told the CEO the same day, set up a daily fix meeting and personally visited both sites to apologise. We had it stable within three weeks. Since then, I always pilot any change that touches pay or rosters, however good the testing looks, and I build staff trust into the business case, not just the savings.”

The second answer is specific. It names the call, owns it, shows the response and ends with a clear change in behaviour. It also gives the panel several useful follow-up threads.

Preparing for the follow-up questions

Panels rarely stop at your first answer. Expect questions like:

  • “When did you first realise it was going wrong?”

  • “Who else was involved in that decision?”

  • “What did the board or CEO say?”

  • “Would you make the same call again with what you knew then?”

  • “How do you know the change has stuck?”

These questions test whether the story is real and whether your learning runs deep. Think them through in advance. You do not need scripts, but you should know the facts and your honest view of each one.

How failure links to your leadership style

Your failure answer often shapes how the panel reads the rest of your interview. If you describe a leader who reflects, owns mistakes and adapts, it supports what you say elsewhere about how you lead.

If it does not match, the panel will notice. A candidate who claims to be open and collaborative but tells a failure story full of blame sends a mixed message. Our piece on describing your leadership style in an interview covers how to keep your answers consistent.

Handling failure questions in a panel

In a panel interview, different members may care about different parts of your answer. The chair may focus on how you told the board. An HR member may focus on the people impact. A finance member may ask about cost.

Look at the person who asked, then include the others as you speak. Keep your answer short enough that they have room to probe. Our guide to executive panel interviews has more on reading and managing the room.

Common mistakes

Choosing a story with no real stakes. If nothing much was lost, the panel learns nothing about you.

Blaming the context. Markets, budgets and other teams may have played a part. Mention them briefly, then focus on your own role.

Skipping the learning. “I learned a lot” is not a lesson. Name the specific change.

Using a failure that is too recent. If you cannot yet show what changed, the story is not ready.

Having only one story. Some panels ask for two failures, or ask again in a different form. Prepare a second.

Questions to ask yourself

Before your interview, check your failure story against these questions.

  • Is this a real failure, not a strength in disguise?

  • Does it match the level of the role I am applying for?

  • Is my own part clear, or am I hiding behind “we”?

  • Could I tell it calmly, in about two minutes?

  • Have I named a specific thing I do differently now?

  • Would I be comfortable if the panel called a referee about it?

  • Do I have a second example ready?

If you can answer yes to all of these, your story is ready.

Treat failure as evidence of judgement

The failure question is not a trap. It is one of the few moments in an interview where a panel can see how you think when things go wrong. Choose a real story, own it calmly and show what changed. Done well, it can be one of the answers that builds the most trust.

If you want help choosing and shaping your strongest interview stories, see how I approach executive interview preparation.

If you have a senior interview coming up and want to test your answers, book a complimentary Clarity Session and we will work through the questions you are most worried about.

executive interview failure questiontell me about a failureinterview mistakes questionbehavioural interviewexecutive interview answersleadership interview questionssenior interview preparationpanel interviewcfo interviewinterview examples
Belinda Paris

Belinda Paris

Founder

Belinda Paris spent 20 years deciding who got shortlisted. For the last 10 years, she has been on the other side, helping CFOs, finance leaders and board directors position themselves for better roles, promotions and pay. More than 5,000 resumes written.

LinkedIn logo icon
Instagram logo icon
Back to Blog