What got me hired wasn’t my PhD
On my first day at a contract research organization (CRO) the quality assurance (QA) staff had handed me a pile of SOPs and showed me the lab and the LC-MS/MS instrument. I read the SOPs for about seven days. Then I started reading the instrument manuals and instructions. When I started reading the in-house methods we were running, I started comparing them against journal articles, taking notes on what could be improved.
My manager observed me reading journal articles, and one day he said “You’re spending too much time on the computer.”
I didn’t understand the meaning at that time. I thought the lab had problems. I was reading about how to solve them. In a graduate study, that was my main job. In industry, apparently, it wasn’t.
It took me at least six months to understand the differences that I didn’t know and no one taught me.
I want to write this for the version of me who needed it in 2017, and for any postdoc reading this who thinks they’re ready for industry because they have the technical skills.
Let me share my experience here.
Your PhD made you industry-adjacent, not industry-ready
This is the part nobody says out loud, especially not to your face during interviews.
A postdoc walks into a hiring conversation believing they have a portable, valuable skillset. Analytical chemistry, instrumentation, problem-solving, communication. Five years of high-end research. Publications. A defended thesis.
The hiring manager hears something different.
They hear: a smart person who has spent five years for novel methods/product in an environment with less time pressure. In most industry novelty is not the goal. Industry wants reliability in an environment with finite time and finite budget. Those are nearly opposite skill profiles.
When I later became the person reviewing CVs, I saw this gap from the hiring side. Let me give you an anonymous example, a candidate wrote “expert in LC-MS method development.” The hiring committe asked: “Tell me about validating a method to ICH Q2.”. Or: “Tell me about transferring a method between two instruments.” Or: “Walk me through how you’d build a stability-indicating method for a formulated cosmetic product.” The candidate struggled to answer these questions.
These are not exotic industry questions. They’re week-three questions in any analytical lab. And most postdocs can’t answer them, because their PhD trained them in research, not in production-grade analytical work.
That’s not a failing. It’s a mismatch between academic teaching and industry expectations.
What actually gets you hired
The postdocs I watched get hired into good roles did three things differently from the ones who didn’t.
One: they got specific.
“I have analytical skills” gets ignored. “I can develop LC-MS methods for impurity profiling in small-molecule pharmaceuticals and validate them to ICH Q2(R2)” get a high chance of a phone screen. The first is a posture. The second is a job description the hiring manager can match to an open position.
The mistake postdocs make is believing specificity narrows their options. It does the opposite. Vague candidates are invisible. Specific candidates are findable.
If you’re a postdoc reading this, the exercise is: write down the five most specific things you can do, in the language a hiring manager would use, not the language your supervisor would use. I urge you to do this as a first piece of work.
Two: they learned to translate.
Academic CVs describe what you did. Industry CVs describe what you delivered. Same content, different framing.
Academic: “Developed novel SPME-LC-MS/MS method for quantification of low-abundance metabolites in complex biological matrices.”
Industry: “Developed a sensitive analytical method that reduced sample preparation time by 40% and enabled detection limits 10x below regulatory threshold, supporting client deliverables in pharmaceutical development.”
The work is the same. The framing decides whether the hiring manager keeps reading.
For most postdocs this translation does not happen because they’re surrounded by people who reinforce the academic framing.
Three: they stopped trying to be impressive.
This was the hardest one for me, and I saw it in several postdoc CV I read. The instinct from academia is to demonstrate intellectual range, theoretical depth, breadth of knowledge. The instinct from industry hiring is to find someone who solves a specific problem reliably.
The postdocs who got hired weren’t the most impressive ones in interviews. They were the ones who could describe, calmly and concretely, exactly what they would do in the first 90 days of the role. They sounded like they were already doing the job, not like they were defending a thesis.
On my first couple of weeks, after reading all the required documents and signing the official documents, I started working with a senior chemist who has been industry for many years. During my instrument training, I tend to think that I know all of these, but letter I found I was doing so many mistakes in specific order the work has to be done, the style I would have to write, the form that I would have to use.. all these took time to master.
What that first month at the CRO actually was
When my manager warned me for reading too much, he was trying to tell me something that would change my perspective.
In industry, your job isn’t to know everything about the methods you run. It’s to deliver the results the client paid for, on time, in the right format. The learning happens around the work, not instead of it. The optimization happens over months, not in the first three weeks.
It took me about six months to internalize this. It took me about two years to actually be good at it. The learning curve wasn’t technical, it was cultural. And, the technical skills I’d been so proud of weren’t the bottleneck. The bottleneck was learning to deliver on someone else’s timeline, in someone else’s format, for someone else’s purpose.
What I’d tell a postdoc deciding to leave
Three things.
You’re probably going to leave. Most postdocs do. The academic job market hasn’t gotten better, and waiting one more year hoping it will is usually waiting one more year. Decide sooner rather than later, even if the decision is hard.
But leave toward something specific, not away from something painful. The postdocs who flourish in industry are the ones who picked a specific direction and pursued it. The ones who struggle are the ones who treated industry as a single destination called “not-academia.”
And give yourself a year of space. The cultural translation takes time. You’ll feel slow, confused, occasionally stupid, in ways you haven’t felt since your first year of grad school. That’s normal. It passes. The ones who quit industry in year one usually quit during that disorientation phase, mistaking it for a sign they made the wrong choice.
It wasn’t the wrong choice for me. It probably isn’t for you either.
The hardest part isn’t whether to leave. It’s translating yourself into someone the next industry actually wants to hire.
I’m still working on it, almost ten years in.