PhD Interview Questions and Answers (2026)

Getting invited to a PhD interview means you've already cleared the hardest filter, your application and your outreach worked. What most question lists get wrong is treating every interview the same, listing 15-30 generic questions with no sense of which ones actually decide the outcome, or how the format changes what a strong answer looks like. Below is what actually gets asked, organized by what each question is really testing, plus the format details that change how you should prepare.

What a PhD interview actually looks like

Format varies more than most guides admit. A single interview with a professor you've already been emailing typically runs 30-45 minutes, one-on-one, often more conversational than formal. Cohort-based programs, common in biomedical and some STEM PhDs, run differently: candidates are flown in for two to four days and sit through five to eight separate one-on-one meetings with different faculty, each 25-40 minutes, alongside group information sessions, a research presentation in some programs, and social events with current students. Panel interviews, two to five faculty members in one room or call at once, sit somewhere in between and typically run 30-60 minutes. Knowing which format you're walking into changes how much you need to condense your answers and how many different people you need to convince, not just one. Some applicants reach this stage through an earlier, more informal step first, a professor proposing a quick call after your original cold email, before any formal interview is scheduled. See our guide on preparing for that earlier phone call if that's the stage you're at right now.

"Tell me about yourself" or "walk me through your background"

Almost every interview opens with some version of this, and it's a real opportunity, not small talk. A strong answer moves through three parts in order: your academic path (briefly, not your full transcript history), the research experience that led you here, and why a PhD, and specifically this lab or program, is the right next step. Two to three minutes is the right length. Longer starts to ramble, shorter skips the connective thread the panel actually wants to hear, how your background adds up to a coherent reason you're sitting in that chair.

"Why do you want to work with me / this lab specifically?"

This question is checking whether you've read their actual work or are giving an answer that could apply to any lab in the field. A generic answer, "I'm interested in your research area," is the single most common way candidates weaken an otherwise strong interview. A specific answer names a particular paper, project, or method the lab is known for and connects it directly to something in your own experience or proposed direction. If you built your outreach the right way in the first place, grounding your original email in a real recent paper rather than a generic interest statement, this question is often just a restatement of something you've already thought through carefully. See how to read a professor's paper well enough to reference it specifically for the same skill applied at interview stage.

Strengths and weaknesses questions

For strengths, pick something directly relevant to research, not a generic trait, and back it with one concrete example rather than a list of adjectives. For weaknesses, the honest answer matters more than a strategically disguised strength. Pick something real that isn't fatal to the specific project you're discussing, and pair it with what you're actively doing about it. "I'm still building confidence with [specific technical skill], and I've been working through [specific way you're addressing it]" reads far better than a rehearsed non-answer, because it shows self-awareness, which is exactly what a multi-year supervision relationship depends on.

Questions about your research experience and a challenge you faced

Expect to walk through a specific project in detail, not summarize it in one sentence. The panel wants to see how you think when something didn't go as planned: a failed experiment, a dataset that didn't behave, a method that had to change mid-project. Structure the answer around what happened, what you tried, and what you learned, since the actual research process, including the parts that didn't work, is what a PhD is made of far more than a clean success story.

Technical and field-specific questions

These vary enormously by discipline, but the underlying test is consistent: can you reason out loud under some pressure, not whether you have a memorized answer for everything. If you genuinely don't know something, say so and think through it anyway rather than guessing with false confidence or going quiet. A panel that watches you reason carefully through an unfamiliar question learns more about how you'll handle the actual PhD than a rehearsed correct answer would tell them.

If the program includes a research presentation

Some programs, particularly multi-day cohort interviews in biomedical and lab sciences, ask candidates to give a short presentation on their prior research or a proposed direction, usually 10-15 minutes, followed by questions from the room. Treat this as a different skill from the one-on-one conversation. Build the talk around one clear narrative arc, the problem, what you did, what you found, rather than trying to cram in every project you've touched. The questions that follow a presentation tend to probe the parts you rushed through or glossed over, so if a slide compresses something complicated into one bullet point, be ready to unpack it out loud. Practicing the talk in front of at least one other person beats refining slides alone, since timing and pacing only become obvious once you say the words out loud under a clock.

"Where do you see this research going / what's your five-year plan?"

This isn't asking for a fixed roadmap, since a first-year PhD student genuinely shouldn't have one. It's checking whether you understand the field has open problems and can speak to them with some specificity, rather than a vague statement about wanting to "make an impact." A reasonable answer names one or two directions you find genuinely interesting within the lab's broader area, while being honest that the specific project will likely shift once you're actually working with your advisor.

Questions you should ask them

Most interviews leave time for your questions at the end, and this part is evaluated too, a candidate with no questions reads as under-prepared or not genuinely deciding among options. Worth having ready:

• How often do you typically meet with students, and in what format?
• What have recent students from your lab gone on to do after finishing?
• What does funding look like for a student in my position, duration, whether summer or travel funding is separate, and what happens if a project runs longer than expected?
• What's the culture like among students in the lab or cohort day to day?
• Are there structured opportunities to publish, present, or teach during the program?

Three to five well-chosen questions land better than a long list read off a notes app. Pick the ones that would genuinely change your decision, not ones that just fill the silence. See our full guide on how to actually raise the funding question without it feeling transactional, and our breakdown of interview red flags worth watching for while you're gathering answers, not just asking questions.

What happens between the formal interviews

In multi-day cohort interviews, the scheduled meetings aren't the only part being evaluated, even when nobody says so directly. Dinners, campus tours, and informal time with current students are genuinely useful for you to gauge lab culture and honest opinions, but they're also, in practice, part of how a program forms its overall impression of a candidate. That doesn't mean performing for two days straight, exhausting and usually obvious when someone does it, it means treating a casual dinner conversation with the same basic professionalism as the interview itself, since current students and faculty do sometimes compare notes afterward.

Preparing without over-rehearsing

Review your own materials the day before, your personal statement, your proposed research direction, and the specific papers from the lab that motivated your application, so nothing you wrote can catch you off guard. Say your answers out loud at least once rather than only rehearsing them mentally, since the gap between a polished mental answer and an actual spoken one is often larger than people expect. What you're aiming for is fluency on the ideas, not a memorized script, since a question that deviates even slightly from a rigid rehearsed answer tends to expose the rehearsal rather than cover for it.

What a relaxed, conversational tone usually means

If an interview feels more like a genuine conversation than a formal interrogation, that's typically a good sign, not a trap. Panels and advisors who are already leaning positive tend to use the time checking fit and answering your questions rather than running a rigid elimination checklist. Don't mistake a friendly tone for the interview not mattering, prepare exactly the same, but it's a useful signal not to read hostility into a relaxed room.

Getting to the interview stage in the first place

None of this matters until you're in the room, and the step before it, getting a professor to actually want to talk with you, depends on the quality of your first outreach, not just your CV. GradScoutFunding finds professors filtered by field and country, confirms they're actively publishing, and drafts a personalized first email grounded in a real recent paper for you to review and send, so the outreach that leads to an interview starts from something genuine instead of a generic template. Once a reply turns into a real conversation, the interview prep tool is there for that next stage. Your first 2 credits are free, no card required.

Common questions