INTERVIEW QUESTION
Tell me about a time you showed leadership: how to answer without a manager title
Show leadership without a title: what people agreed to that they had opposed, and how you got time from people who don't report to you.
If you've never managed anyone, this question can feel like a trap. You search your memory for a time you were in charge, find nothing with a title attached, and end up describing a project where you happened to be the most senior person in the room.
Most leadership questions aren't asking for a title. They ask whether you got people to do something they weren't going to do, when you couldn't tell them to. That covers most of the work engineers, analysts, designers, product managers, program managers and consultants already do.
So the strongest leadership answers say two things clearly. What did people agree to that they had opposed before? And how did you get time committed from people who don't report to you? If the story is mostly about getting groups who wanted different things to one decision, it's a stakeholder management question instead.
What counts as leadership when you don't manage anyone
Interviewers count it as leadership when you changed what a group of people did, whether or not you could tell them to. In a 2019 recruiting video, Google said it doesn't just look at job titles when it assesses leadership, because different team members will need to step into leadership roles and contribute.
That gives you more stories than you think. Spotting a gap nobody owned and fixing it, proposing a change and getting others to adopt it, or mentoring someone through a hard project all count. A practitioner on Reddit lists the same things: finding gaps, suggesting improvements, owning problems and mentoring.
Match the scope to the level you're applying for. An early-career candidate can lead within their own team, such as changing how reviews work. A senior candidate is expected to have moved people in other teams, or someone more senior than them.
If you have little work experience, look wider. A candidate on Reddit said they had “zero experience” of influencing anyone, and the advice they got was to look at school, clubs, volunteering and group projects. Running a society's event or covering for a supervisor during a busy shift both work.
This page is about moving people who don't report to you. If the question is about your part in shared work, or helping a teammate who was struggling, the teamwork guide covers it. For a leadership story, the moment you choose needs a clear point where someone changed their mind.
What interviewers listen for
A leadership story without resistance is just a plan that went well. The interviewer needs to hear who disagreed, why, and what they agreed to in the end. Without that last part, there's no evidence that you led anything.
They also want to see you adjust your own behavior to persuade someone, as a well-supported reply in a software-careers thread explains. Repeating the plan more firmly doesn't count.
Agreement in a meeting is only half of it. When people don't report to you, their time belongs to someone else's plan: their manager has goals for the quarter, and your project isn't in them. The strongest answers show how you got a specific commitment anyway: a named person, a number of days, a date.
Trust makes both halves easier. A product manager on Reddit says influence without authority starts with trust: being honest with engineers and sharing more business context than you have to, which makes it easier to ask for help later. The order you tell the story in should make each half easy to hear.
How to tell it
Keep the setup short, because most of the time belongs to the objection and what you did about it.
What you asked for. One sentence: the change, and who had to make it.
Their objection, fairly. Give the practical reason behind it. Most resistance comes from cost or risk to the other side: extra work, a missed goal, a team that will carry the support load. Name what the other team was measured on and what your request would cost them.
What you did to bring them along. You might bring evidence they already trusted, or change your proposal because their objection was right. You might talk to a key person one to one before the decision meeting, which a PM thread reply recommends for clearing blockers early.
How you got their time. The common moves are making the work smaller, doing the parts only you can do, and moving your own date so theirs works. If none of that is enough, the decision belongs to the people who own their priorities, usually their manager and yours.
Follow-through. Say how you checked that the committed time was actually spent, and what happened when something slipped.
An honest partial win is fine. If you didn't persuade them at all, it's a failure question, and Tell me about a time you failed covers how to tell it.
If you practice in Kora, you pick your role, answer out loud, and get a follow-up when your answer leaves out how you got people to commit. The examples below show what that commitment sounds like for each role.
Example answers
In each made-up stronger answer, you can find the sentence where someone who didn't report to the candidate agreed to something they had resisted. Check whether your own answer has that sentence.
Software engineer
Question: “Tell me about leading people who did not report to you. How did you get them on board?”
Weaker
“I led the effort to retire our old internal search API. I wrote a design doc, presented it at the architecture review, and everyone agreed it was the right thing to do. Over the next few months the teams migrated, and we turned the old API off.”
Agreeing in a review cost nobody anything. The answer skips the part interviewers want: how the candidate got other teams to spend their own time on the migration.
Stronger
“Our old search API was costing us an outage a month, and three other teams still called it. I owned the new one, but I couldn't make them move, and none of them had the migration in their plans.
The orders team pushed back hardest. Their lead said a migration would take a full sprint they didn't have. I asked to see their calls to the old API, and most were one query pattern repeated.
So I offered to write the first change myself, covering that pattern, with one of their engineers reviewing it. That cut their part to about three days, and their lead agreed to put it in the next sprint.
Once orders had moved, I used their change as the template for the other two teams. All three were off the old API within the quarter, and the monthly outages stopped.”
The resistance is specific and fair, the candidate made the ask smaller by doing the part only they could do, and the commitment is a named sprint, not a nod in a meeting.
Follow-ups to expect: What did you do to get them to commit time to it? How did you keep track of progress across the teams?
Product manager
Question: “Tell me about persuading someone who disagreed with you and did not report to you.”
Weaker
“Our head of design didn't want to launch the new checkout until it was perfect. I showed her the data on how much revenue we were losing every week, and she eventually came around. We launched a month earlier as a result.”
The designer's concern is reduced to perfectionism, and the candidate gave nothing up. It sounds like pressure with a revenue number, not persuasion.
Stronger
“I wanted to launch our redesigned checkout in two stages: the new payment step first, the rest a month later. Our head of design opposed it. She'd seen half-finished redesigns ship and never get completed.
Before the planning meeting, I met her one to one and asked what would make a staged launch acceptable. She said the risk was the second stage being dropped, and that the old and new styles side by side would look broken.
So I changed the proposal. Engineering committed the second stage's sprint in writing before we started, and her team got two days to restyle the old screens so the joins didn't show.
She agreed and backed the plan in the meeting. The payment step shipped first and cut failed payments by a fifth, and the second stage shipped on its committed date.”
The objection is stated fairly, the candidate changed the plan because of it, and what she agreed to that she had opposed is clear: a staged launch.
Follow-ups to expect: Did you change anything in your proposal because of their objections? How did you make sure they followed through?
Product designer
Question: “Tell me about a time you set direction for a product and got people behind it.”
Weaker
“I had a vision for a much simpler settings area, so I created a set of high-fidelity mocks and a strong presentation. The team was really excited, and it became the direction for the next year.”
Nobody resisted, so the story shows a good presentation, not leadership. The direction itself is vague, and nothing shows people acted on it.
Stronger
“Our admin settings had grown into eleven separate screens, each owned by a different team. I proposed one rule: every setting lives on the page for the thing it changes, not in a central settings area.
The PM and the engineering lead both thought it was a redesign with no customer asking for it. So I showed them twelve support tickets from that month where admins couldn't find a setting, and recordings of three admins hunting through the screens.
The engineering lead was still worried about moving everything at once. We agreed to apply the rule only to new settings and to the five most-searched existing ones.
Both signed off, and it went into the quarter's plan. Two other teams have since followed the rule in their own features, and setting-related tickets fell by about a third.”
The direction fits in one sentence, the evidence was chosen for the people who doubted it, and the phased compromise is why it was actually adopted.
Follow-ups to expect: Did anyone on the team push back? How did you test the direction before committing to it?
Data analyst
Question: “Tell me about a time you raised the standard of work on your team.”
Weaker
“I noticed our dashboards had a lot of errors, so I took it upon myself to check every query before it went live. The error rate went down a lot, and my manager praised my attention to detail.”
Checking everything yourself is diligence, not raising a standard. The rest of the team didn't change how they worked, and nothing would last if the candidate left.
Stronger
“Twice in one quarter, a number in the weekly executive report had to be corrected after it went out. Both came from SQL changes nobody else had looked at. I proposed that any query feeding that report gets a second analyst's review.
Most of the team opposed it. They were already stretched, and they expected reviews to sit in a queue for days.
So I asked for a four-week trial with two limits: only queries feeding that one report, and reviews done the same day. I wrote a ten-point checklist from the two errors and reviewed the first batch myself.
There were no corrections during the trial, and reviews took about twenty minutes on average. The team voted to keep it, and two other analysts now run reviews without me.”
The team's objection about time is taken seriously, the trial is designed around it, and the standard keeps running without the candidate, which is the evidence it stuck.
Follow-ups to expect: What standard did you introduce or change? How did you get other people to adopt it? How did you check the standard was being followed?
Program manager
Question: “Tell me about getting a team that didn't report to you to do something for your program.”
Weaker
“My launch needed a security review, but the security team was backed up. I escalated to my director, who talked to their director, and the review was done the following week. Escalating early saved the launch.”
Escalation can be right, but here it's the whole story. The security team's position never appears, and nothing shows the candidate tried to make the request workable for them.
Stronger
“Our launch of a new payments partner needed a security review, and the security team's queue was six weeks long. Our date was four weeks away. Their lead said every team claimed to be urgent and the queue was the fair way to handle it.
I asked what made reviews slow. She said most of the time went on chasing missing architecture details and data flows.
So I had our engineers fill in her team's review template completely before anything was submitted, and I moved our launch date by a week. With that, she agreed to assign two reviewers for three days.
The review found one issue, which we fixed before launch. We went live a week later than the original date, and her team now asks every program to submit the completed template up front.”
The candidate respects the other team's reason, changes the request so it costs them less, and gets a specific commitment: two reviewers for three days.
Follow-ups to expect: What did they end up agreeing to? How did you make sure they followed through?
Consultant
Question: “Tell me about a time you led a team through a difficult situation.”
Weaker
“A client's planning team stopped cooperating halfway through our project, and the team was stressed. As the team lead, I kept everyone motivated, escalated to the partner and made sure we delivered on time. The partner was very happy with the result.”
Motivation and escalation are the default response to any problem. There's no decision the candidate made or reasoning behind it, which is what consulting interviewers probe.
Stronger
“I was leading two analysts on a pricing review for a logistics company when the client's head of planning stopped sending data after a tense workshop. Our early numbers had suggested her team's forecasts were off, and she'd taken it as criticism in front of her boss.
The analysts wanted to escalate to our partner and her COO. I thought that would confirm her fear that we were there to judge her team, so I asked to meet her alone first.
I told her what we'd got wrong in how we'd presented it, and asked what she needed. She agreed to share three months of data instead of the full year, if her team saw our findings before anyone else.
That afternoon I reset the analysts' plan around the narrower data, and explained why we weren't escalating. We hit the steering date, and she later sent the remaining months herself.”
The candidate explains the reasoning before the action, chooses not to escalate for a stated reason, and leads both the client relationship and the team's change of plan.
Follow-ups to expect: What did you do to keep the team motivated? How did you organize the work?
Questions only people managers get
Some leadership questions assume you manage a team: how you manage people, how you handled an underperformer, what you delegated, and a hiring decision you made. If you're applying for your first management role, expect a few of these alongside the questions above.
They listen for the same thing as every other leadership question, applied to people who do report to you. Say what you expected, how you found out it wasn't happening, the conversation you had, and what changed afterward. For an underperformer, include what support you offered before any formal step.
For delegation, name what you handed over, why that person, and how you checked progress without taking the work back. For a hiring decision, say what you were looking for and what evidence settled it.
If you haven't managed anyone yet, say so, then give the nearest real example, such as leading interns or onboarding a new hire. People moving from individual work into a lead role are often asked about handling low-level conflict and knowing when to escalate, according to a reply in an interviews forum. Have a story ready for each.
What makes the answer go wrong
Whether or not you manage anyone, most weak answers describe a project rather than a moment when someone changed their mind. These are the common versions:
- Views instead of a story. Saying what leadership means to you. A reply on Reddit makes the point plainly: specific examples are much better than vague generalizations.
- Nobody to persuade. If everyone agreed from the start, there was nothing to lead.
- Nothing given up. Expect a follow-up asking whether you changed anything because of the objections. A story where you gave nothing up sounds less like persuasion and more like pressure.
- Going over someone's head. Escalating can be right. Say that you went to the person first, understood their reason, and took a clear trade-off to both managers together.
- A yes with no time behind it. Agreement in a meeting, with no named person, days or date, leaves the interviewer guessing whether anything happened.
Other ways it gets asked
The same stories usually work for several wordings. What changes is which part you spend the most time on.
“Tell me about a time you led without authority.” This is the core question on this page, and the software engineer and program manager examples answer it directly.
“Tell me about a time you led a team through a difficult situation.” Spend the time on what made it hard and what you did as the lead, such as a changed plan, a hard message or redistributed work. Explain why you chose that response; McKinsey's interviewing page asks candidates to lead with reasoning rather than actions.
“Tell me about a time you set direction and got people behind it.” Explain the direction in one sentence, then how you explained it to the people who had to act on it.
“Tell me about a time you raised the standard of work on your team.” Name the standard, the resistance to it, and evidence that people kept to it after you stopped pushing.
“What's your leadership style?” Answer with one short story, then name the style it shows. Even phrased as a hypothetical, it needs a real example behind it.
The STAR method examples show how to put any of these answers in order.