A PhD interview presentation should answer the task in your invitation, show how you think about research and stay within the time allowed. A useful structure is: research question, approach, evidence or proposed work, limitations, and fit with the project. Adapt that structure to the brief rather than assuming every interview needs the same slides.
Being asked to give a short talk can feel more daunting than being asked questions. Slides make your preparation visible, and a five-minute limit can make a substantial project feel impossible to explain. The solution is to choose one clear story and give each slide a job.
Below are suggested five- and ten-minute presentation plans, an illustrative project example and a rehearsal checklist. These are preparation tools, not university requirements.
Read the presentation brief before building slides
Interview formats vary. The University of Manchester’s postgraduate interview guidance describes several formats and encourages applicants to understand prospective supervisors’ research and discuss their own research experience. Your invitation remains the source for the presentation task.
Make a small brief sheet with the topic, time limit, audience, file format, submission deadline and whether questions are included in the allotted time. If the invitation is unclear, ask the contact named in it. Confirming the task is a sensible part of preparation.
| Invitation asks for… | Main presentation focus |
|---|---|
| A previous research project | Your question, contribution, approach, findings and what you learned. |
| A proposed PhD project | The problem, research question, possible approach, feasibility and uncertainties. |
| A selected paper | The paper’s argument or evidence, a fair critique and its relevance to the advertised project. |
| Research interests or fit | A coherent direction, evidence of preparation and specific connections to the programme. |
Do not use a proposal presentation to avoid explaining a past project when the panel requested one. Equally, an extensive biography may not help when the task is to analyse a paper. Put the brief beside your outline and check each slide against it.
A five-minute PhD interview presentation structure
For a five-minute talk, try five content slides, with your name and title included on the first. This is a suggested starting point. A complex figure might need more time than two short slides, so rehearse the actual talk before deciding the final count.
| Slide | Purpose | Suggested speaking time |
|---|---|---|
| 1. Question and context | State what you studied or propose to study, and why the question matters. | 40 seconds |
| 2. Approach | Explain the design and the main reason for choosing it. | 60 seconds |
| 3. Evidence or planned analysis | Show one main finding, or explain how proposed work would answer the question. | 90 seconds |
| 4. Limitations and learning | Identify a meaningful uncertainty and how you addressed or would address it. | 60 seconds |
| 5. Fit and next step | Connect the work to the opportunity and finish with the research direction. | 35 seconds |
This allocates four minutes and 45 seconds, leaving a small buffer within a five-minute slot. It assumes questions happen afterwards. If questions are included, agree a shorter speaking target with the organiser.
The evidence slide deserves the most room. For completed work, show what you found and explain what supports it. For a proposal, show the comparison, material or analysis you would use. A planned result should never be presented as an observed result.
A ten-minute presentation structure
A longer talk lets you explain choices and alternatives, rather than simply adding more background. The following seven-slide plan leaves a 30-second buffer. Change the balance to suit the task and discipline.
| Slide | What it adds | Suggested time |
|---|---|---|
| 1. Research problem | The central question and why it is worth investigating. | 45 seconds |
| 2. Relevant context | The specific gap or debate needed to understand the project. | 75 seconds |
| 3. Research question and scope | What the project answers and what it leaves outside scope. | 60 seconds |
| 4. Design and your contribution | Methods, material and your own role. | 120 seconds |
| 5. Findings or proposed analysis | The main evidence or the route to answering the question. | 120 seconds |
| 6. Limitations and next study | What remains uncertain and a realistic next step. | 90 seconds |
| 7. Fit and closing message | Why this opportunity suits the research direction. | 60 seconds |
Avoid using the extra time to list every paper you have read. Select the context that explains your choices. If the audience needs a specialised term, define it before you use it to interpret a result.
Worked example: presenting a previous project
Illustrative example only: imagine an applicant completed a small project comparing how two versions of a research script used energy. This outline demonstrates structure. It does not describe an actual experiment or verified findings.
| Slide | Possible heading | What the applicant could explain |
|---|---|---|
| 1 | Can a simpler data-processing pipeline reduce energy use? | Define the task and why the question matters. State that this was a bounded student project. |
| 2 | Compare the same workload under recorded conditions | Explain the hardware, workload, measurement approach and repeated runs. Identify what the applicant implemented personally. |
| 3 | Show the observed measurements | Use the applicant’s actual data, labelled with units and variation. Explain runtime alongside energy rather than equating them. |
| 4 | What this comparison cannot establish | Discuss measurement uncertainty, the chosen workload and limits to generalising across machines. |
| 5 | The next question I want to investigate | Suggest a justified next comparison and connect it to a relevant research group. |
The important feature is ownership. Instead of saying “we tested several scripts,” the applicant could explain which part they designed, what they checked and where another person contributed. Accurate attribution makes it easier for a panel to understand their experience.
If a trial produced an unexpected or inconclusive result, explain that honestly. You can still show research judgment by discussing the checks you performed, what remains uncertain and how you would improve the design.
How to adapt the talk for a proposed PhD
For proposed research, replace a findings section with the route to an answer. Explain the material or participants you need, the comparison you would make, the analysis you are considering and the evidence that would change your view.
Keep the project bounded. “Study sustainable computing” is a broad interest. A proposal needs a question that can guide decisions about methods and scope. The guide to narrowing a research question can help you move from a theme to an investigable problem.
Show that you have considered feasibility without pretending every detail is settled. If access to data is uncertain, say how you would check it or identify a plausible alternative. Explain why the alternative still addresses the research question.
For more detail on the written version, see how to write a research proposal. Your interview slides should select the core argument from the proposal, rather than paste its paragraphs.
Design slides that support the explanation
Give each slide a title that tells the audience what to look for. “Comparison under the same workload” offers more direction than “Methodology.” A finding-led title can work for completed research, provided it accurately reflects the evidence.
Use one readable figure when it explains the point better than a paragraph. Label axes, units, groups and abbreviations. Add a short source citation for borrowed figures or claims, and follow any permission requirements for the material.
Check the slides at the size they will be seen. A table that looks readable on your laptop may be too dense when shared in a video call. Reduce detail, enlarge labels or move supporting information to a backup slide.
Backup slides can hold additional methods, references or sensitivity checks for questions. They should not be essential to the main story. Keep the talk understandable even if no one asks to see them.
Rehearse the explanation, not just the timing
Do one rehearsal for structure: can a listener identify the question, understand your main choice and explain the takeaway? Ask them where they lost the thread. That feedback is more useful than a general “looks good.”
Do a second rehearsal with a timer and the actual slides. If you run over, remove a secondary point before trying to speak faster. Write a short transition between slides so you do not lose time deciding what comes next.
Do a third rehearsal under the likely conditions. For an online interview, practise sharing the correct window and keeping notes accessible. For an in-person talk, check how you will advance slides and whether the supplied computer supports the file.
Save an editable version and a PDF backup, while following the requested submission format. Use a clear filename and send it by the stated deadline. Keep a local copy available in case your connection fails.
Prepare for questions about your choices
For each main slide, write down one question a panel could reasonably ask. Prepare an answer that explains the choice, the evidence behind it and its limitation. You do not need to memorise a script.
Useful rehearsal questions include: Why this method? What alternative did you consider? What was your own contribution? Which result is most uncertain? What would you do with more time? How does this connect to our project?
If you do not know an answer, identify what you would need to check. You can reason from what you do know, while making the boundary clear. Inventing a confident explanation creates a harder problem than acknowledging an uncertainty.
The broader PhD interview questions guide can help with the discussion after the talk.
Show fit with the supervisor or programme
Manchester’s research interview tips emphasise knowledge of the research area and prospective supervisor’s work. They also frame the interview as a chance to assess whether the supervisor is a good fit for you.
Choose a specific connection you can explain: a method the group uses, a question their work raises or an advertised project objective. Avoid listing publications without discussing them. One relevant connection is easier to defend than several superficial ones.
For preparation before applying, emailing a potential PhD supervisor covers how to introduce your interests clearly. At interview, bring questions about supervision, project development or access to the resources your work would need.
Final presentation checklist
Check that you have answered the requested task, stated the research question early, distinguished completed work from plans, credited contributions, made figures readable and finished within the limit. Test your file, citations and sharing setup.
Do all PhD interviews require presentations? No. The invitation tells you what is required. Prepare a talk only when requested, and ask the organiser about unclear instructions.
How many slides should I use? Enough to support your explanation within the time limit. The five- and seven-slide plans here are suggested outlines. Your rehearsal is the better guide.
Can I discuss a project outside the advertised PhD topic? If the brief allows it, explain the relevant research skills and the connection to the opportunity. Do not claim a subject match that the project does not have.
A strong preparation goal is simple: the panel should understand the question, your contribution and the reasoning behind your choices. Build the slides around those points and practise explaining them clearly.
Featured image: Kari Shea on Unsplash.