Graduate School Interview Questions: How to Prepare

A graduate school interview can make an already consequential decision feel suddenly personal. You may be speaking with a faculty member whose work you have read, a panel of admissions staff, or current students who know what the department is like on an ordinary Tuesday. The pressure is real, but the task is more manageable than it first appears. You are not being asked to predict your entire academic future. You are being asked to show how your preparation, interests, and next questions connect to a particular program.

Interview formats vary widely. MIT notes that some programs use interviews after narrowing the applicant pool, while others do not use them at all. When you receive an invitation, start with the program’s instructions. Confirm who you will meet, whether the conversation is virtual or in person, how long it will last, and whether a visit includes sessions with current students. Then prepare for the conversation you are actually having, not a generic performance of being “impressive.”

Know what the conversation is trying to clarify

At its best, an interview helps both sides test fit. A program may want to understand why you are pursuing graduate study, what you have learned from previous work, and whether your interests connect to the people and resources available. You need to learn the corresponding practical details: how mentorship works, what research opportunities are open, what funding is dependable, and whether the environment suits the life you will be living while you study.

That is why preparation should start with your original reasons for applying. Revisit the program notes you made when using the framework for choosing a graduate program. What drew you to this department? Which faculty work, methods, courses, centers, or partnerships mattered? Where are you still uncertain? The answer to those questions becomes the backbone of a focused conversation.

MIT’s list of common prompts includes why you want a graduate degree, why the program is a good fit, and a project you discussed in your application. Those questions are not traps. They are invitations to connect the evidence in your application to the next step you hope to take. Be specific enough to show that you have done the reading, but do not force certainty you do not have. A thoughtful applicant can say what they are still exploring and explain why this program is a good place to explore it.

Prepare a two-minute account of your work

Many applicants can describe what a project was about but struggle to explain what they personally did, what changed because of the work, and what they learned when something did not go as planned. That is the gap to close before an interview. Stanford recommends preparing a brief oral summary of past work that covers the research question, your approach, your own contribution, and what you completed or learned.

Use a simple structure: context, question, action, result, reflection. Begin with the problem the project addressed. Name the question or objective in ordinary language. Explain your role without inflating it. Then describe the outcome and the next question it left you with. A lab assistant, analyst, teacher, community organizer, or working professional can all use this structure. The point is not to turn every experience into a breakthrough. It is to show careful thinking, ownership, and the ability to learn from real work.

Research notes, index cards, and a notebook arranged for practicing an explanation of past work

Practice aloud at least twice. First, listen for jargon that would confuse someone outside your exact specialty. Then ask a trusted person to interrupt with the questions an interviewer might ask: Why did you choose that method? What was difficult? What would you do differently? What did the project teach you about the work you want to do next? A clear answer does not need to be polished into a speech. It needs a beginning, a middle, and an honest ending.

Prepare for the questions behind the questions

Some prompts look broad because they are designed to reveal how you think. “Tell me about yourself” is not a request to recite a résumé. Give a brief account of the experiences that led you toward this field and the question you want graduate study to help you pursue. “Why this program?” calls for more than a ranking or a familiar name. Connect your preparation to a specific research community, training opportunity, or professional direction.

Oregon State’s interview guidance groups common questions around personal strengths, academic experience, teamwork, field knowledge, and future goals. Prepare examples in each group. You might explain a research project, a difficult course or transition, a time you worked through a disagreement, or how a job experience changed the kind of problem you want to study. Choose examples that are true and concrete. If you need to discuss a weak grade or a gap in your record, name the context briefly, explain what you did next, and keep the focus on the evidence of your current preparation.

It is also useful to prepare a measured answer for uncertainty. You may not know exactly which dissertation question you will pursue, especially in a broad or interdisciplinary program. You can still explain the themes, methods, or problems that draw you in, the work you hope to build on, and the questions you want to test once you have stronger training. Intellectual direction is more convincing than a fixed script that cannot respond to what the program actually offers.

Ask questions that help you make a decision

You are allowed to use an interview to learn. Generic questions that a department website already answers will not tell you much, but a short list of well-researched questions can make the conversation more useful for everyone. Stanford suggests preparing specific questions for each faculty conversation and researching the areas that matter to you before you arrive.

Choose questions based on the gaps in your own comparison. For a potential advisor, ask how students move from early ideas to viable projects, how often they meet, how feedback is usually given, and what collaboration looks like in the group. For program staff, ask how funding decisions are made, whether support is guaranteed and for how long, and what graduate students are expected to do in return. For current students, ask what their weeks look like, where expectations are clear or unclear, and what support they rely on when a project stalls.

Notebook, map, and research papers arranged for planning questions about a graduate program

Duke’s graduate-school question guide is particularly useful for funding conversations: ask what kinds of awards exist, whether tuition and fees are covered, how long an award lasts, what work is expected, and whether support is guaranteed. Those details matter as much as the headline stipend. Add them to the same comparison notes you use for program fit and application dates, rather than trying to remember them after several visits. The application deadline timeline can help you keep those funding dates and questions visible from the start.

Use the visit to notice the daily environment

An interview weekend or campus visit offers information that a program brochure cannot. Notice how people talk about students who are not in the room. Listen for whether current students can describe their advising process, funding, workload, and milestones clearly. Pay attention to the practical setting too: housing, transportation, healthcare, family considerations, community, and the rhythm of the work.

Do not treat a warm conversation with one person as proof that every part of the program will work well. Look for patterns across faculty, staff, and students. Equally, do not dismiss a program because one interaction feels awkward. Interviews are social situations, and not every conversation will be smooth. What matters is whether the accumulated evidence supports the kind of work and life you are considering.

After each interview, take ten minutes to record what you learned. Separate confirmed facts from impressions and unanswered questions. Stanford recommends making a simple list of the people you met, your observations, and the pros and cons. That practice turns a blur of conversations into useful comparison material when offers and deadlines arrive later.

Practice without trying to sound rehearsed

Practice is for clarity, not imitation. Read your statement, CV or résumé, writing sample, and any research abstract you submitted. Make sure the story you tell aloud agrees with the evidence you sent. Then do a mock interview with someone who will ask follow-up questions. If the interview is virtual, test the link, sound, camera angle, lighting, and a quiet place to take the call well before the scheduled time.

Bring a short page of notes, not a script. Include names, two or three research details, your prepared questions, and the key points you want to remember. Listen closely rather than waiting for your next line. If you need a moment to think, take it. A calm pause is better than a hurried answer that does not reflect what you mean.

The same principle applies after the interview. Thank people for their time, follow up on any material you promised, and update your notes while the conversation is fresh. Do not overread the timing or tone of a reply. Keep moving through the rest of your application plan, and use the information you gained to decide which programs are worth the commitment they require.

Make a simple interview plan before each conversation

Preparation becomes easier when you use the same one-page plan for every interview. At the top, write the program, the people you expect to meet, and the purpose of the conversation. Under that, list three pieces of evidence that connect your past work to the program. They might be a research project, a professional experience, a course, a method you want to learn, or a question you have been developing. Keep the list short enough that you can return to it naturally during the conversation.

Next, write your questions in order of importance. Start with the information you cannot learn elsewhere, such as how advising works in practice or whether a funding package is renewable. Place a few flexible questions at the end, in case the conversation has already answered the first ones. This protects you from leaving with a page of notes but no answer to the question that most affects your decision.

Finally, decide what you will record immediately afterward: a few factual notes, one impression you want to test against other conversations, and any follow-up you owe. The goal is not to score people or reduce a complex program to a checklist. It is to preserve enough evidence to compare opportunities fairly when the excitement of an interview has passed.

Prepare for the whole decision

Keep fit, funding, and next steps in one place.

Use the guide to turn program research, interview notes, deadlines, and funding questions into a clearer graduate-school decision.

Get the guide Explore application help →

Frequently asked questions

What questions are asked in a graduate school interview?+

Questions commonly cover your academic preparation, research or professional experience, reasons for pursuing graduate study, interest in the specific program, and future direction. Research-focused interviews often also ask you to explain a past project, your role in it, and the questions you hope to investigate next.

How should I prepare for a graduate school interview?+

Read the program requirements and the work of the faculty you may meet, revisit your application materials, and practice a short explanation of your past work. Prepare a small set of questions that help you assess mentorship, funding, training, culture, and the practical experience of current students.

What should I ask current graduate students during an interview visit?+

Ask how advising works in practice, what funding covers, how students receive feedback, how long milestones usually take, and what they wish they had known before enrolling. Their answers add useful daily-life context to the information a department publishes.

Do all graduate programs require interviews?+

No. Interview formats and expectations vary by field and program. Some programs use faculty conversations or visit weekends, while others make decisions from written materials. Follow each program’s instructions rather than assuming one process applies everywhere.