"Tell Me About a Time You Showed Leadership": How to Answer (With Examples)
To answer "tell me about a time you showed leadership," tell one specific story where you moved a stuck situation forward without being told to, and show how you got other people to move with you. Structure it with STAR, put most of the time on your actions, and end with a result you can measure.
Here's the trap. Candidates hear "leadership" and reach for a title. No manager title, they assume, means no story, so they talk about "being a team player" and lose the question. Interviewers aren't checking your org chart. They're checking whether you'll take ownership when nobody assigns it. That's a behavior, and almost everyone with a year of work has done it at least once.
Key Takeaways
- Leadership here means influence, not authority. A story without a title is often stronger.
- Pick a story with a real problem, a moment you stepped in, and other people you had to bring along.
- Spend about 60% of your answer on what you did and how you persuaded people.
- End with a number or a concrete change, then one line on what you'd keep doing.
- Prepare for the follow-ups: "What pushback did you get?" and "What would you do differently?"
What the interviewer is actually scoring
Behavioral questions run on one assumption: how you acted before predicts how you'll act again. Our breakdown of behavioral interview questions covers the full pattern. For this one, the scorecard usually has four boxes:
- Initiative. Did you step in, or were you assigned?
- Influence. How did you get people to follow when they didn't have to?
- Judgment. Did you pick the right problem and the right approach?
- Outcome. Did anything actually change?
Harvard Business Review has written for years about leading without formal authority, through credibility and persuasion rather than rank (hbr.org). That's the version of leadership most interviewers are hiring for, because most roles need it every week.
How to pick the right story
Run your candidates through three filters.
There was a real problem. A missed deadline, a broken process, a team pulling in two directions, a client about to walk. "I organized the holiday party" has no stakes.
You stepped in. Somebody could have waited for a manager to fix it. You didn't. The best stories have a clear moment: "Nobody owned it, so I did."
Other people had to come along. Leadership without followers is just working hard. Your story needs at least one person who disagreed, was busy, or had no reason to help you.
Good sources: a project you rescued, a process you rebuilt, a new hire you onboarded when nobody else would, a cross-team handoff you fixed, a conflict you settled. If the story involves a disagreement, our guide to the conflict with a coworker question shows how to keep it from sounding like a complaint.
Structure it with STAR
Use the STAR method (Situation, Task, Action, Result) and weight it on purpose:
- Situation (10%): One or two sentences. Where, when, what was broken.
- Task (10%): What needed to happen and why it fell to you.
- Action (60%): What you did, in order. Say "I," not "we." Name how you persuaded people.
- Result (20%): The number or concrete change, plus what you learned.
Aim for about two minutes. If you want more worked examples of the format, see our STAR method examples.
Example answers
Individual contributor, no title. Marcus, a support specialist:
"Our team's ticket backlog hit about 400 after a product launch, and our manager was out on leave for three weeks. Nobody was assigned to fix it. I pulled a week of tickets and found almost half were the same three login issues. I wrote short reply templates for those three, then asked two senior teammates to review them, because I knew the team would trust their sign-off more than mine. Then I proposed a daily 15-minute triage at 9am. One teammate pushed back on adding a meeting, so I offered to run it and cap it hard at 15 minutes. Within two weeks the backlog was under 100, and the templates became the team standard. What I learned: people follow a plan faster when someone they already trust has checked it."
Early career or student. Priya, a recent grad:
"In my capstone, our five-person team was two weeks from the deadline with no working prototype, because two people were building different versions. I asked everyone for 30 minutes, put both versions side by side, and we scored them against the client's three requirements. One clearly won. I split the remaining work into tasks with owners and set up a shared checklist we updated every night. We shipped on time and the client adopted the prototype for a pilot. I learned to settle disagreements with criteria, not opinions."
Manager. Sam, a team lead in Queens:
"Two of my engineers had stopped talking after a bad release, and code reviews between them were stalling for days. I met with each one alone first to hear the full story, then ran a short blameless review of the release with the whole team, focused on the process gap, not the people. We added one checklist step that would have caught the bug. Review times dropped from three days to under one within a month, and the two of them paired on the next release. I learned that a fix to the process can also fix the relationship."
Notice what all three share: a clear moment of stepping in, a named person or group who needed convincing, a specific move to win them over, and a result with a number in it.
Mistakes that sink the answer
- "We" the whole way through. The interviewer can't hire your team. Say what you did.
- Picking a title instead of a behavior. "I was team captain" is a role. What did you do as captain?
- No resistance. If everyone agreed right away, it wasn't leadership. It was a meeting.
- Hero stories that crush coworkers. Making others look bad reads as a future problem.
- No result. "It went well" is not a result. Find the number, even an estimate you can defend.
Prepare for the follow-ups
Strong interviewers push past your first answer. Have short replies ready for these:
- "What pushback did you get, and how did you handle it?"
- "What would you do differently?"
- "How did the people you led feel about it afterward?"
- "Tell me about a time your leadership didn't work."
That last one is a cousin of the failure question. Pick a real miss, own your part in one sentence, and spend the rest on what changed after.
The bottom line
"Tell me about a time you showed leadership" isn't asking for a title. It's asking for proof you'll move a stuck situation and bring people with you. Pick one story with real stakes, weight it toward your actions, and land on a number.
The fastest way to find that story is to prep against the actual posting. Every Gate Crashers session turns one job posting into three tailored resume versions and a 12-question interview prep guide built from your real experience. $4.99 one time for three sessions, no subscription. See pricing.