PhD Interview Tips That Actually Help

PhD Admissions

Mar 12

By Ya'el Courtney, PhD | Stanford Postdoc, Harvard PhD in Neuroscience
Last updated: March 2026

PhD interview weekends are strange. You fly to a campus you may have never visited, shake hands with scientists whose papers you've read, try to sound smart and relaxed at the same time, and then go to a student party where you're told "this isn't part of the interview" while knowing it kind of is.

I did 40 one-on-one faculty interviews across seven programs during my interview season. I was terrified before the first one. By the end, I genuinely looked forward to them. I now coach students through interview prep every cycle, and I've seen the same anxieties come up over and over. Here's what I wish someone had told me before I started.

What PhD Interviews Actually Are

First, some context that might take the pressure off: getting the interview is the hard part. Depending on the program, somewhere between 7% and 25% of applicants get invited to interview. Once you're there, 30% to 75% of interviewees will receive an offer. The odds have shifted dramatically in your favor.

At most programs, if you've been invited, you are "good enough" on paper. The committee has already read your application and decided you belong there. The interviews are not a test to see if you were lying on your CV. They serve two purposes: confirming that you're a good fit for what the program offers, and just as importantly, giving you a chance to figure out whether the program is a good fit for what you need.

At Harvard's PhD Program in Neuroscience, we don't even call it interview weekend. We call it recruitment weekend. That framing tells you something about the power dynamic. They want you there.

What to Expect Logistically

Most biomedical PhD interviews span three to four days. Programs typically cover your travel (flights, hotel, sometimes ground transportation). Once on campus, you'll experience a mix of:

One-on-one faculty interviews, usually five to eight of them, lasting 25 to 40 minutes each. These are the core of the experience. Most take place in a PI's office. A current student will often walk you between appointments.

Informational sessions and panels where program directors explain curriculum, requirements, and resources. These can feel dry, but they're actually useful for comparing programs later.

Campus and city tours, sometimes led by current students, sometimes more formal. Pay attention to how the city feels, not just the buildings.

Social events like dinners, happy hours, and the inevitable student party. I'll talk more about these below, because they matter more than people think.

Meals with current students, which are often the most informative part of the whole weekend. Students are less guarded than faculty, and a casual lunch conversation can tell you more about a program's culture than any official presentation.

A note on travel costs: programs will cover your flights and hotel, but be aware that reimbursement can take several weeks, sometimes up to two months. You may need to book flights upfront and get reimbursed later, and hotels often put a hold on your credit card for incidentals. If you're interviewing at multiple programs, this can add up fast. It's worth asking the program administrator about their reimbursement timeline and any cost limits before you book, so you can budget accordingly. This is one of those logistics that nobody talks about but that can be a real source of stress, especially if money is tight.

Preparing for One-on-One Interviews

Before your visit, you'll likely receive an email from the program asking you to list 5 to 10 faculty you'd most like to meet. List more rather than fewer, because some PIs won't be available due to travel, teaching, or other conflicts. The program will do their best to match you, but you'll almost certainly interview with at least a few faculty who weren't on your list. Don't take that personally. It's a scheduling puzzle, not a signal about interest.

Here's how to use your interview list without over-preparing.

For every interviewer: Pull up their lab website. Know what organism they work with, the broad area of their research, and one or two things their lab has done recently. You do not need to read their papers cover to cover. You need enough context to have an intelligent conversation and ask a real question.

For PIs you'd want to work with: Go deeper. Read or at least skim a recent paper. Know what excites you about their work and be ready to articulate why. If their lab is doing something that connects to your prior research experience, be prepared to draw that line. These conversations are where genuine mutual interest starts, and PIs can tell when a student has actually engaged with their work versus skimmed an abstract five minutes ago.

One specific tip: check NIH RePORTER to see if a PI has active grants. If they do, the grant abstracts will give you a clear picture of what data they're currently collecting and where the lab is headed. This is often more current than the lab website.

For everyone else: A quick look at their lab page is plenty. Some of your interviewers will be faculty you'd never work with, and that's fine. The program assigns them because they're good at assessing applicants, not because you're expected to know their field.

If your schedule doesn't arrive until a day or two before the visit (this happens), don't panic. You'll be fine with a quick scan of lab websites. Nobody expects you to have memorized their publication history.

The Interview Itself

Here's how nearly all 40 of my interviews went: I walked in, sat down, the PI made small talk for a minute, and then asked some version of "So, tell me about your research."

This is your moment. Have a clear, practiced version of your research story, around three to five minutes, that covers who you worked with, what question you were asking, what you personally did, what you found, and why it matters. You do not need to cover every experience on your CV. Pick the one or two most significant and tell them well.

A few things I've learned from coaching dozens of students through this:

Be specific about your contributions. Don't say "the lab studies neural circuits in decision-making." Say "I developed a behavioral assay to test whether mice could discriminate between two similar odor mixtures, and I used calcium imaging to track how representations in piriform cortex changed with learning." Specificity signals that you actually did the work and understood it.

Know your results and what they mean. The follow-up question is almost always some version of "What did you find?" If your project is still in progress, that's completely fine. Say what the preliminary data look like and what you expect. If something didn't work, talk about what you learned from the failure and how you troubleshot it. PIs love hearing about troubleshooting because it demonstrates independence.

Be honest about what you don't know. If a PI asks you a question you can't answer (and they will), just say so. "I'm not sure, but my guess would be..." or "That's a great question, I'd want to look into X and Y to figure that out." Admitting uncertainty gracefully is a strength. Making something up is immediately obvious and a red flag.

Let your interviewer talk. This was the single best piece of advice I got before interview season. Your interviewers are scientists who love their work. Ask them about it. "What project in your lab are you most excited about right now?" or "Where do you see your field going in the next ten years?" are great questions. When a PI lights up talking about their research, the dynamic shifts from evaluation to conversation, and that's where connection happens.

Ask real questions at the end. When they say "Do you have any questions for me?", have some. Not performative questions designed to sound smart, but questions you actually want answered. What do they like about this program? What would they change? What do they look for in a good PhD student? These questions help you evaluate the program and they show genuine engagement.

Interviewing with Graduate Students

At some programs, you'll have formal interviews with current graduate students, not just casual interactions over meals. These can last 30 to 45 minutes, and they're more important than many applicants realize. Graduate students are often asked to provide feedback to the admissions committee afterward.

Treat these with the same preparation and respect as your faculty interviews. That said, they're also your best opportunity to get honest, ground-level information about what the program is actually like day to day.

Some of the most useful questions to ask grad students:

Why did you ultimately choose this program? What were you deciding between?
How often do you meet with your advisor? What's their mentorship style like in practice?
How collaborative are students in your cohort?
What program resources have you used the most?
What would you change about the program if you could?

For questions about more sensitive topics, like whether the stipend is livable, how the program handles DEI, or what a PI is really like to work with, it helps to take the pressure off. Add "if you're comfortable sharing" as a qualifier, or rephrase potentially negative questions into positive ones. "Would you recommend this lab to students?" lands very differently than "Should I avoid this lab?" Ask these kinds of questions in one-on-one settings rather than in front of a group, and remember that grad students may not be able or willing to speak freely about everything. That's information too.

If you know ahead of time which students you'll be meeting with, it's worth looking them up. If any of them work in a lab you're interested in, you can ask more specific questions about the day-to-day experience. If you're not on the schedule for a formal student interview, try to seek out students from labs you're considering during the informal parts of the weekend.

Questions to Ask Faculty

I touched on this above, but it's worth expanding. The questions you ask tell your interviewers as much about you as the answers you give. Here are some that I've found genuinely useful, both for making a good impression and for actually getting the information you need to make a decision:

About their lab:

What are the ongoing projects in your lab right now? Where do you see things heading in the next five to ten years?
How do students in your lab typically choose their thesis topics? Do they work on existing projects or develop their own?
How is authorship typically handled in your lab?
What's your mentorship style? How often do you meet one-on-one with students?
What conferences does your lab typically attend?

About the program:

What do you think makes this program unique compared to others you've been part of?
What qualities do you think allow someone to thrive here?
What kind of support does the program offer for students applying for external funding (NSF GRFP, F31, etc.)?
Are there opportunities to collaborate across departments or with other institutions?

A few things to avoid: don't ask questions that are easily answered on the program website (it makes you look like you didn't do your homework), and try not to ask about "strengths and weaknesses" directly, which can come across as pointed. "What's your favorite thing about this program?" gets you better information with less awkwardness.

Red Flags to Watch For

Interview weekends are as much about you evaluating the program as them evaluating you. Here are a few things worth paying attention to:

A PI who isn't clear about their funding situation or whether they'd actually have space for you in the lab. If you can't get a straight answer about this during the interview, that's a problem.
A PI who doesn't want to connect you with current or former students in their lab. Good mentors have nothing to hide.
Students who seem uncomfortable or evasive when you ask about program culture or their advisor. As I mentioned above, some topics are sensitive and students may not feel free to speak openly. But if multiple students seem hesitant, pay attention to that pattern.
A program where the students don't seem to know each other or spend time together outside of lab. Community matters, especially during the hard stretches of a PhD.

The Social Events

Let me be direct about this: the student parties and dinners are not formally part of the evaluation. But your behavior at these events is not invisible. If you behave very poorly (getting extremely drunk, being rude to other applicants, saying something inappropriate), it will get back to the admissions committee. I've seen it happen.

That said, the social events exist primarily for your benefit. This is your chance to talk to current students without faculty present and get honest answers about what the program is actually like. Use this time well. Ask the questions you'd feel awkward asking in a formal setting. Are students happy? Do they feel supported? What would they change? What's the worst part?

A couple of practical notes: there is almost always free alcohol at these events. It's completely fine to have a drink or two if that's your thing. Just know your limits. And if you don't drink, that's equally fine. Nobody is keeping track.

What to Wear

Business casual. That's it. This means clean, professional-looking clothing that you feel comfortable in, emphasis on comfortable, because you'll be on your feet and walking between buildings for hours. Strongly recommend against heels.

My entire interview wardrobe was thrifted. I couldn't afford to buy business casual clothing new, so I hit up secondhand shops and found a collection of vintage button-downs with slightly wild prints. I paired them with slacks or nice jeans and sneakers or loafers. It worked. Nobody cares if your blazer is from Goodwill. They care about your science.

One thing people forget: check the weather for wherever you're going. Interviews happen in January and February, and if you're flying from Texas to Boston, you need to plan for that. Layers are your friend.

Taking Care of Yourself During Interview Season

Interview days are long and draining. You'll be talking nonstop for hours, walking between buildings, and processing a huge amount of new information. A few small things that make a real difference:

Bring a water bottle. You will get dehydrated from talking all day, and there isn't always time to find water between interviews.
Bring snacks. The meals provided are usually generous, but the timing doesn't always line up with when you're actually hungry.
After each interview day, do something that helps you decompress. Watch a show, go for a walk, call a friend. Don't spend the entire evening reviewing notes and spiraling about whether you said the wrong thing in interview #4.

If you're doing multiple interview weekends across different cities (which most people are), the cumulative exhaustion is real. Give yourself grace and try not to schedule them back to back if you can avoid it.

The Mindset That Helped Me Most

Before my first interview, a mentor told me to walk in with the energy that they'd be lucky to have me. I took that to heart and I think it made a huge difference.

Here's the thing: the admissions committee already read your application. They already decided you were worth flying out and spending a whole weekend getting to know. You are not there to prove you deserve to be in the room. You're there to have real conversations with scientists about science, and to figure out if this is a place where you'd actually want to spend the next five to seven years of your life.

I've watched so many applicants go into these weekends radiating "please pick me" energy, and it hurts them. They don't ask the questions they actually want to know the answers to. They don't notice red flags because they're too busy performing. And they come across as less memorable, not more. The applicants who stand out are the ones who are genuinely curious, genuinely themselves, and clearly evaluating the program right back. That's the energy that makes an interviewer write "we don't want to lose this student to another program."

So yes, be prepared, be professional, be kind to everyone you meet. But don't shrink yourself. You earned this.

Quick Dos and Don'ts

Do:

Practice your research talk out loud before you go. With a real person, not just in your head.
Bring comfortable shoes. I cannot emphasize this enough.
Bring a notebook and pen for jotting thoughts between interviews.
Get enough sleep the night before your interviews if at all possible.
Be warm and genuine with other applicants. They may become your cohort.

Don't:

Speak negatively about any scientist, institution, or field. Science is a small world and people know each other.
Fabricate or exaggerate answers to technical questions. It's immediately obvious and far worse than saying "I don't know."
Be condescending to other applicants, current students, or staff. If you're the kind of colleague who punches down, people notice.
Stress about one awkward interview. I had at least one per school. It doesn't mean anything.

After the Interview

Send thank-you emails, but don't overthink them. A brief, specific note to one or two PIs you had particularly good conversations with is a nice touch. It doesn't need to be elaborate. Something like: "I really enjoyed our conversation about [specific thing]. Thank you for taking the time. It made me even more excited about the program." Don't send a form email to every single interviewer. Nobody wants that.

Write down your impressions immediately. Within 24 hours of leaving campus, jot down how you felt. What excited you? What concerned you? Which conversations stuck with you? Write down your unfiltered gut reaction to the program, both the good and the bad, and how it compares to other places you've visited. When you're comparing three or four programs weeks later, these notes are invaluable. Your memory of different recruitment weekends blurs together fast.

Be patient. Most programs get back to you within two weeks of interviews if you've received an offer. If you don't get an offer, you may not hear anything at all, which is frustrating but common. If you haven't heard by mid-March and want clarity, it's fine to email the program coordinator and ask about your status. And if you usually screen calls from unknown numbers, this is a good stretch to stop doing that. Some programs call with good news and don't leave it in a voicemail.

Preparing for PhD interviews and want structured, one-on-one practice? I offer mock interviews and interview coaching for biomedical PhD applicants. We'll work through your research talk, practice fielding tough questions, and make sure you walk in feeling ready.

PhD ApplicationsPhD InterviewsGraduate SchoolSTEMBiomedical PhD

Ya'el Courtney