PEI
You never managed a department.
You never had ten direct reports.
You never approved anyone's budget.
So when an interviewer asks for a leadership example, your mind goes blank.
Then you remember you convinced six people to change what they were doing without having authority over any of them.
That may be the better story.
Academic leadership rarely arrives with the title you were expecting
A PhD is full of situations where responsibility appears before authority.
You mentor a student.
Coordinate experiments across labs.
Organize a seminar series.
Train new researchers.
Set the direction of a project.
Manage a collaboration.
Resolve disagreement over authorship or priorities.
None may appear on your CV under the word “manager.”
The behaviour can still be leadership.
Titles describe hierarchy. Stories reveal influence.
If you want to see how consulting interviews translate these experiences, read How to Show Leadership in Consulting Interviews as a PhD Candidate.
The story becomes interesting when somebody could have said no
Suppose you trained three undergraduate students.
Useful experience.
But simply saying, “I supervised three students,” tells the interviewer very little.
Now add friction.
One student was falling behind.
The project deadline could not move.
Your supervisor had little time.
You redesigned the workplan, changed how you checked progress, and helped the student recover without doing the work for them.
Now something happened.
There was a choice.
There was resistance or uncertainty.
There was consequence.
Leadership starts becoming visible when the outcome was not automatic.
Your strongest example may involve someone more senior than you
This is where PhDs can have surprisingly powerful stories.
You analyze the data and believe the project should change direction.
Your supervisor disagrees.
You cannot order them to change their mind.
So what do you do?
Maybe you build a concise comparison of both approaches.
Maybe you run a small pilot.
Maybe you bring in evidence from a collaborator.
Maybe you change your own position after discovering their concern was valid.
The important part is not “winning.”
It is how you moved the group toward a better decision.
That sounds very different from:
“I showed leadership by doing my experiments independently.”
Independence is useful.
Leadership requires other people.
A small event can reveal more than a large title
Consider these two candidates:
Candidate A was president of an association but mainly attended meetings and approved existing plans.
Candidate B had no formal title but noticed a collaboration was failing, brought three stakeholders together, redesigned responsibilities, and recovered a delayed deliverable.
Which story gives the interviewer more to explore?
That is why searching only for titles can hide your best material.
Look instead for moments where you:
- created direction when people were uncertain;
- influenced people with competing priorities;
- helped someone perform better;
- took ownership beyond your formal responsibility;
- aligned a group around a difficult decision.
For worked examples of what those stories can sound like, read Leadership Story Guide with Three Consulting Examples.
Then comes the question that separates leadership from being helpful
“What would have happened if you had done nothing?”
If the answer is “probably the same thing,” your role may not be strong enough yet.
If the project would have stalled, the student might have failed, the collaboration could have broken, or the team would have chosen a weaker path, now your intervention has weight.
Leadership needs a counterfactual.
Something changed because you acted.
That change may involve five people.
It may involve one.
The budget may be $5 million.
It may be zero.
The interview is not asking whether your PhD secretly turned you into a corporate executive.
It is asking whether, when a group needed someone to create movement, you ever became that person.
You probably did.
The better question is whether you noticed when it happened.