A clinical research fellow sent the same eleven-page document to a university department, a contract research organisation and a mid-size biotech in the same fortnight. The department shortlisted her. The CRO never replied. The biotech recruiter wrote back with one line: "Do you have a resume?" Same person, same work, three readers who wanted three different things on the page.
That is the whole problem with the medical researcher CV. You are one professional, but the document has two legitimate forms, and sending the wrong one reads as a signal that you do not know the sector you are applying to.
The two-document reality
The academic CV is long on purpose. Eight to fifteen pages is normal for a mid-career clinical academic. It carries the complete publication list, every grant, teaching, supervision, peer review activity, committee work, and methods detail down to the assay. A faculty search committee reads it as a record, and an incomplete record looks like a thin one.
The industry resume is two pages, occasionally three for a principal scientist with fifteen years behind them. It carries selected publications, trial experience in screening terms, regulatory literacy, platforms, and results. It is read in under two minutes by a talent partner who is not a clinician, then again by a hiring manager who is.
Where each one belongs:
- Faculty posts, clinical lectureships, fellowships, hospital research units with an academic host, most grant-linked positions: academic CV.
- Pharma and biotech R&D, CRO roles, medical affairs, MSL, regulatory, clinical operations, HEOR, medical writing: two-page resume.
- Hybrid cases such as a translational role in a university spin-out: send the two pages and attach the full CV as a clearly labelled appendix in the same PDF.
The mistake is not having one document too many. It is maintaining only the long one, then hacking it down to two pages the night before a deadline. The compression always eats the wrong things, because the material an academic CV prizes is not the material a biotech screens on. Keep both current and the deadline costs you ten minutes instead of a weekend.
The publication list, which is the section people get most wrong
On the academic CV, the list is complete and grouped. Peer-reviewed articles first, then book chapters, then preprints under their own heading, then conference abstracts. Within each group, reverse chronological order. Number the entries, because reviewers cite them by number. Put your own name in bold and mark your position with a convention you explain once at the top: an asterisk for first author, a dagger for corresponding author, and an explicit note for joint first authorship rather than hoping the reader spots the footnote in the journal.
On the two-page resume it becomes Selected Publications, five to eight entries, and the selection criterion is relevance to the job rather than impact factor. A paper in a modest journal on the exact indication the company is developing beats a middle-author Lancet paper on something unrelated. Close with one line: "Full publication list of 41 peer-reviewed articles available on request", plus your ORCID identifier as plain text.
Three decisions people get wrong:
Middle authorship. Burying it does not help and neither does pretending. If you are fourth of nine on a large multicentre trial, say what you actually did: "Fourth author; ran the biomarker sub-study across four sites and wrote the methods section." That sentence does more for you than the citation alone ever will, because it converts a position in a list into a piece of evidence about your hands.
Preprints. They belong on the list, under their own heading, labelled as preprints with the server name. Filing them silently among peer-reviewed articles is exactly what a careful reviewer catches.
The complete list on a resume. It does not belong in the body. If a form or a recruiter insists on everything, put the full list in an appendix after the two-page resume, with a page break and a header, so the reader sees a two-page document that happens to have a reference attached rather than a nine-page document they have to navigate.
Grants and funding as evidence
Funding is one of the few things on a research CV that carries an external verdict. Somebody else assessed the work and committed money to it. Write it so that verdict is visible.
Each entry needs the funder, the scheme, the amount, the dates, and your role stated in the standard vocabulary: principal investigator, co-investigator, named researcher, or co-applicant. "Involved in funding applications" is worth nothing. "Co-investigator, NIHR Research for Patient Benefit, 284,000 GBP, 2023 to 2026, wrote the statistical analysis plan and the health economics section" is worth a conversation.
Unsuccessful applications still have value if you handle them honestly. A scheme where you were shortlisted, or a resubmission funded on the second attempt, is legitimate on an academic CV under a clearly marked heading. Do not smuggle them in among awarded grants.
On the resume, funding shrinks to two or three lines under your role, and the number matters more than the scheme name. A hiring manager reads a grant total as a proxy for two things: external reviewers trusted you with a budget, and you can write to a specification under a deadline.
Describe studies the way a hiring manager screens them
This is the section that separates a resume that gets a call from one that does not. Industry screens on structured attributes, and if they are not on the page, a keyword search does not find you and a human skimming does not reconstruct them.
For each study, give: phase, study type, indication, number of participants, number of sites, your role, and what you personally touched.
Weak: "Worked on clinical trials in oncology."
Usable: "Clinical Research Fellow, phase II open-label trial in metastatic colorectal cancer, 118 participants across six UK sites. Co-wrote the protocol and two substantial amendments, prepared the ethics submission, sat non-voting on the data monitoring committee, and cleaned and locked the database for the primary analysis."
That version answers, in one entry, the four things a clinical operations manager wants to know before the call: has this person seen a protocol from the inside, have they dealt with a regulator or an ethics committee, do they understand data integrity, and have they worked at multicentre scale rather than on a single-site study of twelve people.
Name the design directly rather than describing it. Randomised controlled, open-label, single-arm, crossover, stepped-wedge, prospective cohort, nested case-control, retrospective chart review. These are search terms. So are the indication and the therapeutic area, which should appear in the words the company uses on its pipeline page.
Regulatory and compliance literacy belongs on the page
Recruiters in clinical research genuinely filter on this, and candidates leave it off because it feels like a given. It is not a given, and the person reading cannot assume it.
Put a short block near the top of the resume covering: GCP certification with the issuing body and the date, ethics and IRB submission experience with the number of submissions if that number is real, informed consent processes including whether you consented participants yourself, protocol deviation handling, pharmacovigilance and adverse event reporting, and data protection in a trial context, which in Europe means pseudonymisation, data transfer agreements and sponsor-side responsibilities rather than the words "GDPR aware".
If you have worked to a specific standard or submission type, name it: ICH-GCP E6(R2), a CTIS submission, an IND or IMPD, ISF and TMF maintenance, an inspection you sat through. Five accurate acronyms beat a paragraph of general claims about rigour.
Techniques and platforms without the tool-list trap
A wall of methods tells the reader you have touched things. It does not tell them what happened next. The rule is result first, method second.
Weak: "Skills: flow cytometry, qPCR, REDCap, SPSS, R, Python, ELISA, immunohistochemistry."
Better, inside an experience bullet: "Built the REDCap data capture for a 400-participant cohort and cut query resolution time from eleven days to three by adding validation at entry."
Keep a short skills block for the search engine and the compliance check, but do not let it carry the argument. Three or four bullets where a technique produced a measurable outcome beat twenty listed platforms, and they give the interviewer somewhere to start.
If you are leaving the university
One short section, because this is a whole discipline of its own and there is a dedicated article on converting an academic CV into an industry resume. The core move is to stop describing the research question and start describing the delivery: the budget, the timeline, the people you coordinated, the deadline you hit, the protocol you shipped. A thesis becomes a three-year project with a fixed deliverable and a sole accountable owner. A lab rotation becomes cross-functional work.
Conferences, posters and talks: what earns space
On the academic CV, all of it, grouped and dated.
On the two pages, the bar is high. What earns space: invited talks, chaired sessions, a plenary, an award for an abstract, and a poster only if the topic matches the role exactly. What does not: routine departmental seminars, attendance without presenting, the long tail of local meeting abstracts. With thirty abstracts, one line stating "30 conference abstracts, including 7 oral presentations at ASCO and ESMO" is shorter and more impressive than five listed individually.
Keep both documents alive. The two-page version gets you into industry rooms, the long one keeps academic doors open, and most medical research careers cross that line at least once.