Interview questions by topic
Leadership interview questions, with sample answers
IraAI writerAI interviewing editor
Published by the Itya team · Updated
8 questions · strong and weak answers in candidates' words · anchored 1-to-5 scale
Answers from James, Tara and Kiran, three illustrative candidatesWhat interviewers listen for
- The team doing the work, not the manager. Strong answers show what other people did differently because of the candidate, not how hard the candidate worked.
- Hard conversations, on time. When they first noticed a problem with someone's work, and how soon they spoke to that person.
- Reasons the team could repeat. Direction and decisions come with a why, including what the team chose not to do.
- Evidence in people decisions. Hiring, development and performance judged on specific work, not on fit or instinct.
- Leadership before the title. For first-time managers, a time they led people who did not have to follow them.
Meet the candidates
Three candidates from different jobs answer the questions below. Each is strong on some and thin on others, the way real candidates are, so you hear both kinds of answer side by side.
James O'Connor
Head of claims operations, insurance · 19 years · Dublin
Runs claims operations for an insurer: sixty people in three teams, each with its own lead. Decisive and fair when a hard call lands on his desk; less practiced at explaining the why, hiring carefully and growing his own leads.
Tara Sinha
Engineering manager, two teams · 13 years · Bengaluru
Manages fourteen engineers in two teams at a travel-booking company, four years into managing. Delegates well and hires carefully; takes longer than she should over hard calls, from a performance problem to a contested decision.
Kiran Patil
Sales team lead, first year managing · 8 years · Pune
Promoted a year ago to lead the six reps he used to sell alongside. Sets clear weekly goals and coaches well on live calls; still steps in to close big deals himself, and still sides with the team against head office.
Illustrative people. The names are invented, the portraits are AI-generated, and their words were written by our AI writers to show what candidates sound like. Any resemblance to a real person is a coincidence.
The questions
Tell me about a time your team was unclear about what mattered most. How did you set the direction?
Whether the candidate turns goals into a few clear priorities the team understands, including what to stop doing and why.
Follow up with
- What did you tell the team to stop doing?
- How did you know they had understood?
- How did you check the direction was right?
Kiran PatilSales team lead, first year managing · 8 years · Pune“When I took over, the team was chasing every lead that came in, from five-person shops to large distributors, and closing very little. I looked at the last two quarters: ninety percent of our revenue came from companies with fifty to five hundred staff. So in my first team meeting I said three things. We focus on that band. We stop doing demos for anyone under fifty staff and send them to inside sales. And every rep books four discovery calls a week. I put the numbers on one slide so they could see why, and asked each rep which of their deals they'd now drop. We review those three every Monday, and our win rate went from about twelve percent to twenty in two quarters.”
What makes it strong
Works out why the team is unclear, chooses a few priorities tied to a goal, explains the reasoning and what will not get done, checks understanding, and revisits when the facts change. Shows how the team's work changed.
James O'ConnorHead of claims operations, insurance · 19 years · Dublin“Direction comes from our targets. Every quarter I share the service levels the business has set: claims settled within ten days, customer satisfaction above eighty. Everyone knows the numbers, and the team leads take it from there.”
What gives it away
Passes on targets from above as the direction, or calls everything a priority. Cannot say what the team stopped doing or why the priorities were chosen.
Tell me about something important you delegated that you could have done faster yourself. How did you hand it over?
Whether the candidate gives away real ownership, with context and support, rather than only tasks, or nothing at all.
Follow up with
- What did you decide not to check?
- What did they do differently from how you would have done it?
- What happened when something went wrong?
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“We had to add a second payments provider before the holiday season, and I'd done a migration like it twice. I gave it to a senior engineer who'd never run a cross-team project. I told him what done meant, a cutover date and zero failed payments, and the constraints, and left the plan to him. We agreed a fifteen-minute check-in twice a week and one rule: he'd tell me the same day if the date was at risk. He moved traffic over one region at a time, which I'd never have done. It took two weeks longer than it would have taken me, and it went live with no failed payments. He runs these now, and I got back about a day a week.”
What makes it strong
Picks work that stretches the person, explains the outcome and the constraints rather than the steps, agrees how and when to check in, lets them make calls the manager would have made differently, and steps in only on agreed risks. Shows growth in the person and time freed for the manager.
Kiran PatilSales team lead, first year managing · 8 years · Pune“I delegate the admin, mostly: CRM updates, the weekly report. With the big deals, honestly, I step in myself. When a deal is worth more than ten lakh, I take the final call with the customer, because I've closed more of those than anyone on the team and we can't afford to lose them.”
What gives it away
Delegates only routine tasks, hands over without context, or takes the work back at the first problem. Talks about delegation as getting things off their plate.
Tell me about someone on your team who was not meeting expectations. What did you do, and what happened?
Whether the candidate deals with underperformance early, directly and fairly, and follows through to an outcome.
Follow up with
- How long had it been going on before you raised it?
- What did you find out about the cause?
- What did you write down, and when?
James O'ConnorHead of claims operations, insurance · 19 years · Dublin“One of my claims handlers, very experienced, started taking twice as long as the rest of the team to settle claims, and his error rate was climbing. I spotted it in our monthly figures and sat down with him that week and showed him the numbers, not my opinion. He told me he'd never been properly trained on the new claims system and had been working around it with spreadsheets. We agreed three things in writing: two weeks with a buddy on the system, a weekly look at his numbers with me, and getting back within the team's range in six weeks. He got there in five. If he hadn't, the next step was a formal plan, and he knew that.”
What makes it strong
Raises it early and privately with specific examples, finds out the cause, agrees clear expectations, support and a timeline, follows up as agreed, and reaches an outcome: improvement, a different role, or an exit handled with dignity.
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“I had an engineer whose work kept needing a lot of rework, and his reviews were always late. I gave him time, because I didn't want to demotivate him, and I hoped the next project would suit him better. It went on for about two quarters before I brought in HR to help.”
What gives it away
Waited months hoping it would improve, handed the problem to HR, or moved the person without a conversation. Talks about the person's attitude rather than specific work.
Walk me through the last person you hired. How did you decide what you were looking for, and how did you choose?
Whether the candidate hires against a clear definition of the job, with evidence from the process, rather than on instinct or speed.
Follow up with
- What did you decide the role needed before you met anyone?
- Who else was involved, and how did you compare notes?
- How has the hire turned out?
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“Last quarter I hired a senior engineer for our search team. Before we posted the role, I wrote down what the person had to do in their first six months: take over our pricing cache and mentor two juniors. That gave us four things to test. Every candidate did the same design exercise and the same two behavioral interviews, and each interviewer wrote up their ratings before we talked. Our final two were close. The one we hired was quieter in the room, but hers was the only design that dealt with stale prices. Six months on, she owns the cache and both juniors are shipping on their own.”
What makes it strong
Defines what the role must achieve and the skills it needs before interviewing, uses the same questions or exercise for every candidate, collects independent views before discussing, decides on evidence, and checks later whether the hire worked out.
James O'ConnorHead of claims operations, insurance · 19 years · Dublin“I can usually tell within ten minutes whether someone will work out. My last hire was a referral from one of my team leads. We had a good chat about how he'd handle a difficult customer, and I could tell he was the right sort. We were short-staffed, so we moved quickly.”
What gives it away
Decides in the first few minutes or on "fit", relies on a referral or gut feel, changes the questions for every candidate, or cannot say what the role needed.
Tell me about a decision you made without all the information you wanted, that not everyone agreed with.
Whether the candidate can make a timely call under uncertainty, explain it, and set a way to know if it was wrong.
Follow up with
- What information did you wish you had?
- Who disagreed, and what was their best point?
- How did you know whether it was the right call?
James O'ConnorHead of claims operations, insurance · 19 years · Dublin“After a storm last winter, claims tripled in a week, and our backlog was heading for six weeks. I decided to pay storm claims under two thousand euro on the customer's photos alone, without an assessor visit. Our fraud lead disagreed, and his best point was that small claims are where fraud hides. I didn't have time for a proper analysis, so I set a guardrail instead: we'd audit one in ten of those claims after payment, and if more than three percent looked suspect, we'd stop. It came in under one percent, the backlog cleared in three weeks, and the fraud lead and I wrote the rule into our storm plan together.”
What makes it strong
Explains why waiting was costly, hears the views that matter quickly, decides by a deadline, explains the reasoning to those who disagreed, sets a signal that would reverse the decision, and reviews the outcome honestly.
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“We had to choose between two databases for a new service, and the team was split. I asked for more benchmarks and set up a few more discussions so we could reach consensus. It took about six weeks, and in the end one of the senior engineers moved to another project, so the decision more or less made itself.”
What gives it away
Waited for consensus or more data until the decision made itself, or decided alone without hearing objections. Cannot say how they would have known it was wrong.
Tell me about someone who got noticeably better at their job while you led them. What did you do, specifically?
Whether the candidate develops people on purpose, through specific feedback and stretch, rather than taking credit for natural talent.
Follow up with
- How did you know what they needed to work on?
- What did you say to them, and how often?
- What can they do now that they could not do before?
Kiran PatilSales team lead, first year managing · 8 years · Pune“Our newest rep gave great demos, but she lost deals at the pricing stage. I listened to recordings of her last five calls and found the pattern: the moment a customer pushed on price, she offered a discount. We agreed one goal for the quarter, hold the price on the first push. Every Thursday we listened to one of her calls together, and before her big meetings we role-played the price objection, with me as a difficult buyer. Her average discount went from eighteen percent to nine in a quarter, and she closed our largest deal that year without me on the call.”
What makes it strong
Identifies a specific gap with evidence, agrees a goal with the person, gives regular specific feedback and practice or a stretch assignment, and can show the change in their work.
James O'ConnorHead of claims operations, insurance · 19 years · Dublin“I've had a lot of people come up through my teams. One of my team leads started as a handler, and I gave her the opportunity to step up when a lead role opened. She's very talented and took to it naturally. I'd like to think I gave her room to grow.”
What gives it away
Says they "gave them opportunities" or that the person was talented, with no specific actions. Cannot say what changed in the person's work.
Tell me about a decision from above that you disagreed with but had to carry out with your team. How did you handle it?
Whether the candidate argues upward through the right channel and then commits in front of the team, rather than distancing themselves from the decision.
Follow up with
- What did you say to your own manager?
- What did you tell the team, in your own words?
- How did the team take it?
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“Leadership decided every team would move from four-week to two-week releases. I thought it was wrong for my payments team, because each release needs a compliance sign-off, and I made that case to my director with the numbers: sign-off took six working days. She held the decision but gave us a faster sign-off path. When I told my team, I explained why leadership wanted it, which was faster fixes for customers, said I'd argued for an exception and lost, and told them what we'd got instead. I didn't pretend I'd agreed. Then we planned how to make it work. We missed one release in the first quarter, and none since.”
What makes it strong
Raised the disagreement privately and with evidence before it was final, then explained the decision and its reasons to the team honestly, without blaming those above, answered questions, and made it work. Can say what they learned.
Kiran PatilSales team lead, first year managing · 8 years · Pune“Head office cut our travel budget, so the reps couldn't visit customers as often. I told the team straight that it came from above and that I didn't agree with it either. I think they respected that I was honest with them. We mostly moved to video calls.”
What gives it away
Told the team "it came from above" or that they disagreed too, carried it out half-heartedly, or never raised the disagreement at all.
Tell me about a time you led people before you had a manager title. What did you do, and what did it teach you?
Whether a first-time manager has already practiced leading: getting people to follow a plan they did not have to follow.
Follow up with
- Why did people follow you?
- What did you do when someone did not?
- What would you do differently now that you have the title?
Kiran PatilSales team lead, first year managing · 8 years · Pune“Two years before I was promoted, our team took on eight new reps in a month and there was no real onboarding. I offered to run it. I wrote a two-week plan, paired each new rep with an experienced one, and ran a Friday session on objections. One of the senior reps thought it was a waste of his time and stopped turning up. I asked him to run one session on the objection he handled best, pricing, and after that he came every week. Seven of the eight hit target in their third month. It taught me that people follow a plan they helped build.”
What makes it strong
Describes a specific piece of work they led without formal authority, how they won people over, how they handled someone who did not follow, and what it produced. Draws a lesson they still use.
Tara SinhaEngineering manager, two teams · 13 years · Bengaluru“I was the senior engineer on my team for a few years before I became a manager, so people naturally came to me with their questions and for code reviews. I think I was the informal leader. When the manager role opened, it felt like a natural step.”
What gives it away
Describes being the expert people came to with questions, or a title such as "lead" with no account of leading. Cannot name a moment when someone did not follow.
Rating the answers
Rate straight after the interview, alone, against these anchors, and write down the line the candidate said that earned the score.
| Rating | What it looks like |
|---|---|
| 5 · Strong | Sets a few clear priorities and explains why, hands over real ownership, deals with underperformance early and fairly, hires against a definition of the job, makes timely calls under uncertainty, and can show people who grew under them. |
| 3 · Mixed | Gives real examples of direction, delegation and hard conversations, with sensible steps. Timing, evidence or follow-through is thin in one or two areas until prompted. |
| 1 · Weak | Describes leading as setting targets and checking them. Does the important work personally, avoids or delays hard conversations, hires on instinct, and distances themselves from unpopular decisions. |
If you are the candidate
- Prepare one story each for setting direction, handing work over, a performance problem, a hire and a hard decision. Most leadership interviews draw from those five.
- Say what your team did, and what you did to make it possible. Use "I" for your actions and roles, not names, for theirs.
- In a performance story, give the timeline: when you noticed, when you spoke to the person, what you agreed and how it ended. Interviewers listen for how long you waited.
- New to managing? Use a time you led without the title: onboarding new joiners, running a project across teams, organizing a college fest or a volunteer group.
- Keep the people you managed anonymous, and leave out their pay and ratings.
Never ask
- Don't ask a candidate's age, or whether they could manage people older or younger than them. Why: age says nothing about leadership, and age-based decisions are unlawful in many places. Ask how they have led someone who knew more about the work than they did.
- Don't ask about marriage, children or plans for a family, or how the candidate would 'balance' a team with home life. Why: they invite decisions on sex, pregnancy and family status, which are protected in many places, and they are asked mostly of women. Ask whether they can meet the role's stated hours and travel.
- Don't ask 'Are you a natural leader?' or 'What is your leadership style?' on its own. Why: it tests self-description, which everyone does well. Follow any answer with 'Tell me about a time…' and rate the example.
- Don't ask which community, region or background the candidate comes from to judge whether a team will 'accept' them as a manager. Why: it is a proxy for caste, religion or origin, and earning a team's trust is the skill you should be testing.
- Don't ask candidates to share the names, pay or ratings of people they managed. Why: it asks them to breach their former team's privacy, and shows you how they would treat yours. Ask what they did, without names.
Questions people ask
- What are the most common leadership interview questions?
- Most ask for a time you set direction, delegated, dealt with underperformance, hired, made a hard decision or developed someone. Situational versions ("What would you do if…") are common for first-time managers. The questions on this page cover each, with follow-ups and what strong and weak answers sound like.
- How do you answer leadership questions if you have never been a manager?
- Use a time you led without the title: training new joiners, running a project that needed other people, organizing an event or a volunteer group. Show how you got people to follow a plan they did not have to follow, and what you did when someone did not.
- How should interviewers rate leadership answers?
- Agree what a 1, a 3 and a 5 look like before the interview, ask every candidate the same questions, and rate each answer alone before discussing it. Rate what the candidate did and what happened to the team, not how confident they sounded.
- What is the difference between leadership and management interview questions?
- Management questions ask about running the work: plans, delegation, performance processes. Leadership questions ask why people follow you: direction, trust, hard conversations, decisions under uncertainty. A good manager interview asks both, and the same behavioral format works for each.
Ask it the same way every time.
Itya puts these questions in every interviewer's guide, records the answers, and drafts a scorecard that quotes the line behind each rating. The AI drafts; your team decides. Free plan, unlimited teammates.