The Entry-Level PhD Paradox

Why many companies ask for doctoral training, but expect new graduates to already have industry experience

Jun 05, 2026

The first time I interviewed for an industry role after my PhD, I didn't get the job because they told me I was too academic for the entry-level position that literally required a PhD.

I remember being very confused by that feedback, not because I thought I necessarily deserved the job, but because I had just spent years earning the exact credential they listed in the job description. Then, once I showed up with that credential, it somehow became part of the reason I wasn’t the right fit.

At the time, I assumed this was mostly my fault. Maybe I had explained my research badly, I hadn’t translated my experience well enough, or maybe I sounded too much like someone who had just come from a university instead of someone who already knew how to operate inside a company.

And to some extent, that may have been true. I do think PhD students need to learn how to explain their work a little differently when they apply to industry roles. Most companies don’t actually care about your thesis, and they’re not going to automatically understand why the skills you built during your doctorate matter outside your specific field.

But the more I went through the industry transition, the more I realized that this problem was not just about how PhDs communicate. A lot of the difficulty comes from the fact that companies often ask for PhDs while being very unsure of what they actually want from people who have them.

PhD students are told over and over that they need to reframe their experience. They need to rewrite their CV, learn the right language, talk about projects instead of research, explain outcomes instead of methods, and prove they can operate outside an academic environment. So many of us take that seriously because we know the transition is real, and we know a company is a different environment than an academic lab.

But then you apply to a role that explicitly requires a PhD, and the interview process makes you feel like you have to convince them that the degree isn’t a liability.

If a role requires a PhD, then the person applying is by default going to have academic experience. And if you don’t want someone with an academic mindset and training, then why require the PhD?

Of course, there are habits that need to be different if you’re working in industry versus academia. A company can’t operate like a dissertation committee, and not every decision can wait until every possible variable has been accounted for. Industry usually requires faster judgment, clearer communication, more comfort with incomplete information, and a stronger understanding of what matters commercially.

But companies train people into new environments all the time. A new employee usually has to learn the company’s systems, tools, workflows, priorities, internal politics, and expectations. Even someone with the right degree and the right background still has to learn how the organization actually works once they get there.

For some reason, with PhDs, that learning curve is not seen as normal onboarding, but as evidence that the person is too academic, inexperienced, or difficult to translate into the role.

And this leaves new PhD graduates in a difficult position. You spent years getting the degree that these jobs require, and then they tell you that your lack of industry makes you risky. It’s like you are expected to have the maturity and expertise of someone who completed a doctorate, but also the practical experience of someone who spent those same years inside a company.

If a company wants someone who already has industry experience, understands corporate workflows, knows how product or business priorities are set, and can immediately operate without much training, that’s completely reasonable. Some roles genuinely need people with several years of direct industry experience. But if that’s the case, the job description should say so clearly instead of hiding a mid-level expectation inside an entry-level posting.

And if a company does actually want to hire new PhDs, then it should be prepared for the fact that they will have academic backgrounds. They may need help learning what to emphasize, what to let go of, how to communicate differently, and how to make decisions in a faster and more commercially constrained environment.

That’s the whole point of hiring someone at the beginning of a transition. What doesn’t make sense is requiring a PhD and then acting surprised that the person in front of you sounds like someone who just finished one.

If I were in your shoes...

If you are a PhD student or recent graduate trying to move into industry, I would still take the translation process seriously even though I think companies need to do much better.

Most people outside your field will not automatically understand what your research required, how hard it was, or why it should matter to them. You need to make that clear without sounding defensive or expecting them to fill in the gaps for you.

I would practice explaining your work in terms of decisions, problems, constraints, tools, outcomes, and tradeoffs. What did you actually have to figure out? What changed because of your work? What did you build, analyze, manage, improve, or communicate? What kinds of uncertainty did you deal with, and how did you make progress anyway?

I would also try to get some kind of applied experience as early as possible. That could be an internship, consulting project, freelance work, startup experience, industry collaboration, public writing, portfolio project, or even informational conversations that help you understand how people in companies talk about work.

It doesn’t always solve for this issue (I did an industry internship and still was told this!), but it’s at least evidence you can point to for your ability to think in an industry environment.

I would also try not to internalize every rejection as evidence that you’re the problem. Sometimes your interview could have been better, your CV could have been clearer, or your examples could have been more relevant. But sometimes the role is simply asking for a person who doesn’t really exist, or the company is hoping to find someone with more experience willing to take an entry-level salary.

In My Orbit

I’ve always been a pretty big tennis fan, and I was extremely ill this week so while I was doing nothing trying to recover on the couch I watched the nearly 6 hour match between Frances Tiafoe and Matteo Arnaldi at Roland-Garros. It was amazing to see them go back and forth the entire match, and continue playing at the highest level for so many hours. I can’t imagine the energy in the stadium that night, and I hope to one day attend in-person to experience it myself!