How to Prepare for an Executive Interview: Answer the Real Question

Most advice on executive interview questions tells you to prepare your stories, research the company and use the STAR method. All true, and it is not why strong leaders lose. They lose because they answer the question that was asked.

At the senior level the question is almost never the question. "Tell me about your modernization playbook" is not a request for a project history. It is "do you have a way of solving the problem we have?" "How would you build our technical strategy?" is "can you take something ambiguous and turn it into a plan we can measure?" Answer the words and you give a good answer to the wrong question. Answer what sits under the words and you sound like the person they are trying to hire.

The research behind this page says the same thing. The executive interview guides, the scoring rubrics hiring panels use, and CEOs describing how they hire all repeat one pattern: a senior interview tests interpretation, not recall. Panels score whether you understood their problem and whether your evidence holds up when they push on it, far more than how polished the answer sounds.

I have sat on both sides of that table. I have hired thousands of people across the globe in my career, and I have been the candidate a recruiter brought into Cox Automotive. When I hire, I listen for three things. Did they do the work they are claiming, or were they near the person who did? I look for the details and facts that prove it. Did they answer the question I asked? And did they have good stories that showed they had the skills the role needed? I now prepare leaders for those interviews. What follows is the method I use, in the order I teach it: seven interview skills, and the interview preparation that builds each one.

Key takeaways

• A senior interview tests interpretation, not recall. Strong leaders lose by answering the words of the question instead of the problem under it.
• Ask one connected question back before you answer. It tells you what they need and shows you have done the job.
• Answer with one story they could check: what you decided, the timeline, the number that moved. Say "I", not "we".
• Keep three or four stories you know cold, and map one to each topic they send you in advance.
• Close with "Did I answer your question?" and watch their face.
• Practice the hard version out loud, with someone who will push.

Executive interview questions by title

The method below is the same for every seat. The questions are not. These pages take the questions each panel actually asks for one title and answer them with this method:

• IT director and VP of IT
• CIO and CTO
• VP of Engineering, director and engineering manager
• COO and general manager
• CEO, and interviewing with the CEO

1. Find the question under the question

Before you answer anything, ask yourself one thing: why are they asking me this?

A panel asks about a failure to learn whether you can examine your own judgment without getting defensive. They ask about strategy because somewhere in the job description is the word "ambiguous", and they want to know you can turn ambiguity into a plan.

Read the job description the same way. It is the company's current guess at what it needs, not the full problem. The best preparation question is the one most candidates never ask: what problem created this role? I saw this from the candidate's side: a recruiter brought me into Cox Automotive to fix technical problems, and the problems turned out to be people and process. The stated problem and the real one are often different. The interview is your chance to show you can tell them apart.

2. Ask one question back before you answer, and make it count

The fastest way to find the question under the question is to ask. One qualifying question, sometimes two, before you answer.

The rule is that it must feel connected to their question, never like stalling. "Before I answer, how do you set technical strategy today? A roadmap with quarterly goals, or week to week?" is connected. "Can you say more about that?" is stalling.

A good qualifying question does three jobs at once. It tells you what they actually need. It shows you know what matters, because only someone who has run the playbook knows to ask about the business problem, the timeline and the team. And it changes the rest of your answer: if they tell you they plan week to week and want a real roadmap, you know exactly which story to tell next.

Listen to the answer. It is information. If you mention that you once brought in an outside analyst firm to make a recommendation, one company hears "rigorous" and another hears "not hands-on". Asking first tells you which company you are in.

3. Answer with one story they could check

Then answer, with one specific story. Not a summary of your career, one situation.

Tell it with enough detail that they could check it: the business problem in plain terms, the stakeholders, the timeline, what you decided, the number that moved. The people interviewing you are trying to work out whether you were the person who did it or the person standing next to the person who did it. Detail is how they tell. One IT staffing firm's interview guide for hiring panels puts it in four words: score the answer, not the delivery. It tells panels to listen for the count, the date, the dollar figure, the name of the vendor. A smooth answer with no specifics loses to a plain answer with real ones.

Two habits make or break the story:

• Say "I". Leaders are trained to say "we", and it is the right instinct when you lead a team. In an interview it hides you. Panels listen for the balance of "I" and "we" because they need to know what you personally decided.
• Put a number on the result. "It went well" is not an answer. "How do you know it went well?" is the follow-up you are trying to make unnecessary. Done is not "we shipped it". Done is the business result the thing was built to deliver.

What is the STAR method?

STAR is a way to organize a story: Situation (the context), Task (what you had to do), Action (what you did) and Result (what changed, with a number). Variations change one step: STAR with a final R for reflection adds what you learned; CAR (challenge, action, result) and PAR (problem, action, result) drop a step; SOAR adds the obstacle. All of them organize a story. None of them tells you which story the question is really asking for. More in the STAR method, and when it fails senior candidates.

4. Keep three or four stories ready, not thirty

You do not need an answer for every question on a long list. You need three or four detailed stories you know cold, each of which can carry several kinds of question: a modernization or transformation, an outage or failure and what you changed after, a team you built or turned around, and a hard call with incomplete information.

When the company sends you its interview topics in advance, map one story to each topic before the day. Then the questions on the day are just new doors into stories you already know.

5. Close with "did I answer your question?" and watch their face

End every substantive answer the same way: "Did I answer your question?"

Whatever they say, watch their eyes when they say it. What people say with their eyes is often more honest than what comes out of their mouths. "Yes, great" with a flat face means you missed something; ask what they were hoping to hear. "No, I was looking for a specific example" is a gift: you now know exactly what to give them.

In person, hold their eyes while you talk. On video, look at the camera while you talk so they feel you are looking at them, then look at their face on screen when you ask. Either way, you learn more in that second than in the rest of the answer.

6. Listen to their words for what they are really hiring

The questions tell you about the company. Words like "modernization" and "ambiguous" in a legacy business usually mean "we know we are slow, are you the change agent?". A panel that keeps returning to the same topic is telling you where its concern is. Answers that do not line up across interviewers (a growth target with no budget behind it, two versions of the roadmap) are a warning about the job, not about you.

7. Practice the hard version, out loud

Most interview preparation rehearses the easy version: alone, or with a friendly colleague, at a comfortable pace. Then on the day a director asks the question they rehearsed in a slightly sharper tone, and the answer comes out twice as long.

Practice with someone who will push. Role-play the question you dread, asked the way you fear it will be asked. Slow down: speed raises your stress and theirs. Answer, then stop talking. Silence after a good answer is not a gap you need to fill.

Three things the panel weighs that are not on the question list

The questions on the list are the visible part. Three things decide senior hires, and they are rarely on it.

They will hear you more than once. For a senior hire, expect several members of the executive team to interview you, and the CEO more than once. The resume got you in the room; after that it is a weak signal next to the conversations. Your story has to hold up the third time, told to a different person probing a different angle. That is why step 4 says three or four stories you know cold.

They want the why behind every move. Why you left, why you joined, why now often tells them more than what you did there. Expect a version of "what is your greatest strength, and what does it cost you?" Every strength has a shadow: the decisive leader who steamrolls, the consensus builder who defers. Prepare one honest sentence for each career move, and know your shadow before they ask. And be careful with "I'm very self-aware"; the people who are rarely say it.

They want to see that you want this. Late in a senior process the question shifts from "can you do this?" to "why do you want this, here, now?" Panels are listening for real desire and a connection to their problem, not a search that happens to include them. Have a real answer.

When they ask about a failure

Every senior interview asks about a failure, and most answers fail the same way: too small to matter, or so polished the panel cannot see the decision. A strong answer has the shape of the rest of this method:

1. Name the failure and your part in it first. "I approved the plan before we had proved the cost to serve" is an answer. "The organization wasn't ready" is not.
2. Give the objective, the decision you made and what it cost, with the number.
3. Say when you realized it was failing and what told you.
4. Say what you did about it, and give credit to the people who fixed it with you.
5. Say what you do differently now, and give one later example where the change worked.

Do not force a happy ending. If the money was not recovered, say so. A panel trusts the leader who can describe a loss plainly, and it notices when the blame drifts to a predecessor, a board or a team. "I", not "we", matters most here.

The interviews that do not look like interviews

The coffee, the dinner, the "chemistry" meeting with the chair are interviews. They test judgment and fit in a setting where it is easy to relax into a story you would never tell in a panel.

Before you go, find out why the meeting is happening. If someone set it up, ask them what prompted it and "what would make this meeting a success from their side?" Bring a one-page brief in your head: what you want to learn, the two or three experiences most relevant to them, and what is still unresolved.

In the room, use it to test the job as much as they test you. "Autonomy" and "transformation" are easy words over dinner; ask what authority, budget and people actually come with them. Do not make casual promises about what you will deliver or when you could start, and leave compensation for a later conversation with the right people in it.

Questions to ask in an executive interview

Executive interview prep usually stops at your answers. Your questions are part of the interview too, and the best ones use the same method: they get at the problem under the job.

Ask	What the answer tells you
What problem created this role, and why now?	Whether the job description matches the real problem
Twelve months from now, what will have happened for you to say hiring me was the right call?	How they will judge you, in their words
Where does the leadership team see this role differently?	Whether the mandate is agreed. If the answers differ across interviewers, that is the job
What authority, budget and people come with the mandate? Do I own the budget or recommend it?	Whether the title comes with the power to deliver
What did the last person in this seat struggle with?	The trap waiting for whoever takes the seat
When we disagree, how will we decide?	How decisions really get made above you
Is there anything about my background that gives you pause?	What could still cost you the offer

The last one takes nerve. It also lets you answer the concern while you are still in the room, instead of leaving it for the debrief after you go.

What is the 30-60-90 rule in an interview?

It is the expectation that a senior candidate can say what they would do in their first 30, 60 and 90 days, and you should expect to be asked. The strong answer is not a fixed plan. It is how you would diagnose before you act: who you would listen to first, what you would measure, and the one visible problem you would fix before redesigning anything. I wrote about what actually works in the first 90 days.

Questions people ask

What is the 80/20 rule in interviewing?

It comes from interviewer training: the candidate should do about 80% of the talking and the interviewer about 20%. For you that means most of the time is yours, so every answer has to carry substance. At the senior level the split is more two-way: your qualifying questions and your questions at the end are part of how they judge you.

What is the biggest red flag to hear when being interviewed?

Answers that do not line up: a growth goal with no budget behind it, two leaders describing different roadmaps, or nobody able to say what success looks like in the first year.

How long should an answer be?

Long enough to tell one specific story with a result, short enough that they can ask a follow-up.

What are the 5 C's of interviewing?

A memory aid with no single official list. Most versions include confidence, competence and communication, plus two of courtesy, clarity, character or culture fit. Useful as a checklist; at the executive level the panel is weighing your judgment on their problem more than any list.

How do you prepare for an executive interview?

Find the problem that created the role, prepare three or four stories you can tell with checkable detail and a number, map one story to each topic they send you, practice the hard version out loud with someone who will push, and prepare questions that get at the problem under the job.

Should I use the STAR method?

Use it to organize the story, not to deliver it. Senior panels care more about your judgment than about a tidy situation, task, action, result. Start with the question under the question, then tell the story.