How to Prepare for a PhD Interview Without Guessing the Format

An interview invitation gives you something much better than a list of guessed questions: it gives you the starting material for preparing for a real conversation. The invitation, the opportunity page, the course page, any attached instructions, and the documents you submitted are the evidence that matters.

This is important because PhD interviews are not one standard event. Some programmes interview, some do not. Some give detailed instructions before an interview; others send only practical arrangements. The format can also change between departments and application routes. The University of Oxford's graduate guidance tells applicants to use the relevant course page for interview method and format. Imperial College London's doctoral guidance likewise points applicants to the individual department's interview information. At UCL, the relevant academic department contacts an applicant if an interview or test is needed. These are useful examples of a simple rule: the course and department materials control your preparation, not a generic interview script.

Your aim is not to predict what a panel will ask or to copy someone else's experience. It is to understand the instructions you have, understand the work you applied for, and be able to speak honestly about your own evidence.

Start with the documents that control this interview

Put the following material in one folder or note before you start preparing:

• the interview invitation and any follow-up emails;
• the original opportunity or programme page;
• the project description, where there is one;
• the university or department page that describes the application route;
• any task, presentation, document, or technical instruction sent with the invitation;
• the exact application materials you submitted, including your CV, research proposal or statement, transcript, and writing sample if one was required.

Keep the original links as well as downloaded copies. A programme page can change while an application is being considered, and the invitation is the most direct record of what you have been asked to do. If two sources seem to disagree, do not try to decide which one is more likely to be right. Use the newest instruction sent by the responsible department, or ask that contact to clarify the difference.

The course page is useful even when it says very little about interviews. It can confirm the degree route, the advertised project, the named research area, the entry requirements, and the department contact. That gives you a way to separate facts from assumptions.

Turn the invitation into a practical preparation note

Read the invitation twice. The first reading is for the overall message. The second is for details that need an action. A short note with the following fields is enough:

Do not add fields that are not in the evidence. For example, do not write down a presumed dress code, panel size, assessment rule, or presentation requirement simply because another programme used one. A preparation note is strongest when it clearly separates “stated” from “not stated.”

The University of Cambridge Sensor CDT's admissions page is one example. It tells shortlisted applicants that the interview is online with academics from the CDT and that further information will come in the invitation. That information belongs to that programme only. It does not tell an applicant at another university what to expect. It does show why an invitation should be treated as a working document rather than a formality.

Re-read the opportunity and project description

After you understand the arrangements, return to the opportunity that led to the invitation. Do not try to become an expert in every part of a broad field in a few days. Focus on the exact work described in the official material.

Make a plain-language record of four things:

• the research problem or topic named in the opportunity;
• the methods, data, equipment, or skills the description mentions;
• the expected training, project setting, or research group where these are stated; and
• anything you did not understand when you applied and still need to clarify.

Then explain each point aloud in your own words. If you cannot describe a term in the project description, that is useful information. Read a reliable source connected to the field, return to the project text, and write down the remaining question rather than hiding it behind vague language.

This is also a good moment to check the scope of the opportunity. A project title, programme name, and research-group page may overlap, but they are not interchangeable. The project description tells you what was advertised. The group page can give context about current research. Neither page proves details that it does not state, such as a future project change or a particular supervision arrangement.

Know the application you already submitted

An interview can refer back to the material already in your application. Prepare from your own record, not from a new version of yourself.

Open your CV and mark the entries most relevant to the opportunity. For each entry, write a few factual prompts: what you did, the setting, the method or tool you used, the result or learning you can support, and the limit of your role. If a project was collaborative, say what you personally did. If a result was incomplete, explain it plainly. Clear limits are more useful than a polished claim that cannot be defended.

Do the same with a research proposal, personal statement, or writing sample if you submitted one. Read it as though you are checking it for accuracy. Be ready to explain why a question interested you, how you approached a past piece of work, and where you would need further training. Do not promise skills, data access, or a research outcome that your application and the official project materials do not support.

Your transcript can also be a useful prompt. You do not need to memorise every course. Instead, identify the courses, dissertation work, laboratory work, or methods training that genuinely connect to the opportunity. If a course title is unclear to a reader outside your university, prepare a simple explanation of what you learned and how it relates.

Use named people for context, not prediction

Sometimes an invitation names the people attending. Sometimes it does not. Both situations are normal.

When people are named, use their official university, department, or research-group pages to understand their current role and broad research area. This can help you read the project description in context and avoid asking a question that is already answered on the department page. It does not give you a reliable way to predict what an individual will ask or how they will respond.

Keep the research light and relevant. You do not need to summarise a long publication record or pretend to know every paper. A better goal is to understand where the advertised work sits: the research group, its current questions, and the methods or facilities it publicly describes. If the invitation does not name people, stay with the project, programme, and documents you have. Do not search for a supposed panel and treat the result as confirmed.

Prepare questions only where questions are invited or needed

Some programmes make room for applicant questions. Some invitations say nothing about this. The invitation and course guidance should shape what you do.

If questions are invited, choose one or two that resolve a real point you could not answer from the official pages. Good questions are narrow and tied to a source you have already read. They might be about a stated training route, a project element that needs clarification, or an application step described incompletely. They are not a request for the panel to predict a decision, explain private comparisons between applicants, or repeat information that is clearly published.

If an essential practical fact is missing before the interview, contact the office or person identified in the invitation or course page. Keep the message short. State what you have read, name the precise missing detail, and ask one answerable question. For example:

Hello [name], thank you for the interview invitation. I have read the interview instructions and the course page. Could you please confirm whether the requested [document or presentation] should be submitted before the interview, and if so, where it should be sent? Thank you.

This kind of message does not ask for private advice or special treatment. It asks the responsible office to clarify a published requirement. If no contact route is given, do not invent one from an unrelated department page.

Rehearse the evidence, not imagined answers

Preparation can include practice without becoming a performance based on guesswork. Use your preparation note and submitted materials to rehearse a clear explanation of:

• the research topic or opportunity you applied for;
• your most relevant prior work and the limits of your experience;
• the parts of your application that connect directly to the stated project or programme; and
• any work explicitly requested in the invitation.

Practice with a friend, mentor, or on your own only after choosing prompts grounded in those materials. Ask the person helping you to point out where an explanation is unclear, too broad, or unsupported by what you submitted. Do not ask them to create an imagined panel or guarantee that a certain question will be asked.

If the invitation requests a presentation, this becomes a separate piece of work. Follow its stated topic, time limit, slide rules, and submission instructions. The University of Oxford Department of Experimental Psychology publishes one programme-specific example in which shortlisted applicants are asked to prepare a short presentation, with details sent in the invitation. That is a reminder to follow the instructions for your own programme, not a reason to make slides when your invitation does not ask for them.

Check the practical details before the day

The final check should be boring. That is the point. It reduces avoidable uncertainty without turning it into a theory about the interview.

• Confirm the date, time zone, joining link or location, and any stated identification or check-in instructions.
• Test the platform only if the invitation requires an online meeting. Use the actual account, browser, equipment, and connection you expect to use.
• Keep the invitation, the official opportunity page, and your own submitted application easy to find. Do not bring or send extra material unless the instructions allow it.
• Complete any presentation, upload, or document step by the stated route and deadline. Save confirmation where the system provides it.
• If you need an adjustment or an essential clarification, use the official contact route with enough time for a response.

Once this list is complete, stop adding imagined tasks. The point is to arrive ready for the interview described by the university, not to spend the final hours preparing for several possible interviews at once.

Keep the boundary with the wider application process clear

This guide starts after a real interview invitation arrives. It does not replace the work of choosing opportunities, checking funding and eligibility, preparing required documents, or managing the whole application timeline. Those decisions belong in the wider PhD application workflow.

For the opportunity itself, return to the verification guide if you need to check the page that controls funding, eligibility, or an application route. For the earlier decision about whether to contact a named academic before applying, see when and how to contact a potential PhD supervisor.

Invitation-based checklist

Before the interview, you should be able to say yes to each of these:

• I have saved the invitation and any later official instructions.
• I know the stated date, time zone, location or platform, and any deadline for a task.
• I have re-read the opportunity or programme material that relates to my application.
• I have reviewed the exact CV, statement, proposal, and other material I submitted.
• I know which preparation is explicitly required and which details are still unknown.
• Any question I plan to ask is permitted or addresses a genuine factual gap.
• I have used the responsible department contact if an essential instruction is unclear.

Sources

• University of Oxford: graduate interviews explains that the relevant course page indicates whether interviews are used and, where applicable, the method and format.
• Imperial College London: doctoral interview guidance notes that individual departments publish their own interview information.
• UCL: waiting for a decision explains that the relevant academic department contacts applicants with interview or test details when needed.
• University of Cambridge Sensor CDT: how to apply gives a programme-specific example in which shortlisted applicants receive further interview information with their invitation.
• University of Oxford Department of Experimental Psychology: graduate admissions procedures gives a programme-specific example of a requested presentation and interview arrangements.

Related AcademicWings pages

• Application workflow
• The International Applicant's PhD Application Workflow
• How to Verify a PhD Opportunity Before You Apply

Browse practical guides