PEI
Someone asks what your PhD is about.
You know this topic better than almost anyone in the room.
Then 90 seconds later, you are still explaining the background.
Expertise has become the obstacle.
A consulting interviewer does not need your dissertation abstract.
They need to understand why your work mattered, what you actually did, and what your experience says about you.
Fast.
The scientifically accurate version may be the least useful version
Imagine your research studies a specific signaling pathway involved in neuronal plasticity.
You could begin with the receptor.
Then the pathway.
Then the disease model.
Then the literature gap.
Every sentence may be correct.
The interviewer can still lose the thread.
That is because your research description has two audiences.
A specialist wants precision.
A consultant wants orientation.
Those are not the same communication problem.
Try moving one level upward.
Instead of beginning with the mechanism, begin with the problem:
“I study how brain cells adapt when their activity changes, and what goes wrong in a neurological disorder.”
Now the interviewer has a map.
Technical detail can come later.
For more examples of how to make that translation, read How to Explain Your PhD in a Consulting Interview.
The sentence becomes stronger when your research stops being the main character
This feels strange.
You spent years on the science.
Surely the science should dominate the answer.
Not necessarily.
The interviewer is also learning about you.
What did you own?
What was difficult?
What decision did you make?
What changed because of your work?
Compare:
“My PhD investigates X using Y to understand Z.”
with:
“I led a five-year research project on X, combining experiments and data analysis to answer Z.”
The subject is still there.
But now the interviewer can see the candidate.
Your PhD is context. Your actions are evidence.
Fifteen examples would not help if they all sound like abstracts
The useful patterns are simpler.
A strong one-sentence explanation often contains three ingredients:
- Problem: What are you trying to understand or improve?
- Approach: What did you personally do?
- Meaning: Why might anyone outside your subfield care?
For example:
“I study why some cancer cells stop responding to treatment, using genomic data to identify mechanisms that could point to better therapies.”
Or:
“I model how urban air pollution moves through neighbourhoods so cities can understand where interventions may have the biggest effect.”
Or:
“I study how workplace policies affect nurse retention, combining large datasets and interviews to understand why people leave.”
Different fields.
Same compression.
Then the interviewer interrupts with the question you actually wanted
“That sounds interesting. What was the hardest part?”
Now you are somewhere useful.
You can talk about ambiguity.
Influencing collaborators.
Recovering from a failed experiment.
Prioritizing when resources were limited.
Explaining results to non-specialists.
Those stories connect naturally to consulting.
Your one-sentence explanation was not supposed to finish the conversation.
It was supposed to open the right one.
That is why the same principle matters in your broader introduction. Elevator Pitch Consulting Interviews shows how the research line fits into the rest of your candidate story.
So what should you actually say?
Start with something a smart non-specialist can understand.
Keep one technical term if it genuinely matters.
Remove three others.
Show your role.
Give the work a reason to exist.
Then stop.
If the interviewer wants the mechanism, they can ask.
If they want the method, they can ask.
If they want your publication record, they can ask.
Curiosity is a successful outcome.
The uncomfortable part is that years of work may collapse into twenty words.
That does not make the work smaller.
It proves you understand it well enough to decide which twenty words deserve to survive.