Why Oral Assessment?
Most of your career will not involve sitting quietly at a desk writing answers on paper. It will involve explaining your thinking to a teammate, walking an interviewer through how you'd solve a problem, defending a design decision in a code review, or teaching a concept to someone who needs to understand it to move forward.
Oral assessment trains that exact skill. When you come in for an interview, you're not just demonstrating that you know something — you're demonstrating that you can communicate it. That's the harder and more valuable skill.
There's also an honesty component. A written test can be memorized the night before and forgotten the next day. A conversation can't be faked in the same way. If you understand the material, talking about it should feel natural. If you don't, that will become clear quickly — and that's actually useful information for both of us. It lets us figure out where the gap is and address it, rather than discovering it on a final exam when it's too late.
Why First-Come, First-Served?
Appointments sound fairer but they aren't, for a few reasons.
Appointments favor students who plan ahead, who are organized, who already feel comfortable engaging with their instructor. Students who are struggling — the ones who most need to come in — often don't make appointments because they feel like they're not ready, or they're embarrassed, or they keep thinking they'll figure it out on their own. By the time they book an appointment, weeks have passed.
A first-come queue removes that barrier. Show up, join, wait your turn. No planning required. No commitment to a time slot three days in advance. The student who finally decides at 2pm on a Tuesday that they need help can act on that impulse immediately.
It also creates a natural rhythm. Students who are keeping up with the material can come in regularly, build a habit, and stay current. The queue rewards consistency.
What the Grades Actually Mean
When you come in for an interview, your performance is evaluated on a four-level scale. Here's what each level actually means — not just as a grade, but as a description of your understanding.
Mastery
You understand the concept deeply and can explain it clearly, apply it to new situations, handle follow-up questions, and reason about edge cases. You could teach this to someone else.
Approaching Mastery
You understand the core idea and can explain it in straightforward cases. Some gaps show up when the problem gets harder or when the question changes direction. Solid foundation, some work still to do.
Proficient
You have a basic working knowledge — enough to answer surface-level questions, but the understanding isn't deep yet. You know what it does but not fully why, or you can describe it but struggle to apply it.
Incomplete
Not enough demonstrated yet to evaluate. This usually means the interview was too short, you weren't able to attempt the material, or the preparation wasn't there. Come back when you've had more time with it.
The most important thing to understand about these levels: your grade is always your highest earned level. A better performance later can only help you, never hurt you. There is no downside to coming in and trying.
The Baseball Bat Analogy
Baseball players warming up in the on-deck circle swing a weighted bat — heavier than the one they'll actually use in the game. They do this deliberately. When they step up to the plate and swing the real bat, it feels lighter. The harder preparation makes the actual performance easier.
That's exactly what's happening here.
The oral interview format is harder than a multiple choice test. It requires you to think on your feet, explain your reasoning, handle unexpected questions, and communicate under mild pressure. It will feel uncomfortable at first, especially if you're used to being able to look things up or take your time.
But here's what happens: when you walk into a real job interview — and you will — and the interviewer asks you to explain how a hash table works, or walk them through a sorting algorithm, or describe how you'd design a system — it will feel familiar. You've done this before. You've practiced explaining things under pressure, in real time, to someone who will ask follow-up questions.
The weighted bat is the interview session. The real game is the career that comes after.
On AI Tools and Academic Integrity
Large language models are powerful tools and you should absolutely use them — for studying, for exploring ideas, for generating examples, for getting unstuck. That's not cheating. That's using available resources intelligently, which is itself a skill your career will require.
The line is this: you must understand every line of code or every argument you bring into this course. If you submit code generated by an AI, by a classmate, by a tutor, or by anyone other than yourself, that's fine — but when you come in for your interview and I ask you about it, you need to be able to answer.
Why did you implement it this way? What would happen if the input were empty? What's the time complexity? Could you write this differently? If you can't answer those questions, I know you don't understand the material — and that's what I'm grading. Not the code. Not the product. The understanding.
AI tools that help you learn faster are excellent. AI tools that let you skip learning are counterproductive — and the interview will make that clear.