CRNA Interview Clinical Scenario Questions: 3 Stories

Updated September 2026

Most CRNA interview clinical scenario questions come down to 3 prompts: a conflict with a provider, an ethical bind, and a patient who was crashing. Committees score judgment, escalation, and ownership. So prep 3 stories, not 12.

What CRNA interview clinical scenario questions actually sound like

You know that moment when the interviewer says "tell me about a time you disagreed with a physician" and your brain serves you up a completely blank white wall? Yeah. And that happens to almost everybody, and it isn't because you have no stories. It's because you've got 400 shifts in your head and no index.

So let me give you the actual wording. Back in episode 14 I listed what programs ask, and two of them show up over and over. "Tell me about a time you had conflict or had to solve a problem." And "tell me about a situation where you had to confront a colleague." That's it. That's the whole scary thing.

And the prompts our members are drafting answers for in our chatbot are almost the same three every time. Disagreeing with a resident about extubating a patient after an SBT. A patient who self-extubated and then wanted to leave AMA. A hypotensive patient who kept sliding even on high-dose norepinephrine. Three buckets. Conflict, ethics, crashing patient.

I'm not saying the wording will be identical at your program. It won't be. And every committee has their own house question and some of them are weird. But the underlying thing they're digging for is the same, and once you see that, you stop needing a story for every possible prompt.

Go deeper in the Learning Library

Emotional Intelligence

The emotional intelligence questions programs ask, why they ask them, and how to answer with a real story instead of a script.

Start with a free trial →

What is the committee actually scoring here?

Listen, they are not grading your patient. They genuinely do not care that your guy was a 62-year-old post-op CABG. They're scoring you. So, three things, and I want you to hold onto these because everything else in this post hangs off them.

Number one, judgment. Did you notice the right thing, and do you know why it mattered? Not "his pressure was soft." More like, his pressure was soft and his lactate was climbing and his urine output had been garbage for 4 hours, and that combination meant something to you.

Number two, escalation. Who did you tell, and in what order? And this is the piece people skip completely. They tell a great story about noticing something and then it just sort of resolves off-screen. No. Say the chain out loud. Charge nurse, resident, fellow, attending, rapid response, whoever it actually was.

And number three, ownership. What was yours in this? What would you do differently? Every single scenario answer should end with one honest sentence about what you'd change. Not a groveling one. But an honest one.

The closest public checklist to what programs score these against is the COA critical care competencies. I'm not going to restate them here because that post already does it. But read them once and then look at your 3 stories and ask which competency each one is quietly proving. It changes which details you keep.

Why does the story where you were right go so badly?

Okay so this is the one that stings a little. But the instinct is to pick the story where you caught something everybody else missed, you pushed back, and you were vindicated. Hero story. And it feels great to tell.

But you know what a committee hears? Someone, not you, but someone who is about to spend 3 years inside a care team with anesthesiologists, surgeons, and a clinical coordinator, and who has already framed themselves as the only competent person in the room. That's the read. It's not fair, exactly, but it's the read.

So pick the version where it was genuinely murky. Say you had a patient who passed an SBT and the resident wanted the tube out, and you thought the secretion burden was too high and the mental status was too soft. Maybe you were right. Maybe you weren't. The good answer says what you saw, what you said, who you looped in, and then what the team decided, even when the team decided against you and it turned out fine.

I'm not saying invent humility you don't have. And I'm definitely not saying pick a story where you were negligent. There's a middle version of almost every disagreement where two reasonable people read the same patient differently, and that's the one you want.

How do you build the 3 stories?

Alright. Buckle up, buttercup, this is the part where you actually do work instead of reading about doing work. You're building 3 stories and then you're done building stories.

So each story gets 5 or 6 beats and no more. Setup in one line. What you noticed. What you did. Who you escalated to. What happened. What you'd do differently. That's it, and it should take you about 90 seconds to say.

The how-you-tell-it part, the actual structure of a story, is its own animal and I'm not re-teaching it here. Go read the what, how, and why storytelling breakdown and build your beats on that scaffolding.

And write them down. Like, physically. I've watched people carry three great stories entirely in their head, walk into the interview, and lose the middle of every one of them. Typing it out once fixes most of that.

Do you need the clinical numbers in a scenario answer?

Some, yes. Not all of them. And there's a difference between a scenario question and a knowledge question, and people blur them into one giant anxiety ball.

A knowledge question is "what does a wedge pressure of 24 tell you." That's a different beast and it lives over in the Swan-Ganz interview post, which is where you should go for waveforms and numbers. A scenario question is "tell me about a hemodynamically unstable patient." Different prompt, different scoring.

But the scenario answer gets better when you sprinkle in 2 or 3 real numbers. Say you had a patient severely hypotensive on high-dose norepinephrine. Saying the actual dose you were at, saying the MAP you were chasing, saying the lactate, all of that signals you were the nurse in the room and not somebody reciting a case study.

And if you blank on a number mid-answer? Say so. "I'm actually blanking on the dose right now, but I know it's going to come to me." That's a completely survivable sentence. Way better than a guess that's off by a factor of ten.

What goes wrong when people practice these?

So three things, and I've seen all three enough times that they're basically predictable now.

First one. So they practice silently. They read their story in their head 40 times, feel great, and then the first time the words leave their mouth is in front of a panel. Don't do that. So say it out loud to your dog, your car, your phone, whoever.

Second. They fill every gap. Something I said in episode 14 and I'll say again here: be okay with silence. When they finish the prompt, taking 3 seconds before you start is not a failure. It reads as considered. Filling those 3 seconds with "um, so, like, one time" reads as panic.

Third. They pick a story that does not survive a follow-up question. And the committee is going to ask what you would have done if the patient got worse, or what the attending said after. If your story is thin, the follow-up eats it. So just to recap the three failure modes: no reps out loud, no tolerance for silence, and a story with no depth behind it.

There are a bunch of other interview traps I'm not covering here, and most of them are in the mistakes to avoid post. Some of them are dumb and avoidable, and nobody is above the dumb ones.

Our Final Thoughts

Three stories. Conflict, ethics, crashing patient. And say each one out loud until it's 90 seconds and not 4 minutes, and end every one with the thing you'd do differently. That's the whole assignment. And if you're sitting there certain you have no good stories, you do. You just haven't gone looking through your own shifts yet, and that's a one-evening job, not a personality problem.