Leadership questions ask for evidence that you set a direction and brought people with you, whether or not you had the authority to assign the work. The evidence to show is the same at every level: the direction you chose and why, the people who moved and what you did to move them, and what changed for the team afterwards. This page covers the question families (direction against disagreement, leading without authority, holding a standard, developing people, the style question) with what strong answers show, the mistakes that weaken them, the follow-ups to expect, and how the evidence changes from a first-time manager to a senior leader.
What leadership questions are asking for
A leadership question is usually asking for three things: a direction you chose, people who moved because of you, and what changed afterwards. An answer with a direction and an outcome but no people in it is a project story; an answer with people in it but no direction is a teamwork story. Both are fine answers to other questions. Neither is a leadership answer.
A common way to weaken a leadership story is to tell it as an observer: the team decided, the group aligned, things improved. Prepare to say what you decided, whom you talked to, what they said, and what you did about it. This competency sits inside the wider set of manager behavioral interview questions, and the management interviews guide covers how management answers are evaluated as a whole.
Setting direction when the team does not agree
Question forms:
- Tell me about a time you set a direction your team did not agree with.
- Describe a decision you made that was unpopular.
Disagreement with a direction comes in three forms, and a strong answer says which one you were facing, because each calls for a different response. The team can disagree with the goal (they do not think it matters), with the path (they would get there another way), or with your right to decide it (they do not think it is your call). A goal disagreement is answered with the reason and the evidence; a path disagreement is often best answered by taking the better path if they have one; a right-to-decide disagreement is answered by naming who decides and why, and then deciding.
Tell the story with the form of disagreement named, the response you chose, what you did with the objection you could not accept, and what the team did afterwards. An answer where you changed the path because a team member's route was better is a leadership answer, not a weakness; an answer where you held the goal against real objection and explained why is also one. The weak answer is the one where nobody objected.
Failure modes: a story with no disagreement in it; alignment that arrives without a mechanism, where the team simply comes round; treating every objection as a right-to-decide challenge; and reversing a direction under pressure and calling it listening.
Follow-ups to expect: "Which of them still disagreed at the end?", "How did you know the objection was wrong?", and "When has a team talked you out of a direction?"
Leading without formal authority
This is the question family to prepare hardest if you have never held a title, and worth preparing for everyone else, because it can be asked of any candidate.
Question forms:
- Tell me about a time you led people who did not report to you.
- Describe how you got a group to change how it worked.
Without authority, the interesting part of the story is the mechanism: what you did instead of assigning the work. Strong answers usually name one or more of these, and the interviewer can follow up on any of them:
- Evidence. You showed the problem in a way people could not unsee: a measurement, a demo, a failure walked through in the open.
- A small first step. You asked for something cheap to try, made it succeed, and let the result make the case for the rest.
- Borrowed credibility. You got one respected person to try it first, or you did the work yourself once so the ask was concrete.
- Making it easy to say yes. You removed the cost of the change for the people who had to make it, by doing the setup, the template, or the boring part.
- A visible commitment. You said in public what you would do and by when, and then did it.
Name the mechanism, then the resistance and what you did about it, then what the group did differently afterwards. The same shape works at three scales, and it is worth having an example at the scale closest to the role: two peers on a small change, a team of five to ten on a process, a group across teams on a direction.
State the scope in the first sentence rather than waiting to be asked: "four peers, no reporting line, over about two months." Scope is the natural follow-up either way, and answering it first turns a potential weakness into evidence of judgment.
Failure modes: a story with a mechanism missing, where people "came around" for no stated reason; describing coordination (booking the meetings, chasing the updates) as leadership; and inflating a mentoring or coordinating role into a reporting line.
If you are interviewing for your first management role, the first-time manager interview guide shows how to draw this kind of evidence from project leadership, mentoring and peer situations.
Holding a standard
Question forms:
- Tell me about a time you had to hold a team to a standard it was slipping from.
Leadership is also what happens after the direction is set. A strong answer shows that you noticed the slip, named the standard to the people concerned, and followed through in a way the whole team could see, and it says what the team's work looked like afterwards. When the story becomes about one person not meeting expectations, it has crossed into a neighbouring competency; the performance management interview questions page covers that sequence in full.
Developing people
Question forms:
- Describe how you helped someone grow into a bigger role.
A strong answer names what the person can do now that they could not before, and what you did to create the chances: the work you handed over, the feedback you gave, the risk you took on their behalf. Growth described as sending someone on a course is a weak answer. Handing over decisions, not only tasks, is the competency underneath; the delegation interview questions page covers it.
The leadership style question
"Describe your leadership style" tends to produce an answer that sounds like everyone else's. A single style, however good it sounds, is a weak answer because it implies you do the same thing with every person and every situation.
A structure that works: two situations, two adjustments. Describe a person or a moment where you were hands-on and why, and one where you deliberately stepped back and why, and what happened in each. The style is whatever those two examples have in common, and you can name it in a sentence at the end rather than the start.
Failure modes: labels ("servant leader", "transformational") with no example behind them; a borrowed framework presented as your own practice; and an answer that never mentions a person.
How the evidence changes with seniority
- First-time manager: direction and influence without a title. One story of setting a direction among peers and bringing them along, with the scope stated honestly, is enough.
- Experienced manager: patterns, and the people who got better. Prepare to show how you set direction repeatedly, not once, and name the people who grew under you and what they can do now.
- Senior leader: direction across teams and through other leaders. Prepare stories where you set direction that other managers then carried, and how you handled a manager who did not.
Role changes the flavour of the questions. For an operations manager interview, prepare direction through shift leads and supervisors; for an engineering manager interview, technical direction and the tech-lead-to-manager shift; for a sales manager interview, direction through coaching and standards under quota. The evidence to show is the same in each.
Choosing your leadership stories
Two stories cover this page if you choose them for range: one where you held authority and set a direction against disagreement, and one where you did not and had to earn the change. If you have never held authority, prepare two of the second kind at different scales. For each, write down the direction, the people who moved, and what changed, and check that the story has a person in it who pushed back.
Rehearse spoken, with the follow-up asked right after: "were you right?" and "what would you do differently?" are the ones to be ready for. A manager mock interview built for your target role asks them, and gives feedback on each answer, so the observer story or the missing disagreement shows up before the real interview.
Practice these questions out loud
Reading a list is silent rehearsal. Run a mock interview for your target role and get feedback on every answer.
Start a mock interview
About the author
Mock Interview Pro team · Interview coaching and practice
Mock Interview Pro runs mock interviews and practice sessions with per-answer feedback. Our guides are built from the questions and answer patterns we see in those sessions and reviewed against the platform's coaching standards.
