So You've Got a Registrar Interview. Here's How It Actually Works.
Most candidates walk into a registrar interview thinking they'll be asked clinical knowledge questions. They're usually wrong. I've sat on panels and volunteered at assessment centres across three different training rounds, and the gap between what applicants expect and what actually happens is wide enough to drive a van through. The whole process varies by country and specialty, but the core structure is pretty consistent. You're being assessed on clinical reasoning, professional behaviour, communication, and your ability to handle ambiguity. Anything that looks like you're just reciting textbook answers gets flagged fast.
Common Registrar Interview Questions That Actually Come Up
Don't bother memorising answers to every possible question. Instead, understand the patterns. Panelists recycle the same frameworks with different scenarios. Here's what shows up repeatedly: Situational judgement questions like "Describe a time you made a clinical error and what you did about it." Or "A junior doctor comes to you worried about a patient. Walk me through your approach." These aren't testing whether there's one right answer. They're testing whether you have a structured way of thinking under pressure. Professional values questions come up constantly. "How do you prioritise when you have five sick patients and an admin deadline?" "Tell us about a time you disagreed with a senior colleague's management plan." The pitfall here is giving either a subservient answer or a rebellious one. The sweet spot is showing you can challenge appropriately while maintaining patient safety as your north star.
Some panels run modified Calgary-Cambridge role-plays where you're given a brief and need to conduct a consultation with an actor. I've seen excellent clinicians fail these because they focused entirely on gathering information and completely missed the emotional component the examiner was looking for. The actor is trained to show subtle cues — a hesitant parent, an anxious patient minimising symptoms. If you don't pick up on those, the panel notices immediately. MCQs and data interpretation are standard in many programmes now. Think ABG analysis, ECG interpretation, survival curves, and basic statistics questions. This part is usually the most straightforward if you've kept your fundamentals current. The trap is rushing through because it feels too easy and missing subtle qualifiers in the question stems.
Get the Full Details
What Most Candidates Get Wrong
The biggest mistake I see is performing instead of thinking out loud. Panels want to hear your reasoning process, not a polished final answer delivered with confidence. When you say "I would do X" without explaining why, you're leaving the examiner to guess at your thought process. That's a risky bet on their part, and most panellists will mark you down for it. Another common failure is the over-reliance on guidelines without acknowledging real-world constraints. Saying "I would refer to NICE guidelines" sounds good until the follow-up question is "And if that guideline isn't available in a rural hospital at 2am?" The answer they're listening for involves risk assessment, escalation, and knowing when it's appropriate to deviate from protocols. Time management during the interview itself is a silent killer. Some formats give you exactly nine minutes for a case presentation and two minutes for questioning. I once watched a candidate who was clearly brilliant spend seven of those nine minutes setting up their framework instead of getting to the clinical content. They had nothing left when the actual questioning started. Practice with a stopwatch. Not ten minutes. Nine. Because eight feels comfortable and nine feels tight, and that's exactly how the real thing will feel.
Preparing Without Wasting Three Months
You don't need to study for weeks. A focused two-week preparation block is usually sufficient if you're already in clinical practice. Here's what I'd prioritise: First, do at least three full mock interviews. Record them. Watch them back. You'll catch things in review that you never noticed while doing it — the verbal tics, the areas where you went silent for too long, the times you answered a question that wasn't actually asked because you misread the prompt. I spent eight minutes of one practice session explaining shared decision-making in a question that was specifically about consent capacity. The mock caught it before the real day. Second, refresh your clinical fundamentals. Not everything. Just the stuff that comes up in interviews: sepsis bundles, anaemia workups, chest pain pathways, acute neurological presentations, and basic pharmacology interactions. You don't need to re-read Harrison's. A couple of hours of focused revision on each topic is more useful than passively browsing textbooks.
Third, read up on the specific programme you're applying to. What's their stated values? What training model do they use? I once interviewed at a programme that emphasised rural training and continuity of care, and a candidate who'd clearly researched this wove those themes into almost every answer. Another candidate gave a perfectly competent response about metropolitan subspecialty pathways and looked visibly confused when the panel pivoted to asking about rural health equity. Context matters more than people admit.
Things I Wish I'd Known Before My First Panel
Panel composition varies but typically includes two or three consultants from your target specialty, sometimes a trainee representative, and occasionally a clinical academic or primary care physician. The trainee rep is often the most insightful person in the room. They're the one who will remember what this process felt like six months ago, and they vote the same as everyone else. Treat them with the same respect you'd give the consultant. There's also a thing called the "halo effect" that happens more often than panelists would like to admit. If someone starts strong with a compelling clinical story, subsequent answers get slightly more generous marking. Conversely, a fumbled first response can create a headwind that's hard to recover from. This doesn't mean you should curveball yourself early, but it does mean if you stumble, don't spiral. Panels reset between questions more often than candidates assume. The administrative side deserves attention too. Some programs require you to bring original certificates, references, and portfolio evidence on the day. I once saw a shortlisted candidate turned away at the door because their fellowship was an authenticated copy rather than an original, and the programme's policy was absolute on this. Check the requirements twice. Then check them a third time.
Registrar Interview Questions: The Framework That Actually Works
Stop trying to have clever answers for every scenario. Build a toolkit of four or five reusable frameworks and learn to slot any question into them. Here's the one I use and recommend: Patient safety first. Always. It's not a trick question where prioritising safety over efficiency is the wrong move. State it explicitly at the beginning of your answer and come back to it. "My first priority here is ensuring this patient is safe, so I would..." That alone covers half the marking criteria in most interview rubrics. Context matters. Before jumping to management, acknowledge what information is missing. "I don't yet know the patient's age, comorbidities, or medication list, which would change my approach. Based on what I have..." This shows clinical maturity. Beginners fill gaps with assumptions. Registrars state the gaps and work around them.
Escalate appropriately. Every program wants to know you won't float and you won't panic. The answer is usually somewhere between "I'd handle it myself" and "I'd call the consultant immediately." The right response involves assessing severity, considering your own competence, communicating with the team, and documenting everything. Say that sequence out loud. Reflect and learn. If a question asks about a past mistake or a challenging situation, the reflection part is where most candidates fall short. Don't just say "I learned from it." Say what you changed in your practice afterwards. "Since that incident, I've started using a structured handover tool that includes..." Specificity proves the learning was real, not just something you figured out they wanted to hear. Close with patient involvement. Whatever the scenario, circle back to how the patient or their family fits into your plan. Shared decision-making isn't a buzzword in these interviews. It's a core competency they're checking for.
A Specific Edge Case I Deal With Regularly
One question pattern that trips people up involves cultural competence and language barriers. The standard version goes something like: "You have a patient who speaks little English and needs an urgent procedure. Their family member wants to translate. What do you do?" The expected answer involves using professional interpreters, not family members, and explaining why. Straightforward. The edge case version I encountered last year went further. The patient had limited English but also significant hearing impairment, and the only available "interpreter" was their adult daughter who spoke the regional dialect but not standard medical terminology. The panel wanted to see whether candidates could identify that this wasn't a simple interpreter-vs-family question but a layered communication problem requiring a specialist assessment service, not a quick workaround. Two-thirds of candidates in that session defaulted to the standard answer and lost marks on the nuance. Don't be one of them.
Practical Day-of Considerations
Logistics eat into your mental bandwidth more than you'd expect. If it's an in-person interview, arrive 45 minutes early. Not 15. Not 30. Forty-five. That gives you time for security, finding the room, and sitting quietly for five minutes before the first candidate is called. I've seen capable doctors freeze in the waiting room because they were running late and hadn't had a moment to centre themselves. If it's virtual, test your camera, microphone, and internet connection the day before, not the morning of. A dropped connection during a clinical scenario question is humiliating and costly. Have a phone hotspot ready as backup. I know this from watching it happen to a colleague who ended her entire virtual interview on 4G while her home broadband decided to reconnect for an update. Bring water. Not because you'll be thirsty but because you need a deliberate pause point during your answers. A sip of water gives you three seconds to collect your thoughts mid-response. Use it. It's a small professional trick that most candidates overlook.
And when it's over, don't debrief with other candidates. Not because you're competitive but because every person's experience is different and comparing notes rarely helps anyone. Just go home, sleep, and move on. The selection process usually takes weeks to finalise anyway, and obsessing over what you said won't change it. Registrar interviews are genuinely stressful. They're designed to be. But they're also predictable if you've done the work. Focus on the frameworks, practise out loud, and remember that the panel would rather you succeed than fail. Their job isn't to catch you out. It's to find someone competent enough to train and safe enough to practice independently. Everything you do should point toward those two conclusions.
