Questions to ask C-level executives in an interview

Start with the evidence you need, not the impressive conversation

The best questions to ask c-level executives are not the cleverest ones. They are the ones that make a senior candidate show how they thinks, decides and behaves when the stakes are awkward. That sounds obvious until you sit opposite a polished CFO, COO or CRO who has spent 20 years making rooms feel calm. Executive presence is useful. It is not evidence by itself.

An executive interview should therefore begin with a more severe question for the hiring team: what evidence would make us confident this person can do the job here? If the answer is "they sounded strategic", you have not finished the work. You need comparable evidence about judgement, trade-offs, leadership behaviour and the conditions under which the candidate has actually delivered.

The research problem is familiar. Dana, Dawes and Peterson (2012) describe how unstructured interviews create a feeling of understanding even when the information is weak. Interviewers can make sense of almost anything a candidate says, and that sensemaking can increase confidence without increasing accuracy. McDaniel, Whetzel, Schmidt and Maurer (1994) found that structured interviews have higher validity than unstructured interviews, especially when the content is job-related.

That matters more, not less, at the C-suite. Leadership interviews differ from front-line hiring because the answers are more abstract, the candidates are more practised and the cost of a false positive is larger. The job of the interview is not to admire fluent leadership language. It is to make the candidate produce usable evidence.

The executive competencies worth testing

Before writing questions, agree the leadership competencies you are trying to measure. A C-level interview is too important to be built from whatever questions the panel happens to like. Campion, Palmer and Campion (1997) argue that stronger interviews start with job analysis, ask consistent questions and evaluate answers against defined criteria. Levashina et al. (2013) describe the same principle as predetermined rules for questions, observations and evaluations.

For most C-level roles, the useful competency map is compact. Test strategic judgement: how the candidate chooses where to play, what to stop doing and how to allocate scarce attention. Test operating judgement: how they translate intent into rhythm, accountability and numbers. Test people leadership: how they build teams, raise standards and handle underperformance. Test stakeholder management: how they work with founders, boards, peers and customers when interests collide. Test values under pressure: what they protect when performance, politics and incentives pull in different directions. Finally, test learning: whether they can update their view without outsourcing every hard lesson to "the market".

The role will change the weighting. A CPO needs deeper evidence on organisational design and talent standards. A CFO needs sharper evidence on capital allocation, risk and commercial judgement. A COO needs proof of operating cadence. But the structure is the same: choose the competencies first, then ask questions that make the candidate provide evidence for those competencies.

OPM describes structured interviews as assessments of job-related competencies. That phrase is doing real work. If a question cannot be tied to a competency, it is probably theatre. Pleasant theatre, perhaps. Still theatre.

Strategic questions to ask senior leaders

Strategic questions to ask senior leaders should force prioritisation. Many executives can explain a market. Fewer can show how they would choose when every option has a constituency and every delay has a cost. Use questions that make the candidate name assumptions, expose trade-offs and describe consequences.

1. Tell us about a time you chose not to pursue a promising opportunity. What made it attractive, and why did you still say no?
2. Imagine this business has 12 months of runway for only two of its three major bets. How would you decide which one loses funding?
3. Describe a strategic decision where your first read was wrong. What evidence changed your mind?
4. When have you inherited a strategy you did not fully believe in? What did you do in the first 90 days?
5. Which metric have you seen leaders over-trust, and what did it hide?

Strong answers have a shape. The candidate explains the context without drowning you in it. They separate facts from assumptions. They name the stakeholders who mattered, but do not hide behind stakeholder management as a substitute for judgement. They describe the opportunity cost, the risk they accepted and the result they watched afterwards. If every answer ends with universal alignment and a neat hockey-stick outcome, keep probing. Real strategy tends to leave fingerprints.

Useful follow-ups are simple. Ask: "What did you stop doing?", "What would your strongest critic have said?", "What did you measure three months later?", and "What would you do differently now?" These follow-ups stop the candidate performing strategy as a set of nouns - vision, alignment, transformation - and bring them back to decisions.

McDaniel, Whetzel, Schmidt and Maurer (1994) found that interview validity varies by interview content. That is the point here. A strategic executive interview question is not good because it sounds senior. It is good because it pulls job-related evidence into the room.

Questions that test people leadership and culture

People leadership is where many executive interview questions become foggy. "How would you describe your leadership style?" is not useless, but it invites a brochure answer. Calm, empowering, accountable, transparent. Lovely. Also available in multipacks. Better questions ask for behaviour under strain.

1. Tell us about the highest-performing person you have managed who was damaging the team. What did you do?
2. Describe a time you raised the talent bar in a team without losing trust.
3. When have you had to replace a leader you personally liked?
4. What is a cultural behaviour you will not tolerate, even from a commercially valuable person?
5. How do you decide whether underperformance is a capability problem, a motivation problem or a context problem?

These questions test leadership competencies because they ask for observable judgement: diagnosis, standards, courage, fairness and follow-through. A strong answer does not need melodrama. It should show what the candidate noticed, what options they considered, how they communicated, what changed and what they learned. Weak answers often stay at the level of intent: "I believe in accountability" or "I create psychological safety". Those may be true, but beliefs do not run meetings, write role scorecards or tell a popular executive their behaviour has a cost.

Structure helps here because culture is dangerously easy to personalise. OPM's concise definition of a structured interview emphasises standardised questioning and scoring for all candidates. That discipline keeps the panel from giving one candidate credit for warmth and another credit for toughness when both were meant to be assessed against the same standard.

Good people-leadership questions are not personality tests. They are evidence traps, in the useful sense. They make the candidate show how they lead when someone talented, senior or commercially important makes the easy answer uncomfortable.

How to score C-level answers without being dazzled

The question list is only half the instrument. The scoring does the quiet work. Without it, the panel will remember the best story, the most confident candidate or the person whose experience feels closest to their own. Dana, Dawes and Peterson (2012) would not be surprised. Humans are very good at turning rich interview material into a convincing story. We are less good at noticing when the story is doing the scoring for us.

Use a simple 1-5 scale for each competency. A score of 1 means the answer is vague, evasive or not relevant. A 2 gives some example but little ownership or consequence. A 3 shows a credible example with reasonable logic. A 4 shows clear judgement, trade-offs, measurable consequences and learning. A 5 shows all of that in a context close to your role's difficulty, with evidence that the candidate can repeat the behaviour rather than merely remember it fondly.

For each question, write the signals before the interview. For a strategic trade-off question, a strong answer may include explicit criteria, rejected options, stakeholder handling, decision timing and post-decision measurement. For a people-leadership question, it may include diagnosis, direct communication, support, consequences and team impact. This is the difference between a structured interview and an expensive chat with notes.

OPM's guidance on structured interview scoring recommends scoring competencies on a proficiency scale and using equal weights unless there is a documented reason to do otherwise. That is a useful default for smaller hiring teams. Do not create a delicate 17-factor weighting model if the panel has not yet learned to take clean notes.

Score independently before discussion. Then compare evidence, not impressions. "I liked her" is not banned, but it must translate into something observable: what did she say, what did she do, what result followed? Senior candidates can be dazzling. The scorecard is there for the moments when dazzled people start calling themselves calibrated.

Installing this process across every interviewer

Once you have the questions and scoring rubric, the next problem is consistency. A founder asks about vision. The CFO asks about cost control. The head of people asks about values. The board member has a favourite question from 2008 and is not giving it up without a small ceremony. Each question may be reasonable on its own, but the process can still fail if no one is assessing the same evidence.

This is where executive hiring needs an operating system, not another downloaded question bank. Decide the competencies. Assign questions to interviewers. Give each interviewer the evidence signals and scoring anchors. Keep candidate questions for a separate part of the conversation so they do not consume the assessment time. Ask interviewers to record evidence during the interview and score before the debrief. Campion, Palmer and Campion (1997) list these as core elements of structure: same questions, ratings for answers, anchored scales, notes, multiple interviewers, no premature discussion and interviewer training.

HireSchool exists for this exact kind of practical installation. The Structured Hiring Method programme is a self-guided digital programme that helps small businesses and scale-ups codify their hiring process: interview flow, capabilities tested, candidate assessment and decision mechanics. It is delivered through video content and a learning management system, so every interviewer can learn the same method without bringing in consultants or inventing a new process from scratch in the gap between two urgent vacancies.

That matters for C-level hiring because senior processes often look deceptively mature. The calendar is full, the panel is impressive and the candidate pack has a tasteful font. Underneath, the decision may still depend on who had the most persuasive conversation with the CEO. A structured process does not make the decision mechanical. It makes the evidence visible enough that judgement has something decent to work on.

OPM describes structured interviews as among the most valid assessment tools when designed and used correctly. The "used correctly" part is where companies usually come unstuck. The method has to survive contact with busy interviewers, different functions and the understandable temptation to go off-script because a senior candidate is interesting.

A good process still leaves room for human judgement. It simply asks that judgement to show its working. In executive hiring, that is not bureaucracy. It is due diligence wearing sensible shoes.

A C-level interview question bank you can adapt

Use this bank as raw material, not as a script to plough through. Choose six to ten questions that match the role, assign them to competencies and score them properly. SHRM's guidance on structured executive panel interviews makes the same practical point: prepared leadership questions help teams compare candidates, especially when several senior stakeholders are involved.

• Strategy: Which opportunity would you deliberately not pursue in our position, and why?
• Strategy: Tell us about a decision where the financially rational answer conflicted with the strategically right answer.
• Operating cadence: What weekly or monthly rhythm do you install first when a team is drifting?
• People leadership: Describe the most difficult talent call you made in the last two years.
• Stakeholders: When have you had to tell a board, founder or CEO something they did not want to hear?
• Change: What did you do when a transformation programme started to lose credibility?
• Values: What commercial result would you refuse to celebrate?
• Learning: What belief about leadership have you changed your mind on?
• Hiring: What do you look for when hiring your own direct reports, and how do you test it?
• Risk: Which risk in your current or most recent business did people under-price?

If you are answering common search questions: good questions are specific, job-related and hard to bluff. The hardest interview questions are not trick questions; they are questions that ask for a real trade-off, a real mistake or a real standard. Leadership frameworks such as the three, five or seven Cs can be useful prompts, but they are not a scoring system. Convert any framework into behaviour before using it.

The point is not to catch people out. It is to give excellent executives a fair chance to show the work behind the polish, and to give your hiring team a fair chance of remembering the evidence after the room has gone quiet.