Academic CV for PhD Applications: Structure and an Example
Academic CV for PhD applications: the two-page evidence format, a proven page budget, project-entry patterns and an honest publications section.
The two-page PhD CV, section by section
An academic CV for doctoral admission is a two-page evidence document, not an autobiography. The dominant block is research: education with grades and thesis title, then research experience in reverse-chronological entries that each carry a question, a method and an outcome. Skills follow only when they serve the project — programming languages, lab techniques, statistical packages — and teaching, awards and service fill the remaining space. Publications go under a clear heading even when the only entry is 'under review', with status stated honestly. Everything else — school prizes, unrelated jobs, generic soft-skill lines — costs you the reader's attention for zero return.
Length discipline is the test of judgement: two pages at application stage, with the project entry format shown in the sample (three to five lines: role, question, method, result, product) doing the compression. The chart shows a proven page budget; the table maps sections to the evidence admissions panels say they look for.
| Section | Lines | Evidence it proves |
|---|---|---|
| Education and grades | 4-6 | Threshold eligibility, class of degree |
| Research experience | 14-20 | Method competence, project ownership |
| Publications and preprints | 2-6 | Writing ability, output |
| Skills and tools | 2-4 | Day-one lab or coding readiness |
| Teaching, awards, service | 4-8 | Collegiality, trajectory |
View as table
| Label | Value (% of page space) |
|---|---|
| Research | 40 % of page space |
| Education | 20 % of page space |
| Publications | 12 % of page space |
| Skills | 10 % of page space |
| Teaching and awards | 10 % of page space |
| Contact | 8 % of page space |
Formatting rules panels never say out loud
Format signals competence before content is read. Dates in consistent right-aligned or fixed columns; one font; section headings identical in style; bullet fragments without full stops. Reverse chronology everywhere — panels look for the last two entries first, and a CV that buries the newest project under older ones reads as padding. File naming is part of the application: 'CV_Surname_Firstname.pdf' survives shared drives and committee printing; 'final_v3_new.pdf' signals chaos. Links (ORCID, GitHub, personal page) go in the header, live and clickable.
Honesty boundaries are bright lines. 'Manuscript in preparation' is a claim; 'manuscript submitted to Journal X on [date]' is evidence. A teaching entry without hours is decoration; 'demonstrated 12 lab sessions for second-year statistics, 2024-25' is evidence. And the skills section lists only tools you could be interviewed about tomorrow — every line of a PhD CV is a potential interview question, and you are writing the interviewer's list for them.
Start with the evidence the programme needsAn early-career academic CV should make your qualifications, research preparation and relevant skills easy to find. Use the programme's template and length limit where one is provided. Otherwise, choose a clear structure that gives the most relevant evidence enough space without listing every activity you have completed.
Put your name and professional contact details at the top. Include working links where they help the reader inspect relevant work. Add an ORCID or research profile only if you have one; do not create the impression of a publication record through an empty profile. Provide personal details such as nationality only where requested or relevant to the application process.
Education and research experience
List qualifications with the institution, subject, dates and accurate status. If a degree is ongoing, state the expected completion date rather than presenting the award as complete. Report grades in the original system unless the application provides a conversion method. A self-calculated UK classification should not be presented as an official award.
For a relevant project, explain the question and your contribution. Identify the methods you actually used, a result or decision you can discuss, and any shareable output. If the work was collaborative, distinguish your role from the team's overall achievement. A smaller task described precisely is more credible than a broad claim of leading research you did not lead.
An illustrative project entry
"[Project title] — [institution], [dates]. Investigated [specific question] using [method]. My contribution included [actual implementation, experiment or analysis]. Compared [baseline or alternative] under [documented conditions]. Produced [report, code or presentation where shareable]. The main limitation was [limitation you identified]."
Replace every placeholder with a fact. Include a numerical result only when you have measured it and can explain the conditions. A simulation experiment should be labelled simulation. Planned hardware tests should remain planned. The entry is a structure for reporting your own work, not a fictional candidate's achievement to copy.
Choose sections that fit your record
| Section | Useful information | A boundary to keep clear |
|---|---|---|
| Research and projects | Question, contribution, methods and evidence | Your work versus collaborators' work. |
| Publications and outputs | Accurate title, authorship, venue and status | Published versus accepted, submitted or in preparation. |
| Employment | Relevant responsibilities and decisions | A routine duty versus an independent research result. |
| Teaching | Role, audience and responsibilities | Formal teaching versus informal assistance. |
| Skills | Relevant techniques you can discuss or demonstrate | Practical experience versus introductory exposure. |
| Awards | Actual award, awarding body and date | Received awards versus pending applications. |
Omit empty sections unless a template asks for them. If you have no publications, use the space for projects and other preparation rather than inventing a manuscript. A technical report or dissertation can be listed accurately without implying peer review. Check confidentiality and permissions before sharing links or documents from employment.
Make the document easy to inspect
Use consistent dates, clear headings and readable typography. Keep formatting simple enough to survive a PDF export. Check that links work and that symbols, line breaks and page breaks have not hidden information. A compact document is useful only if it remains readable.
Tailor the order and detail to the application. A research project relevant to the advertised methods may deserve more space than an unrelated role. Keep the factual history accurate while changing emphasis. Do not delete a material qualification issue merely because it is difficult to explain; use the application's guidance for relevant context.
References and final checks
List referees only when the application or template asks for them, and obtain their agreement before supplying details. Follow the specified number and submission process. A name on the CV does not replace a reference submitted through the required system.
Read the final CV beside the form and statement. Qualification names, dates, grades and output statuses should agree. Ask whether every claim could be explained in an interview. Revise vague praise into a factual contribution, or remove it when it adds no evidence. Keep a copy of the submitted version so that later updates do not obscure what the programme received.
Audit each claim before sending the CV
Read every project bullet as though an interviewer asks what you personally did. Replace a team-level claim with your own contribution where necessary. If the project produced a result, describe it accurately and keep the conditions visible. A simulation result should not be presented as a hardware demonstration, and a classroom exercise should not be labelled an independent research appointment.
Publications need particularly careful status labels. Published, accepted, under review, submitted and in preparation are different categories. Use the category that is true at the time of submission. Do not add a journal name to an unsubmitted draft in a way that implies acceptance.
Check evidence and labels together
| CV item | What the reader needs |
|---|---|
| Research project | Question, your contribution, methods and a result or limitation. |
| Technical skill | A credible level of use, preferably supported by a project. |
| Collaborative work | Your role separated from the group's overall output. |
| Publication or report | Accurate title, authorship and current status. |
| Link | A working destination containing material you have permission to share. |
Use consistent dates and qualification names across the CV, forms and statement. If a document uses a local degree title, add a concise explanation where useful without inventing an official equivalence. Tailor the order of sections to the programme's needs while retaining an accurate history.
Is a two-page CV compulsory?
Follow the call's limit. A concise early-career CV can often fit within two pages, but the right length is the one that meets the instructions and presents relevant evidence clearly.
Use links as evidence, not decoration
Link to a project report, repository or presentation only when it helps explain a relevant contribution. Check that the destination opens without a private login if public access is intended, and identify any access restriction clearly. A broken or unexplained link can make useful work harder to assess. Keep confidential data and credentials out of shared material, and use a short description so the reader knows what the link contains before opening it.
Questions applicants often ask
How long should a PhD application CV be?
Two pages at master's-to-PhD stage. Research experience takes about 40 per cent of the space, education 20, publications and skills the rest. Three pages signals an inability to edit; one page hides research evidence.
What should an academic CV include with no publications?
Research experience in detail: each entry names the question, method, your specific role and the outcome — including talks, posters, preprints or 'manuscript in preparation'. Statuses must be honest; panels value a credible 'under review' entry and discount inflated ones.
Official sources and further readingRequirements and policies should be checked for your programme and application date.
Related guides
Official sources and further reading
Similar opportunities
University of Strathclyde
The Applications of Quantum Technologies CDT offers a funded doctoral training route in quantum research.
Auckland University of Technology (AUT)
AUT's 1 November 2026 doctoral scholarship round requires applicants to secure doctoral admission and submit a separate scholarship application. The published 2026 stipend rate is indicative.
University of Manchester
The BBSRC North West Doctoral Programme in Bioscience (NWDP) is a four-year doctoral training partnership between the University of Manchester, University of Liverpool, and BBSRC. Fully funded studentships starting October 2027, with applications open 2 November 2026 and deadline 4 December 2026. Limited number of full awards available to international applicants.

