Key takeaways
A machine learning oral exam tests whether you can explain a model out loud and then defend that explanation when the examiner pushes on it. The authors of a 2026 paper on AI-run oral exams at NYU Stern argue that a scripted answer without real understanding breaks down within one or two follow-ups. That makes the useful preparation spoken, done under questioning, and started weeks before the exam rather than the night before.
What happens in a machine learning oral exam?
There's no single format. The three published examples below have one thing in common, which is that you explain something out loud to an examiner who can question you about it.
- Task-based, with article skills in the objectives. Aalborg University's 2024/2025 Specialisation Course in Machine Intelligence, part of its MSc in Computer Science (IT), lists an individual oral exam of 45-minutes, with a task handed out 7 days before the examination. The module description says students must present a scientific article's "premises, issue(s), theory, methods, results and conclusions" and assess how practical its proposed solutions are.
- Course content plus project. The University of Pisa's Generative and Deep Learning course says its oral examination "will test knowledge of the course contents (models, algorithms and applications)." Students on the traditional route, who don't take the midterms, also deliver a final project and present it with slides for a presentation of 15 minutes during the oral.
- Project and case, run by AI. NYU Stern's undergraduate AI/ML Product Management course ran its final oral exam through a voice AI examiner for two cohorts (36 students in Fall 2025, 37 in Spring 2026), as Panos Ipeirotis and Konstantinos Rizakos describe in a paper published in Communications of the ACM. One phase asked about each student's own capstone project. Another walked through a product case study. It's a product management exam rather than a modeling one, but it's the only one of the three with published data on how students experienced it.
Read your own syllabus before anything in this post. The format decides what you practice.
Why do follow-up questions catch students who studied by reading?
Reading builds recognition. You see the bias-variance tradeoff on a slide, it looks familiar, and familiarity feels like knowing it. An oral exam asks for something else, which is producing the explanation from nothing and then extending it in a direction you didn't choose.
The follow-up is the part you can't prepare a script for. In the NYU Stern paper on the AI/ML Product Management exam, the examiner's questions are calibrated to what the student just said, and the authors argue that "a scripted answer that does not reflect actual understanding breaks down within one or two follow-ups." The project phase made this concrete by asking about each student's "goals, data choices, modeling decisions, evaluation approaches, and failure modes," which nobody can improvise convincingly about work they didn't do.
Expect follow-ups from a few families. Why does this work? When does it fail? What would you change if the data looked different? How would you know it was wrong? Each one starts from your previous sentence. That's why a student who can recite the derivation of logistic regression still stalls when asked what happens to it on perfectly separable data.
The practical lesson is that every topic on your list needs two layers. The first is the explanation. The second is the answer to "why" asked twice in a row.
How stressful is an ML oral exam, and does practice fix the nerves?
The best published data says students in one AI-run oral exam found it more stressful than a written one, and offers a small hint that experience didn't help. The safe plan is to prepare to perform while nervous rather than to stop being nervous.
The NYU Stern study surveyed both cohorts of its undergraduate AI/ML Product Management course after their AI-run oral exams. In the first cohort, 83% of respondents found the exam more stressful than written exams. In the second cohort, which sat the exam after several fixes to the examiner, 63% did. In the first cohort, 70% agreed the exam tested their actual understanding. Those numbers come from one course at one institution, so they say nothing reliable about human-run oral exams elsewhere.
One more detail in the NYU Stern data is about experience. You'd expect students who had sat oral exams before to be calmer. They weren't. Every respondent with prior oral-exam experience (all 5 in Fall 2025 and all 4 in Spring 2026) reported the AI exam more stressful. The groups are tiny, so this is a hint rather than a finding, but it's a hint against expecting familiarity alone to calm you down.
What practice does change is how well you think while your heart rate is up. If you've explained gradient descent out loud twenty times, the twenty-first time under stress still has a path to follow. Four-Leaf's guide to interview anxiety covers the in-the-moment techniques, and they transfer directly to an exam room.
What topics should you be able to explain out loud?
Start from the syllabus, then turn each topic into four questions you can answer in under two minutes without notes:
- What problem does this solve?
- What does it assume about the data?
- How is it trained or computed?
- How does it fail, and how would you notice?
The fourth question is the one to spend the most time on, because it's where follow-ups naturally go. For a linear model, it's what happens with correlated features. For a decision tree, it's overfitting and what pruning trades away. For a neural network, it's vanishing gradients, overfitting and what each regularizer actually does to the weights.
If your exam centers on a research article, Aalborg University's Machine Intelligence course description makes a good checklist, since it asks students to present an article's premises, problem, theory, methods, results and conclusions. Can you state the paper's premise, the problem it addresses, the theory behind it, its method, its results and its conclusions? Then can you say where the method would break and what the authors didn't test? That last step is what "assess their qualities and practicality" means in practice.
For a project-based exam, rehearse your own decisions. Why that dataset, why that model, why that metric, and what you'd do with another month. Questions about why you built it that way test understanding in a way the finished report can't.
How should you practice for a machine learning oral exam?
Practice the way the exam runs, which means speaking, being interrupted and answering one question at a time.
- Explain each topic out loud, cold, and record it. Two minutes, no notes. Play it back and note every place you said "basically" or trailed off. Those are the gaps.
- Get asked follow-ups, one at a time. A classmate works well if they ask "why" and "what if" rather than nodding along. In the NYU Stern exam, question stacking was the most common Fall 2025 complaint about the AI examiner, matching a 31% stacked-turn rate, even though its prompt said "You must NEVER ask two questions in the same turn." Your practice partner should follow that rule.
- Talk while you write. If your exam has a board or paper, practice writing a derivation while narrating each step. Narrating as you go gives the examiner a chance to redirect you before you're five lines down the wrong path.
- Rehearse not knowing. Pick a question you can't answer and practice reasoning toward it out loud from what you do know. A visible line of reasoning gives the examiner something to follow up on, which silence never does.
- Run one full mock under time. Use your exam's real length, from your own course's rules, with someone who hasn't seen your notes.
If you don't have a practice partner, a voice mock interview can stand in for the follow-up drill. Four-Leaf's voice mock interviewer is instructed to ask one question per turn and usually follows up on the answer you just gave before moving on. It's designed for job interviews rather than coursework, so bring your own topic list. Four-Leaf's guide to practicing interviews alone covers the recording and mirror methods in more detail.
What is overrated
Rewriting your notes. It feels productive and it builds recognition, which is the skill the exam doesn't test. Time spent tidying a summary sheet is time not spent saying the material out loud.
Memorizing model answers is overrated too, for the reason the NYU Stern paper on AI oral exams gives. A rehearsed paragraph covers the first question and none of the ones after it. Memorize definitions, key equations and the names of things. Then practice saying everything else in your own words, slightly differently each time, so you aren't depending on one phrasing.
How does an ML oral exam compare with an ML engineer interview?
Closely. The authors of the NYU Stern paper on AI oral exams extend their argument past the classroom to "a job interview, a professional licensing board" and anywhere else a polished artifact stands in for understanding that ought to be tested directly. An interviewer asks you to explain regularization, then asks what happens when you double the penalty, then asks how you'd detect that in production.
That overlap is useful if you're finishing a degree and heading into the job market. The habit of explaining a model and then defending it is the same habit the ML fundamentals and system design rounds test. Four-Leaf's breakdown of MLOps and ML engineer interview questions maps the four rounds those loops usually run, and the machine learning engineer interview prep page covers the technical, system design and behavioral questions those loops ask.
The difference is stakes and scope. An exam tests a syllabus you were given. An interview tests whatever the team cares about, plus production questions no course covers. Treat the oral exam as the rehearsal it is.
Where this is heading
The NYU Stern paper on AI oral exams opens with an argument every ML student should take seriously. "Written work no longer certifies that a student understands it," the authors write, and "oral examinations restore that evidentiary link." Their system graded a full cohort's oral exams for under one dollar per exam, on top of a voice subscription that covered the speaking time. When a format that resists ghostwriting gets that cheap to grade, expect to meet it more often.
That makes explaining your work out loud, under questioning, a skill worth building on purpose. Before the exam, get asked "why" twice on every topic, and make sure you have an answer both times.