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.
Table of Contents
10 Leadership Interview Questions and How to Answer Them
Question 1
Tell me about a time you demonstrated leadership.
What it tests
Whether you can produce a story that contains a direction you chose, people who moved because of you, and something that changed afterwards, rather than a project you happened to be part of.
What a strong answer includes
A strong answer names the direction and why you chose it, the specific people you had to move and what you did to move each of them, and what the team did differently afterwards. It stays in the first person throughout: what you decided, whom you spoke to, what they said back, what you did about it. A version where the team simply aligned and results improved reads as an observer account of someone else's work.
Sample answer
My team shipped a weekly release that broke something roughly every other week, and everyone had come to treat that as normal. I decided we would stop adding features for two weeks and fix the release process instead. I walked the three loudest skeptics through the last six incidents one at a time, because the pattern was only obvious once you saw them together. Two agreed on the spot; the third wanted to keep one feature in flight, so I let that one continue and paused the rest. We rewrote the deployment checklist, added a rollback step, and I ran the first two releases myself so nobody had to trust a process they had not seen work. Broken releases dropped to about one a quarter, and the team was still using the checklist after I moved to another project.
Question 2
Tell me about a time you set a direction your team did not agree with.
What it tests
Whether you can hold a direction through real disagreement, and whether you can tell which kind of disagreement you were facing: the goal, the path, or your right to decide.
What a strong answer includes
A strong answer names the form of the disagreement and the response it called for, states the objection you could not accept and what you did with it, and reports what the team did after the decision. Changing the path because someone had a better route belongs here too, as long as you say why you changed it. The version worth avoiding is the one where nobody actually objected.
Sample answer
We had to cut a growing support backlog and my team wanted a contractor. I thought the backlog was a symptom of an unclear triage rule rather than a headcount problem, so I set the direction that we would fix triage first and revisit hiring in six weeks. Two people pushed back hard in the team meeting and said I was making them absorb the work. We all wanted the backlog down, so this was a disagreement about the path, not the goal. I brought the numbers for my route: around four in ten tickets were being reopened because they had gone to the wrong person first. Then I asked whether anyone had a better way to fix triage. One of those two proposed a different triage rule from mine, and it was better, so we used theirs. The backlog halved in five weeks and we did not hire. At the retro I said whose rule it was, and I said plainly that I had been ready to be wrong about the contractor.
Question 3
Describe a decision you made that was unpopular.
What it tests
Whether you can make a call that costs you goodwill, explain the reasoning that made it worth the cost, and stay accountable for it once people are unhappy.
What a strong answer includes
A strong answer says who it was unpopular with and why, what you weighed, how you delivered it, and what you did about the fallout. It also says what the decision cost: someone who stayed unhappy, work that got slower for a while, a relationship you had to repair. A decision that turned out to please everyone once explained was not really an unpopular one.
Sample answer
I managed a hardware store where staff had always arranged weekend cover among themselves by text. Swaps kept falling through at the last minute, and Saturday afternoons, our busiest hours, were regularly short by two people. I decided that every swap would go through the schedule and need my approval two days ahead. The long serving part timers hated it, because the old way gave them flexibility they had earned. I announced it at the Monday huddle rather than in a message, showed them the Saturdays we had run short, said the call was mine, and did not pretend it was a group decision. I also committed to answering every swap request the same day, and kept one exception for genuine emergencies. One part timer cut her hours over it, and I did not talk her out of that. The rest adjusted within a few weeks, and we stopped running short on Saturdays.
Question 4
Tell me about a time you led people who did not report to you.
What it tests
Whether you can move a group without being able to assign the work, and whether you can name the mechanism you used in place of authority.
What a strong answer includes
A strong answer states the scope in the first sentence (how many people, no reporting line, over what period), names the mechanism (evidence people could not unsee, a cheap first step, a respected person who went first, removing the cost of the change), and then the resistance and what you did about it. Coordination work such as booking the meetings and chasing the updates is a different thing, and it is worth being clear about which one you did.
Sample answer
Four peers across two teams, no reporting line, over about two months. Both teams kept a separate list of customer issues, neither list was trusted, and escalations kept arriving twice. I could not tell anyone to change, so I merged one week of both lists by hand and showed the overlap at the joint standup: a third of the entries were duplicates and two serious issues had fallen between the lists entirely. Nobody argued with that. Then I asked for one thing only, a two week trial of a single shared list, and I did the migration and wrote the template myself so nobody else had to spend an evening on it. One peer stayed skeptical about what counted as serious, so I asked them to own that rule, and they did. We kept the shared list after the trial and duplicate escalations stopped.
Question 5
Describe how you got a group to change how it worked.
What it tests
Whether you can shift an established way of working, and whether the change survived after your attention moved somewhere else.
What a strong answer includes
A strong answer describes the old habit concretely, the small first change you asked for rather than the full redesign, who resisted and what you did about it, and evidence that the change outlived you: still in use months later, picked up by a team you were not in, written into how people onboard. A change described only as an agreement, with nobody doing anything differently the following week, is hard to believe.
Sample answer
Our design to engineering handoff was a fifty page document nobody read, and the same questions surfaced in build week every time. I did not try to replace the document. I asked for one thing: a thirty minute walkthrough with the two engineers who would build it, held before the document was written. I ran the first four myself and took the notes. Build week questions dropped enough that engineers started asking for the walkthrough on projects I was not part of, which was the moment it stopped being my idea. About six months later it was in the team handbook, and the document had shrunk to five pages because the walkthrough had absorbed most of what it existed to say. I had moved to another team by then and it was still running.
Question 6
Tell me about a time you had to hold a team to a standard it was slipping from.
What it tests
Whether you notice a standard slipping, name it to the whole team rather than to one person, and make the standard easier to meet instead of only demanding it more loudly.
What a strong answer includes
A strong answer says what the standard was and how you noticed the slip, what you said and to whom, and what you changed so the standard became easier to meet rather than only more loudly demanded. It ends with what the team's work looked like afterwards. If the story is really about one person repeatedly missing expectations, that belongs to performance management, and it is worth saying so and offering the team level example instead.
Sample answer
We had a rule that no change shipped without a second reviewer, and across one busy quarter it quietly became optional. I noticed when two of the three incidents that quarter traced back to unreviewed changes. I raised it in the team meeting rather than privately, because this was everyone and not one person: I walked through the two incidents, said the rule still stood, and said that I had let it slide by approving my own changes twice. Then I made it easier to follow. We set a fifteen minute cap on reviews for small changes and put up a reviewer rotation so nobody had to hunt for a volunteer. I checked the rotation myself for three weeks and mentioned it at standup until it was boring. Reviews went back to every change and were still holding a year later.
Question 7
Describe how you helped someone grow into a bigger role.
What it tests
Whether you develop people through real work and real risk, and whether you can say concretely what the person can do now that they could not do before.
What a strong answer includes
A strong answer names the gap you saw, the work you handed over including a decision rather than only tasks, the feedback you gave and how the person took it, and the risk you carried while they learned. It ends with what they now do unsupervised. Describing a course you sent someone on, or narrating their promotion without your part in it, leaves the question unanswered.
Sample answer
One of my analysts was the strongest person on the team technically and had never presented above me. That was the whole gap. I gave her the monthly business review, which had been my slot, and sat in the room without speaking. The first one went badly: she read the slides and lost the room when a director cut in with a question about method. Afterwards I told her exactly that, and we rehearsed the interruption rather than the slides. By the fourth month she was fielding the questions herself and I stopped attending. She runs that review now and has since picked up two analysts of her own. The risk was mine for the first two months, because if the numbers had been wrong in that room it was my name on them, and I said as much to my own manager before we started.
Question 8
Describe your leadership style.
What it tests
Whether you can describe how you actually work with people, with examples of adapting, instead of reaching for a label that would fit any candidate.
What a strong answer includes
A strong answer gives two situations and two adjustments: a person or moment where you were closely involved and why, and one where you deliberately stepped back and why, with what happened in each. The style is whatever those two have in common, named in a sentence at the end rather than announced at the start. Labels with no example behind them, and borrowed frameworks presented as your own practice, say very little about you.
Sample answer
I adjust by how much the person has done the thing before. When a new hire took over our month end close, I sat with him through the first two cycles and reviewed every line, because a mistake there ends up on customer invoices and he had never seen our systems. He found that intense and told me so, so I said what would end it: two clean closes and I would stop looking. It took three. With a senior engineer on the same team I did the opposite. She asked me to review a migration plan, I gave her the one constraint I cared about, which was no downtime in business hours, and then stayed out of it completely. If I had to name what those have in common, it is that I try to give people the smallest amount of me they need, and I say out loud what would make it less.
Question 9
How has your leadership changed as your responsibility has grown?
What it tests
Whether you can set direction through other people rather than doing more of what worked at a smaller scope, and whether you know which of your habits you had to drop.
What a strong answer includes
A strong answer names a specific habit that worked at the smaller scope and stopped working, what you replaced it with, and how you now set direction that other people carry: what you say once and then repeat, what you decide and what you hand over, how you find out whether a direction landed when you were not in the room. If nothing changed except the headcount, the scope grew but the practice did not.
Sample answer
With six people I set direction by being in the detail with them, and I was usually the one who spotted the problem first. With four teams that stopped working, and I kept trying for a couple of months anyway, which mostly meant I was late to everything. What changed is that I write the direction down and repeat it well past the point where it feels necessary: one page a quarter, the same three priorities in every skip level and every review, and I ask the managers to tell it back to me instead of telling it to them again. I also had to let a manager solve a problem in a way I would not have. One of them rebuilt an on call rotation against my instinct and it worked better than my version. My rule now is that I own the outcome and the constraint, and they own the method.
Question 10
Tell me about a leadership decision you got wrong.
What it tests
Whether you can look back at a direction you set honestly, separate the quality of the decision from the luck of the outcome, and say what is different in how you decide now.
What a strong answer includes
A strong answer picks a decision that actually cost something, says what you knew at the time and what you missed, what you did once it was clear, and what changed in how you decide. Naming the people who paid for it, and what you did to repair it, is worth more time than the analysis. A story where the wrong decision quietly worked out in the end is not an answer to this question.
Sample answer
I split a team of eight into two teams of four so that a strong engineer would have a leadership path. The reasoning was about him rather than about the work, and the work did not split cleanly: both teams needed the same person for anything touching payments, and dependencies that used to be a two minute conversation became a queue. I held the structure for a quarter, mostly because reversing quickly felt like admitting the promotion had been a mistake, and that reluctance was the real error. Then I merged the teams back, kept him as a lead inside the single team, and told the whole group why, including my own part in leaving it too long. Delivery recovered within a month. Now I shape the structure around how the work actually flows and find the growth path inside that, rather than the other way around.
How the interview is evaluated
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 around; 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 neighboring 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 flavor 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, so you can rehearse questions like these out loud before the real interview.
