15 Leadership Interview Questions and Sample Answers

Leadership questions are almost always about the past. "Tell me about a time you..." is the usual opening, and the interviewer wants a real story: what was going on, what you decided, how you got other people to go along with it, and how it turned out. Polished generic answers don't work well here, because the follow-up questions ("What did your manager think?" "What would you do differently?") quickly show whether the story is real.

Below are 15 common leadership questions with sample answers. The details are placeholders. Swap in your own situation, numbers, and results.

Before you start: pick your stories

Most leadership questions can be answered with five or six stories you know well. Write down a time you:

• made a call without all the information,
• got people who didn't report to you to do something,
• helped someone improve,
• dealt with a conflict,
• pushed through a change people resisted,
• failed and fixed it.

Then match each question below to one of your stories. Try not to use the same story twice in one interview.

Decisions and direction

1. Tell me about a time you had to make a decision without all the information you wanted.

"We were two weeks from a product launch when a key supplier said they might be late. We didn't know if it would be days or a month. I had to decide whether to delay the launch. I listed what we did know, called a backup supplier to get a firm price and date, and recommended we place a small backup order. It cost a little extra, but when the main supplier was three weeks late, we launched on time."

2. Describe a time you set direction for a team when things were unclear.

"When our team lead left suddenly, nobody knew which projects to keep going. I listed everything in progress, sorted it by deadline and customer impact, and proposed a priority order in our next team meeting. We agreed on it together and sent it to our director, who approved it with one change. That list was what the new lead started from."

3. Tell me about a time you disagreed with a popular decision.

"The team wanted to rebuild a reporting tool from scratch. I thought fixing the existing one would take a third of the time. I put together a quick comparison of effort and risk and asked for one meeting to go through it. We ended up fixing the old tool first and planning the rebuild for later, which freed up a month for other work."

4. Tell me about a decision you changed after getting new information.

"I'd decided to move our customer onboarding entirely to email. A week into the trial, the data showed completion rates dropping for older customers. I told the team I'd been wrong about that group, and we kept phone onboarding as an option for them. Admitting it quickly mattered more than being right the first time."

Influence and teamwork

5. Describe a time you led without formal authority.

"I was a developer, and our releases kept breaking because three teams tested differently. None of them reported to me. I wrote up the two failures from the last month, showed what they'd cost, and proposed one shared checklist. I asked each team lead to change it until they were happy with it. After a month all three teams were using it, and release problems dropped."

6. Tell me about a time you got people with different goals to agree.

"Sales wanted a new feature fast, and support wanted us to fix bugs first. I set up one meeting where each side shared their numbers: deals waiting on the feature versus tickets caused by the bugs. Seeing both lists, they agreed to split the next sprint, fixing the three bugs behind most tickets and starting the feature in parallel."

7. Tell me about a time you delegated something important.

"I was overloaded during our busiest season and handed our weekly client report to a junior colleague who'd never written one. I walked her through the first one, reviewed the second, and then let her own it. She was faster at it than I was by the third week, and the client didn't notice the change."

Developing people

8. Tell me about someone you coached to improve.

"A new team member was missing details in his work. Instead of just correcting it, I sat with him to see how he worked and noticed he wasn't using a checklist. We made one together for his most common tasks. His error rate dropped within a few weeks, and he later shared the checklist with the next new hire."

9. How have you handled a conflict between two strong performers?

"Two senior engineers kept arguing in design reviews, and it was slowing everyone down. I talked to each separately and found the real issue was that they owned overlapping parts of the system. I worked with our manager to split ownership clearly. The arguments mostly stopped, and design reviews got shorter."

10. Tell me about a time you gave someone difficult feedback.

"A colleague's presentations were running long and losing the room. I asked if he wanted feedback first, then told him privately that the main point came too late and offered to help him restructure the next one. He was frustrated at first, but his next presentation was half the length and got good responses."

Change and accountability

11. Describe a change you introduced that people resisted.

"I moved our team from spreadsheets to a project tool. People resisted because the spreadsheets were familiar. I started with one project, set it up myself, and showed how much less time the weekly update took. Once a couple of people saw that, they asked to move their projects too. I didn't force the switch for anyone until most of the team was already on it."

12. Tell me about a leadership failure.

"I once agreed to a deadline without checking with my team first. It wasn't realistic, and we missed it, which hurt our credibility with another department. I apologized to them and to my team, and we delivered two weeks later. Since then, I don't commit to dates for my team without asking them first."

13. How did you respond when your team missed a goal?

"We missed our quarterly target for new sign-ups. I didn't want to just push harder, so I went through the funnel with the team to find where people were dropping off. Most of the loss was at one form. We simplified it and hit the target the next quarter. I also started reviewing progress monthly instead of only at the end."

14. What leadership feedback changed how you work?

"My manager told me I was solving problems for my team instead of letting them solve them. It was hard to hear, but she was right. I started asking 'What do you think we should do?' before giving my answer. It took longer at first, but the team got much more independent."

15. Why do you want a leadership role?

"I've found I get more satisfaction from a team doing well than from my own work alone. I've been doing parts of the job already: mentoring, running projects, sorting out conflicts. I'd like to do it properly, with the responsibility that comes with it."

If you've never had a leadership title

Interviewers know many candidates haven't managed anyone, especially for team lead or first-time manager roles. Good leadership examples from individual contributors include leading a project, getting another team to change how they work, onboarding or mentoring a new hire, running a meeting or event, or taking charge when something broke and nobody else did. Be honest about your role. "I didn't manage them, but I was responsible for getting it done" is a perfectly good answer.

For "what would you do if" questions about managing people, see our supervisor interview questions, and for hypothetical scenarios more broadly, our situational interview questions.

Common mistakes

Saying "we" for everything is the most common one; the interviewer can't tell what you did. Next is picking a story where the result is vague or where someone else made the key decision. Some candidates also choose stories that are too small, like organizing a team lunch, when they have stronger ones. And skipping the "what I learned" part makes failure stories sound like excuses.

Practicing your stories

Tell each story out loud and time it. If it runs past two and a half minutes, cut the setup. YesToTheOffer can help you prepare: add your resume and the job description, and read back the transcript afterward to see whether you said what you did and what happened. For help structuring stories, see our STAR answer guide.