TL;DR
- Oral defenses differ by field, but the questions underneath them don't — almost every committee is testing the same twelve things.
- The problem usually isn't knowing the answers — it's retrieving them out loud, under pressure, on the spot.
- STEM defenses tend to weight methodology questions more heavily; humanities defenses tend to weight framing and theory more heavily.
- A precise, specific answer about your study's limits reads as rigor. A vague one reads as evasion, even when it's true.
- Rehearsing a one-sentence answer to each question, out loud, closes the retrieval gap before it costs you in the room.
Every field has its own vocabulary, but dissertation defense questions are more similar to each other than most candidates expect. Committees are, in the end, testing the same handful of things: whether you understand your own work, its limits, and what it would mean to do it again.
Here's the part most prep advice skips: knowing the material isn't the hard part. I've advised students who could talk about their dissertation for an hour without notes, and still froze the moment a committee member asked them to say one specific thing, one specific way, on the spot. The defense doesn't test what's in your head. It tests what you can pull out of your head when someone's waiting for an answer.
The defense committee tests what you can retrieve when it matters — not what you know.
Why the same questions keep showing up
A defense isn't really an exam on your dissertation's content — the committee has already read it. It's an exam on your relationship to that content: can you explain it, defend it, and locate its weaknesses without the manuscript in front of you.
This isn't a new observation. Back in the 2010s, Open University researcher Rebecca Ferguson compiled a list of 40 recurring viva questions that's still circulated by prep guides today — proof that the pattern isn't specific to one field or one decade. The twelve below are the ones that come up most often across that lineage, grouped by what they're actually probing for.
How the questions shift by field
The twelve underlying categories hold across disciplines, but which ones get the most weight in the room varies.
STEM defenses tend to spend disproportionate time on methodology questions — sample size, instrument validity, why this statistical test and not another. The committee is often verifying technical correctness as much as intellectual contribution. A methods choice that would get a single follow-up question in a humanities defense can become the center of a twenty-minute exchange in a STEM one.
Humanities and qualitative social science defenses lean harder on framing and theory instead — how your interpretive lens shapes what counts as evidence, and why you chose that lens over an adjacent one. The "who is this for" and "why does this matter outside academia" questions tend to land with more weight here too, since the connection between the work and its audience is less self-evident than in an applied STEM study with an obvious practical use.
Neither pattern is a rule. Individual committees vary by the people on them as much as by field. But it's worth weighting your rehearsal time accordingly, rather than treating all twelve as equally likely to dominate.
Interdisciplinary work tends to get a mix of both — expect questions from whichever side of your committee leans more methodological, and questions from whichever side leans more toward framing and contribution. If your committee is split across departments, it's worth rehearsing with that specific split in mind rather than assuming one dominant style.
Your contribution and your choices
These open almost every defense, because they're the ones that separate "did the work" from "understands the work."
- What is your contribution, in one sentence?
- Why this method, and not an alternative?
- What would you do differently if you started again?
- What's the weakest part of your argument?
Knowing the material doesn't guarantee you can answer these under pressure — it's a different skill, and the gap between the two is where most defenses actually go sideways.
"It was right there." The committee asked them to explain the statistical tool they'd used. Simple question. They'd presented it a dozen times in practice. The slide was already on the screen.
They froze. Stared at it. Couldn't find the words. The answer was literally right in front of them — and they still couldn't say it. That's when they realized: knowing your content isn't enough. You have to train yourself to access it under pressure.
"I told them." I warned him: "The committee will ask about your research gap. Be ready to explain it in one clear sentence." We practiced it. He said: "I've got this."
Defense day came. The committee asked: "Where exactly is the research gap in your study?" He froze. Talked about methodology, sample size, timeline — anything except the actual gap. The committee pressed him three times. He never gave a clear answer.
Afterward, he messaged me: "You told me this would come up. I should've listened." I've seen this dozens of times. Students who know their topic can't articulate the one thing that justifies their entire study. That's not a knowledge problem — that's a preparation problem.
Your committee doesn't need you to be brilliant, but clear.Questions 5–8 of 12
The field and the limits of your claim
Once contribution and choices are settled, committees turn outward — checking whether you can place your work honestly against everyone else's.
- How does this connect to [a paper the committee assumes you've read]?
- What are the limits of your sample or scope?
- Who is this work actually for?
- What surprised you during the research?
The "who is this for" question is really two separate questions committees sometimes fold into one: contribution to your field (academic) and actionability of your findings (practical). Answer both — not just whichever one comes to mind first. Editage's defense-prep guide lists this as its own question category — who benefits from the research, separate from where the study goes next — worth treating as two answers, not one.
The "limits of your sample or scope" question deserves more attention than most candidates give it in prep. It's tempting to treat scope limitations as a weakness to minimize.
But a precise, specific answer here reads as rigor, not weakness. Something like: "this applies to first-generation undergraduates at large public institutions; I can't speak to how it generalizes to selective private schools, because the enrollment patterns differ enough that the mechanism I'm describing may not hold."
A vague answer — "well, every study has limitations" — reads as evasion, even when it's technically true. The specificity is what separates a strong answer from a weak one here. Not whether limitations exist. They always do. The committee already knows that; what they're checking is whether you know exactly where yours are.
Questions 9–12 of 12What happens after the defense
The last four are forward-looking — they're checking whether you see the work as finished, or as one step in something ongoing.
- How do you respond to the obvious counterargument?
- What's the next study, if you kept going?
- Why does this matter outside academia?
- Is there anything you'd like to add?
Two of these are worth seeing in shape, not just naming.
The counterargument question. The move worth copying: cite the study that could be used against you, before someone else brings it up. In one consultancy client's related-work section, a specific prior study was named and its finding used as the setup for the exact gap their own work addressed — rather than pretending the prior research didn't exist. Naming the counterargument yourself, on your own terms, reads completely differently than having a committee member surface it for you.
The next-study question. A consultancy client's recommendations section didn't say "more research is needed" and stop there. It named a specific hard-to-reach subgroup from the original study, proposed a specific method — ethnographic interviews — to understand that group's barriers, and pointed to one concrete follow-on study: a feasibility trial tailoring intervention delivery to that subgroup's needs. Specific limitation → specific method → specific next study. That sequence is the whole pattern; it works regardless of field.
How to rehearse an answer
Write a one-sentence answer to each of these twelve before you write a paragraph. If you can't compress it to one sentence, that's the part to work on — not the part to over-prepare with more words. The Master's student above had plenty to say about his research gap. What he didn't have was one sentence he could reach for under pressure.
Then say the sentence out loud, to another person, under mild time pressure. Reading an answer silently and defending it out loud under questions are two different skills — the student who froze on the statistics question wasn't unprepared on paper. He was unprepared out loud.
The night before
Don't reread the whole manuscript. Reread your one-sentence answers to these twelve questions, and get some sleep. Committees can tell the difference between someone who knows their work and someone who memorized their manuscript the night before — and it isn't the second one who does well.
If a question here catches you off guard because your chapters never quite connected to each other, that's usually an outline problem more than a memory problem — see how dissertation chapters should set each other up.
