How to interview for leadership roles: a loop, questions and a rubric that test how people lead
On this page
To interview for a leadership role, test how the candidate gets results through other people, not how well they talk about leadership. Build a loop of four or five stages that each cover different criteria (direction, developing people, decisions, and working across the organization), ask for specific past examples with follow-ups, add a realistic work sample, and score every interviewer independently against the same rubric before the debrief.
This guide is for hiring managers filling first-line manager, senior manager and director roles. It differs from our executive search screening questions, which cover a recruiter's confidential first call with a senior candidate. Here you are the one running the full interview loop.
What leadership interviews usually get wrong
- Rewarding fluency. Experienced managers have told their leadership stories many times. A polished answer is not evidence; the details under the second and third follow-up are.
- Asking about philosophy. "What is your leadership style?" invites a description of how they would like to lead. Ask what they did last time.
- Confusing scope with skill. Managing 40 people is not the same as managing them well. Ask what changed because they were there.
- Every interviewer asking the same things. Four people asking about stakeholder management leaves people development untested.
- Letting seniority skip the process. Senior candidates may push to replace structured interviews with "a conversation". Keep the structure and make it respectful; they will be running structured processes themselves.
Define the leadership criteria for this role
Leadership roles differ. A new manager of five engineers and a director of three regional sales teams need different things. Start from what the role must achieve in its first year, then pick five or six criteria from the list below and write what "strong" means for this role.
| Criterion | What it covers | Invented example of "strong" for a support team manager |
|---|---|---|
| Setting direction | Turning goals into priorities people understand | Has set quarterly priorities for a team and dropped work to protect them |
| Developing people | Feedback, coaching, growing others' scope | Can name people they developed and what those people do now |
| Accountability and performance | Addressing underperformance fairly and on time | Has managed a performance issue to resolution, either way, with documentation |
| Decision-making | Deciding with incomplete information; revisiting when wrong | Can describe a decision they got wrong and what they changed |
| Hiring | Building a team deliberately | Has run a structured hiring process and can describe a hire that did not work |
| Working across the organization | Influence without authority; managing conflict with peers | Has resolved a recurring conflict with another team's leader |
| Operational judgment | Metrics, budget, capacity, trade-offs | Knows their team's key numbers and what moved them |
Design the loop
An invented example for a manager hire. Each conversation owns specific criteria and nothing else.
| Stage | Interviewer | Owns | Length |
|---|---|---|---|
| 1. Hiring manager interview | Hiring manager | Setting direction; decision-making | 60 min |
| 2. People leadership | A peer manager | Developing people; accountability and performance | 45 min |
| 3. Cross-functional | Leader of a partner team | Working across the organization | 45 min |
| 4. Team conversation | Two future direct reports | How they give feedback and handle disagreement (narrow brief) | 30 min |
| 5. Work sample | Hiring manager and peer | Operational judgment; setting direction | 60 min including discussion |
Brief every interviewer on their criteria, the questions, and what not to ask. Future direct reports need the briefing most; they are often inexperienced interviewers and may ask about family or availability out of friendliness. The interviewer training checklist and panel interview plan template help.
Leadership questions, with strong answers and red flags
Setting direction
Ask: "Tell me about a time your team had more work than it could do. How did you decide what not to do?"
- Follow-ups: Who disagreed? What did you tell the people whose work was dropped? What happened to the dropped work?
- Strong answer: A named trade-off, a criterion for choosing, a conversation with a stakeholder who lost out, and a result they can check.
- Red flags: Everything was done by working harder; the answer is about their own workload, not the team's; no one disagreed.
Developing people
Ask: "Tell me about someone on your team who grew significantly while you managed them. What did you do, specifically?"
- Follow-ups: What feedback did you give that was hard to give? What did they do next? What would they say you did?
- Strong answer: A specific person (no name needed), specific feedback, stretch assignments chosen deliberately, and a visible change in their scope.
- Red flags: Takes credit for a promotion the person earned alone; cannot recall giving difficult feedback; development means "sent them on a course".
Accountability and performance
Ask: "Tell me about the last time someone on your team was not performing. Walk me through what you did from the first sign."
- Follow-ups: How long did it take you to act? What did you document? What was the outcome? What would you do sooner?
- Strong answer: Early, direct conversation; clear expectations; support offered; documentation; an outcome either way; honest reflection on timing.
- Red flags: Waited for HR to act; moved the person to another team without addressing it; describes the person with contempt; shares details that identify them or their health.
Decision-making
Ask: "Tell me about a significant decision you made that turned out to be wrong. How did you find out, and what did you do?"
- Follow-ups: What information did you have at the time? Who did you tell? What did you change about how you decide?
- Strong answer: A real mistake with consequences, early recognition, a reversal communicated openly, and a changed practice.
- Red flags: A disguised strength ("I trusted people too much"); blame on others; no change afterwards.
Working across the organization
Ask: "Tell me about a time you needed something from another team whose priorities conflicted with yours."
- Follow-ups: What did the other leader need? What did you give up? How is that relationship now?
- Strong answer: Understood the other side's constraints, found a trade, escalated only after trying directly, and kept the relationship.
- Red flags: Won by escalating first; describes the other team as the problem; no ongoing relationship.
Hiring
Ask: "Tell me about a hire you made that did not work out. What did you miss in the interview?"
- Strong answer: Names a gap in their process and what they changed, such as adding a work sample or scoring independently.
- Red flags: Every hire worked; blames the recruiter; describes hiring for "fit" without criteria.
For scoring these answers consistently, see the behavioral interview scoring rubric.
A leadership rubric to copy
LEADERSHIP INTERVIEW SCORECARD – [Role] – [Candidate] – [Interviewer]
Score only the criteria assigned to you. Submit before the debrief.
1 = No relevant example, or example contradicts the criterion
2 = Example present but vague, team-level only, or no outcome
3 = Specific example: own decisions, actions and a checkable outcome
4 = Several specific examples; reflects on mistakes; changed practice
Criterion: [e.g. Accountability and performance] Score: __
Question asked:
Evidence (candidate's words):
What they personally did vs what the team did:
Follow-up that changed my view, if any:
Criterion: [ ] Score: __
Question asked:
Evidence:
Overall concerns (job-related only):
Recommendation: [strong yes / yes / no / strong no]A work sample for leadership candidates
Conversations test what people say they did. A work sample shows how they think in your context. Keep it short, realistic and fair to someone who does not yet have inside information.
- Team scenario (45 to 60 minutes): give an invented one-page brief of a team with a missed target, two people in conflict and a new priority from above. Ask for their first 30 days: what they would find out, who they would talk to, what they would decide and what they would not decide yet.
- Feedback role-play (20 minutes): an interviewer plays an employee who missed a deadline and is defensive. Score clarity, listening and a concrete next step. Tell the candidate in advance that a role-play is part of the loop.
- Metrics review (30 minutes): a simple invented dashboard. Ask what they would question and what they would do first.
Avoid take-home strategy documents that amount to unpaid consulting on your real problems. The guide to evaluating a take-home assignment covers fair limits.
References and the debrief
- Ask for a former direct report as a reference, not only former managers. How someone led is best described by the people they led. Ask for permission first and respect confidentiality for current employers.
- Test the examples you heard. "The candidate described turning around a team's delivery in 2025. What did you see?"
- Run the debrief by criterion, not by interviewer. Read all scores for one criterion, discuss the evidence, then move to the next. See the interview debrief template.
- Watch for the halo of presence. Senior candidates who are confident and articulate can lift scores across every criterion. If a score is higher than the evidence written under it, lower it.
- Internal candidates get the same loop. See interviewing internal candidates for how to handle familiarity and feedback.
Leadership loops generate a lot of conversation and it is easy to lose the specific evidence. Take notes in the candidate's words, or use a note-taker so you can listen; Interview Signal, for example, splits questions across a panel and shows which were covered, without sharing anyone's notes. Either way, score before you talk to the other interviewers.
Questions people ask
What is the most important thing to test in a leadership interview?
How the candidate gets results through other people: setting direction, developing and holding people accountable, and making decisions with incomplete information. Ask for specific past examples of each, with names of roles, numbers and outcomes, rather than their philosophy of leadership.
Should future direct reports interview a leadership candidate?
Many teams include one or two, with a narrow brief such as how the candidate gives feedback or handles disagreement, and a scorecard like everyone else. Their input is evidence, not a veto, and the hiring manager should brief them on what they may not ask.
How do I tell whether a leader or their team drove a result?
Ask what they personally decided, what they would do differently, and who disagreed. Listen for "I" on the decisions and "we" on the execution. Candidates who can only describe outcomes, not the choices behind them, may have been near the result rather than responsible for it.
How should I interview an internal candidate for a leadership role?
Use the same loop, questions and rubric as external candidates, and score only what you hear in the interview plus documented performance. Familiarity cuts both ways; the guide on interviewing internal candidates covers how to keep it fair and how to tell them the outcome.