How to translate a PhD into a CV that industry hiring managers will actually read

Somewhere on your hard drive there is a CV that is four to six pages long, set in a serif font, and organised into sections called Publications, Conference Presentations, Teaching, Grants, and Invited Talks. That document did its job. It got you through viva panels, funding rounds, and possibly a postdoc. It is also, for the purpose of an industry job search, almost useless.

That is not a judgement on the work. It is a judgement on the format. An academic CV is written for completeness, because the people reading it are peers who want to see everything and will weigh it themselves. An industry CV is written for relevance, because the person reading it is not a peer, has a stack of other applicants, and is trying to answer one question quickly. Can this person do the job we are hiring for, and is that obvious from the page?

If your PhD experience is buried under a publication list and described in the passive voice, the honest answer from their side is that they cannot tell. So they move on. The fix is not to hide the doctorate. It is to translate it, which is the same move every career changer has to make.

The PhD is experience, not education

The single biggest structural change is where the PhD sits on the page. On an academic CV it goes under Education, one line, degree and institution and year. On an industry CV that placement is a mistake, because it tells the reader you spent five years obtaining a qualification rather than five years doing work.

Move it. Put it in your experience section as a role.

Doctoral Researcher, Department of Computer Science, University of Edinburgh, 2020 to 2025

Then write bullets underneath it the way you would for any job. What was the problem, what did you build or analyse, at what scale, with whom, and what came out of it. The degree still appears in Education as a single line so nobody thinks you left it out. But the substance of what you did lives where a hiring manager expects to find substance.

This one change reframes the entire conversation. You are no longer a fresh graduate with an unusually long education section. You are someone with several years of independent project delivery under real uncertainty, which is a fair description of most doctorates and a genuinely rare thing to be able to say. Prospects makes the same point in its guide to what comes after a PhD. Outside academia you are hired for what the doctorate proves you can do, not for the doctorate itself.

Translate research into problem, method, scale, outcome

Academic writing is trained to hedge. Results are suggested. Findings may indicate. Further work is needed. That register is correct for a paper and wrong for a CV, because a hiring manager reads hedging as uncertainty about whether you actually did anything.

Every research bullet needs the same four parts a good industry bullet has. The problem you were solving, the method or tool you used, the scale you worked at, and the outcome. Here is what the translation looks like in practice.

Academic version. “Investigated the application of graph neural networks to molecular property prediction, contributing to two first-author publications.”

Industry version. “Designed and trained graph neural network models to predict molecular properties across a dataset of 400,000 compounds, cutting screening time for the group’s experimental collaborators from weeks to days. Work published in two first-author papers.”

Same truth. The second version names the scale, names the outcome in terms someone outside the field can understand, and treats the publications as evidence of delivery rather than the point of the exercise.

A few more translations that come up constantly.

“Supervised three MSc students” becomes “Mentored and managed three master’s students through six-month research projects, all of whom submitted on time.”

“Secured funding through a competitive grant application” becomes “Wrote and won a competitive grant proposal worth £120,000, then managed the budget across two years.”

“Developed a novel pipeline for” becomes “Built a data processing pipeline in Python that replaced a manual workflow and ran nightly on the department’s cluster for three years.”

“Presented at international conferences” becomes “Presented technical work to audiences of up to 300 at four international conferences, including one invited talk.”

Notice what disappears. The word novel, which means nothing to a recruiter. The passive constructions that hide who did the work. And the reliance on the reader already understanding why the research mattered.

Say what you did, not what the group did

Academic work is collaborative and the writing reflects it. Papers have six authors. Grants have co-investigators. Lab websites describe what “we” found. That habit follows people onto their CVs, where it quietly destroys their case, because the reader cannot tell whether you led the work or fetched coffee for the person who did.

Be specific about your part. If you designed the experiments, say so. If you wrote the analysis code, say so. If your contribution to a six-author paper was the statistical modelling, write that the statistical modelling was yours. This is not arrogance. It is the only way the reader can price what you actually bring.

The same rule applies in the other direction. Do not claim ownership of the whole project if you owned one component. Anyone who interviews you will ask, and a doctorate that has been inflated on paper is worse than one that has been described accurately.

Compress the sections that academia cares about

Publications, conference presentations, teaching, awards, and professional memberships all get radically shorter. Not deleted. Shortened.

For publications, one line. “Eleven peer-reviewed publications, including four first-author papers. Full list on Google Scholar.” Include a specific paper only if the role is close enough to the topic that the title itself would mean something to the hiring manager. For most applications it will not.

For teaching, fold it into the doctoral researcher bullets if it demonstrates something the role wants, such as communication or mentoring. Otherwise a single line under Additional Experience is plenty.

For talks, awards, and memberships, apply the same relevance test you would apply to any hobby or side project. Does this tell the reader something useful for this specific role that the rest of the CV does not already prove? If not, cut it. If you find that painful, remember that the full record still exists. You are not erasing it. You are choosing not to lead with it.

Write a summary that names the job, not the thesis

The top of your CV should not be your thesis title. It should be two or three sentences that say what kind of role you are targeting and what evidence backs that up.

A weak version reads like this. “PhD graduate in computational biology seeking to apply my research skills in an industry setting.”

A stronger version reads like this. “Machine learning researcher with five years’ experience building and deploying predictive models on large biological datasets, now moving into applied ML engineering. Comfortable owning a problem from ambiguous question through to production code and published result.”

The second one tells the reader what you are, what you want, and why they should believe you can do it. It also uses the language of the roles you are applying for rather than the language of your department. That matters because most applications pass through applicant tracking systems before a human sees them, and those systems are matching on the advert’s vocabulary, not yours.

Build the skills section from the advert, not from your discipline

Your skills section on an academic CV is probably organised by scientific technique. Your skills section on an industry CV should be organised by what the job advert asks for.

Read the advert. Pull out the tools, languages, frameworks, and methods it names. If you genuinely have them, list them using the advert’s wording. If the advert says PyTorch and your CV says “deep learning frameworks,” some screening systems will not connect the two. If it says stakeholder communication and you wrote “liaised with collaborators,” same problem.

Discipline-specific jargon goes unless the advert uses it. A recruiter for a data science role does not need to know the names of the assays you ran. They need to know you can handle messy data at scale, write production-quality code, and explain results to people who are not specialists.

Different roles want different slices of the same PhD

Here is the part that most PhD job seekers get wrong, and it is the same mistake experienced professionals make in every field. They write one industry CV and send it everywhere.

A doctorate is a large body of work and different roles value different parts of it. A research scientist role at a lab wants your publication record and your methodological depth. A machine learning engineer role wants your code, your pipelines, and your evidence that you can ship. A data scientist role wants your statistical judgement and your ability to explain findings to non-specialists. A product or consulting role wants the project management, the stakeholder handling, and the proof that you can deliver under uncertainty.

All of that is in your PhD. None of it should be on every CV at the same weight.

The practical solution is to keep the complete record in one place and generate each application from it. That is what OutRung is built for. You keep one master profile with the full doctorate broken down into projects, methods, tools, outcomes, publications, teaching, and everything else. When you find a role worth applying to, it scores how well your evidence matches what the advert is actually asking for, shows you the gaps, and generates a tailored CV that pulls the relevant slice forward. The research scientist version and the ML engineer version come from the same profile. You just stop rewriting the document by hand every time.

Common mistakes worth avoiding

A few things that reliably make a PhD CV weaker in industry.

Length. Two pages is the ceiling. Naturejobs puts the same contrast in numbers: an academic CV commonly runs four to five pages or more, while an industry resume is typically one or two. One page is often stronger if the doctorate is your only substantial experience. Nobody in industry is going to read page four.

LaTeX formatting that fights the parser. Two-column layouts, custom section headers, and heavy typographic styling often break in applicant tracking systems. Use a plain single-column document with standard headings.

Putting Dr in front of your name. It is not wrong, but for most roles it reads as a signal that you expect the title to matter. Let the PhD entry do the work.

Describing the postdoc as if it were still education. A postdoc is a job. List it as one, with bullets, in the experience section.

Apologising for the lack of industry experience in the summary. You have years of independent project delivery. Frame it that way and let the reader decide whether it counts. It usually does.

The honest version

A doctorate is one of the hardest and most self-directed projects a person can complete. The problem is not that industry does not value it. The problem is that the document academia trained you to write actively hides the parts industry values most.

Move the PhD into experience. Translate every bullet into problem, method, scale, and outcome. Compress the academic sections. Write a summary that names the role. Build the skills section from the advert. Then tailor each version to the job in front of you instead of hoping one generic translation works for all of them.

You did the work. Now write it down in a language the person hiring can read.