PhD Interview Preparation: Research Questions and Clear Answers

Prepare to discuss your work, the proposed project and the decisions behind your methods. Practising clear answers is more useful than memorising impressive phrases or pretending to know every answer.

Scoring the sixteen questions by what they test

Every PhD interview question maps to one of four competencies: research understanding, method capability, project ownership and fit. Sort the sixteen questions in this guide by that mapping and preparation becomes targeted instead of exhaustive. 'Tell us about your dissertation' and 'what is the main contribution of your project?' test research understanding; 'how would you analyse X?' tests method; 'what would you do if your results contradict your hypothesis?' tests research behaviour; 'why this group?' tests fit. Answer the competency the question is actually buying, and the same evidence serves multiple questions.

The answer formats that score: STAR for experience questions (situation, task, action, result in 90 seconds), thesis-antithesis for discussion questions (state a position, name its strongest criticism, resolve), and the two-part unknown ('I do not know, and here is how I would find out') for genuine gaps. Panels consistently prefer a candidate who reasons visibly over one who recites — the interview is a live test of how you will think at the bench or the terminal, and rehearsed-perfect answers read as risk.

What is a PhD interview designed to assess?

A research interview often explores your understanding of the proposed project, preparation, methodological judgement, willingness to learn and ability to discuss uncertainty. Formats vary: an advertised funded project, structured doctoral programme and self-proposed doctorate may use different panels and tasks. The questions below are realistic practice examples, not a documented list asked by every professor.

The logistics questions and the questions you ask

Panels always end with 'do you have questions for us?', and the question you ask is itself scored. Strong questions are specific and operational: 'how does the group's funding run after the current grant ends?', 'what does supervision look like week to week — one-to-ones, lab meetings, writing groups?', 'where did the last two doctoral students from this group publish, and who did they work with?'. These signal that you are evaluating them as seriously as they are evaluating you — which is true and welcome. Weak questions ask about information on the website, and no question at all reads as indifference.

Handle the logistics block cleanly when it comes: start date flexibility, visa timeline, relocation. Answer in facts, not enthusiasm — panels use the logistics block to check that accepting you would actually work. If a constraint exists (a visa processing time, a notice period), say it plainly and offer the workaround. Surprises discovered after an offer cost everyone; constraints disclosed in the interview are just planning data.

Sixteen common PhD interview questions — with answer frameworks

1. Tell us about your research background.

A useful answer approach: Summarise one relevant project: research question, your exact contribution, method, result and a limitation.

2. Why do you want to do a PhD?

A useful answer approach: Describe a real question you want to investigate and why sustained research is the right next step.

3. Why this project or supervisor?

A useful answer approach: Connect one verified part of the group’s research to your experience without claiming an automatic fit.

4. What is the central research question?

A useful answer approach: State a focused question in two sentences and distinguish hypotheses from established facts.

5. What does the literature already tell us?

A useful answer approach: Discuss two or three real papers, agreement or disagreement and what remains uncertain.

6. Which methods would you choose and why?

A useful answer approach: Compare a preferred method with at least one plausible alternative.

7. How would you evaluate success?

A useful answer approach: Name relevant measures, baselines, controls and uncertainty estimates.

8. What could make your proposal fail?

A useful answer approach: Describe a likely technical or practical risk and a sensible fallback.

9. What would a negative result mean?

A useful answer approach: Explain what the result would rule out or teach, not how to hide it.

10. Describe a challenge in a previous project.

A useful answer approach: Use a real example of troubleshooting or changing course, including what you learned.

11. What are your current technical limitations?

A useful answer approach: Admit a skill gap and give a concrete plan to address it.

12. How would you manage your first year?

A useful answer approach: Propose a literature map, pilot study, training and realistic milestones.

13. How will you deal with research ethics?

A useful answer approach: Mention approvals, consent, data security, safety or reproducibility where relevant.

14. How do you work with collaborators?

A useful answer approach: Give an example of responsibilities and communication; avoid generic teamwork clichés.

15. Why should we fund this project?

A useful answer approach: Address the actual award’s criteria and the proposed study’s feasible value.

16. Do you have questions for us?

A useful answer approach: Ask about supervision arrangements, equipment access, training, expectations and funding scope.

Example answer: discussing a project setback

Subject: Practice response — adapt only to your actual experience

In [my real project], I initially expected [hypothesis]. The first results showed [observed problem], so I checked [data or assumption] and compared [alternative]. I changed [specific step] after [evidence]. The outcome was [actual outcome], but the main lesson was to test [important assumption] earlier. I would bring that habit to a PhD project.

A realistic preparation plan

1. Re-read your CV, application, proposal and relevant project advert.
2. Review a few relevant papers and prepare to discuss one limitation for each.
3. Prepare a two-minute explanation of your most relevant project.
4. Practise a short methods comparison and a negative-results question.
5. Test any presentation files or video-call setup in advance.
6. Prepare two thoughtful questions about supervision, facilities and funding.

If you do not know the answer

Say what you know, make your assumptions explicit and describe how you would investigate the unknown. Inventing an answer usually weakens an otherwise thoughtful research discussion.

Questions you can ask the panel

• How is supervision organised between the main and secondary supervisors?
• What milestones would a successful first year usually include?
• Are the proposed datasets, equipment or field sites accessible?
• How does the programme support research training and conference participation?
• What does the funding package cover for international applicants?

Practise a research explanation, not a script

Prepare a two-minute explanation of one project: the question, your contribution, the method, the result and a limitation. Then practise follow-up questions. Why did you choose that method? What would you change with more time? Which result surprised you? If an interviewer asks about a technique you have not used, distinguish what you understand from what you would need to learn. Bring questions about supervision, training and the project’s early milestones. An interview is also a chance to understand the working relationship you would be entering.

Prepare the decisions behind your project

An interviewer may ask why you chose a method, how you checked a result or what you would do differently. Practise those decisions rather than memorising a perfect description. Use one completed piece of work and explain the problem, your contribution, the evidence and a limitation in plain language.

If a technical question goes beyond your experience, state the boundary and reason from what you do know. You can ask a clarifying question before answering. Distinguish an informed possibility from a result you have demonstrated. A confident invented answer is harder to defend than a careful explanation of how you would investigate the issue.

Match preparation to the interview format

Read the invitation for tasks, timing and permitted materials. If a presentation is requested, practise to the actual time limit and prepare for questions that interrupt the planned sequence. Test the connection and screen-sharing arrangement for an online interview without assuming the panel will allow extra time for setup.

What should I ask the panel?

Ask questions that affect the work: supervision, first-year expectations, equipment or data access, training and project flexibility. Use the funding office for unresolved award details where appropriate, and keep academic fit separate from a formal funding decision.

Questions applicants often ask

What are the most common PhD interview questions?

Sixteen questions cover most panels: your dissertation or project, its contribution, method choices, a failure you handled, why this group, how you would analyse a given problem, reading you have done, and practical logistics. Each maps to research understanding, method, ownership or fit.

How should I answer a question I cannot answer?

With the two-part format: state clearly that you do not know, then describe how you would find out — the source you would read, the person you would ask, the small experiment you would run. Panels score visible reasoning far above bluffing.

Official sources and further reading

Requirements and policies should be checked for your programme and application date.

• Oxford: graduate application requirements
• Cambridge: postgraduate entry requirements

Related guides

• Finding a DAAD Scholarship: Choose the Right Scheme for Your Degree
• How to Explain an Academic Gap in a University Application
• After a PhD Rejection: Review Your Application and Plan Your Next Steps