Occupational Therapy Interview Questions

So You Need to Nail an Occupational Therapy Interview

Let's just get straight to it. You've got an interview coming up. Maybe it's your first post-graduation position, maybe you're pivoting from acute care to outpatient, maybe you're in private practice and need someone who won't crack under billing pressure. It doesn't matter what context you're in. The questions are more similar than you think, and the mistakes candidates keep making are remarkably consistent. Here's the thing most candidates miss: interviewers aren't trying to catch you. They're trying to figure out if you'll be safe, communicative, and survivable on their team for more than three months. Three months is the rough average before new OTs burn out or get let go, by the way. That stat alone should shape how you answer everything. The questions break into roughly five buckets. Clinical reasoning and case presentation. Behavioral scenarios. Scope and boundaries. Documentation and compliance. And the ones that seem casual but aren't — things like "why our clinic?" or "where do you see yourself in five years?" Don't sleep on those either. They're filtering for retention risk.

I sat on a hiring panel at a hospital system once. We had a candidate — solid grades, great fieldwork evaluations, perfect on paper. Then we asked her to walk us through how she'd approach a post-stroke patient with hemiparesis, aphasia, and significant safety concerns with ADLs. She gave me a textbook answer. Fine. Then I pressed: "OK, now the patient gets frustrated and refuses to participate in therapy after session two. What do you do?" She froze. Couldn't pivot. Hadn't practiced thinking out loud under mild pressure. We didn't hire her. Not because she was incompetent. Because the interview revealed she'd likely shut down in real situations that require quick adaptation. That story exists to tell you something practical: practice verbalizing your thinking. Out loud. To another person. Not just writing answers down and memorizing them. There's a difference between knowing the material and being able to demonstrate it under mild stress.

How to Structure Your Answers Without Sounding Robotic

The STAR method — Situation, Task, Action, Result — is standard advice everywhere. I'm not going to skip it because it's standard for a reason. But here's what nobody tells you about using it properly. Most candidates compress the Action part and inflate the Situation and Result. They spend two minutes describing the patient and thirty seconds explaining what they actually did. That's backwards. The Action is the whole point. This is where you show clinical reasoning, not where you pad your word count. Aim for roughly this ratio: 15% Situation, 15% Task, 60% Action, 10% Result. Keep each component tight. If you find yourself going over two minutes per answer, you're either choosing too dramatic a situation or you haven't practiced enough. Pick a moderate-complexity case from fieldwork. Something that showed good judgment without being a miraculous outcome. Honest results beat impressive results every time.

Behavioral Questions and the Follow-Up Trap

Behavioral questions start with "Tell me about a time when..." or "Give me an example of..." These are designed to extract a real behavior, not a hypothetical one. The problem is that follow-up questions. Interviewers will drill deeper after your initial answer. They might ask about conflict, about failure, about a moment you disagreed with a supervisor. I once interviewed a candidate who described a time she disagreed with a physician's treatment plan. Good answer. Strong clinical judgment. Then the interviewer asked: "And what happened after that conversation?" She couldn't remember the outcome. Hadn't thought about it. It turned out she never followed up after that discussion, left the decision to the attending, and the patient's progress suffered as a result. Red flag. Not because she disagreed — disagreement is good. Red flag because she didn't own the downstream consequences of her communication choices. The workaround for this is simple but most people don't do it. After you pick a story to tell, write down not just what happened but what happened next. And what you learned from what happened next. Two sentences. That's it. It changes your answer from a monologue into a complete clinical narrative.

Clinical Reasoning Questions — Where Most Candidates Fold

These are the questions that separate people who've actually done therapy from people who've only read about it. You'll get case vignettes. Sometimes they're detailed, sometimes they're deliberately sparse. The sparser ones are harder because you have to ask for information rather than having it handed to you. Here's a counter-intuitive insight: interviewers often prefer you to ask clarifying questions over jumping to a solution. A candidate who says "Before I proceed, I'd need to know the patient's baseline cognition, medical stability, and home situation" is demonstrating better clinical reasoning than one who immediately launches into a treatment plan. You don't have all the data. Acknowledging that and systematically requesting what you need is a skill. Demonstrating it earns points. Another thing people get wrong: they treat these questions as if there's one right answer. There isn't. There are defensible answers and indefensible ones. An indefensible answer ignores safety, violates scope of practice, or recommends something outside evidence-based guidelines. A defensible answer shows you considered multiple factors and chose a path with rationale.

I had a colleague who interviewed candidates at a pediatrics clinic. She'd ask them to prioritize interventions for a child with cerebral palsy who needed seating, feeding, and play access. Most candidates picked one and ran with it. The strongest candidates listed the priority framework they'd use — medical stability first, then function, then participation — and explained why that hierarchy made sense for that specific child. That's the level of thinking they were looking for. Not a single correct intervention but a correct process.

Scope, Ethics, and the "I Don't Know" Question

You will be asked about ethical dilemmas. You will be asked whether you know your limits. The worst thing you can do is pretend you know everything or dodge the question about your limitations. Here's the practical truth: saying "I don't know" to a clinical question is fine. Saying "I don't know" to an ethical or scope question without immediately following it up with how you'd handle not knowing is a problem. The follow-up matters more than the admission. A good template: "I don't have direct experience with that specific scenario, but here's how I would approach finding the right answer — I'd consult the AOTA code of ethics, review relevant state practice act provisions, and seek guidance from a licensed supervisor or colleague before proceeding." That's two sentences. It shows you know where to look and that you won't wing something that affects patient care.

There's also a less obvious trap. Some candidates over-disclose. They volunteer personal struggles or admit to mistakes that weren't caught or reported. There's a line between honesty and oversharing. Mistakes you learned from and fixed? Fine. Mistakes that are still unresolved or that you handled poorly without seeking supervision? That's your responsibility to fix before the interview, not material to bring into it unless specifically asked.

Documentation and Compliance — The Boring Questions That Matter

People skip prep for this category. They think it's dry. It's not. It's where jobs are lost. You will be asked about documentation. You will be asked about Medicare, about billing, about what to do when you're behind. Be honest about your experience level with documentation. If you've only done school-based or academic charting, say so. If you've worked in acute care with SOAP notes and interdisciplinary charts, mention it specifically. The interviewer needs to know what training load they're signing up for. Here's something I wish more candidates understood: they'll ask about documentation mistakes. This is usually a trap question disguised as humility. The correct answer acknowledges a real mistake, describes what you changed afterward, and demonstrates that the change stuck. "I once wrote a goal that wasn't measurable. My supervisor flagged it. Since then I use the SMART framework and run my goals past a peer before finalizing." That's the arc they want to hear. Not perfection. Growth with proof.

Situational Questions and the Pressure Test

Situational questions are hypothetical. "What would you do if..." These test your instinct more than your experience. And here's the part that surprises people: they're often more stressful than the behavioral questions because you can't fall back on "this actually happened to me." My approach to these has always been to anchor your answer in a framework rather than a specific technique. When asked what you'd do in a novel situation, explain your decision-making process first, then apply it. This signals that you can handle the unexpected, not just the rehearsed. For example, if asked how you'd handle a patient who becomes aggressively noncompliant, don't just say "I'd de-escalate." Explain your de-escalation framework. Name the steps. Show that you have a repeatable method, not just a reactive impulse. That distinction is what separates a technician from a clinician in the interviewer's eyes.

Questions You Should Be Asking Them

Every interview has a Q&A portion. This is where you prove you've done research and that you're evaluating them as much as they're evaluating you. Good questions include inquiries about caseload composition, mentorship structure, documentation expectations, and turnover rates. Bad questions are ones whose answers are publicly available on the website. I've seen candidates ask about benefits and PTO in the first interview. Save that for offer stage. It's not wrong to care about those things — it's strategically wrong to lead with them. It signals that you're optimizing for comfort rather than growth, which is a legitimate concern for a hiring manager who's already worried about retention.

The Casual Questions That Aren't Casual

"Why this clinic?" "Why occupational therapy?" "What do you do for fun?" These feel like icebreakers. They're not. They're cultural fit assessments and commitment probes. The "why this clinic" question has a right answer and a wrong answer. The wrong answer is generic praise or something that could apply to any clinic. The right answer references something specific about their patient population, their approach to care, their community reputation, or a service line they offer that aligns with your interests. Even if you're a new grad and don't know everything about them, show that you looked. For the "what do you do for fun" question, honesty works best. Don't invent hobbies. But also don't give an answer that signals you'll be checked out emotionally on weekends and beyond. Something that shows engagement, even if it's quiet engagement, reads better than "I like to sleep" — which, fair, but not helpful in an interview context.

A Practical Preparation Routine

Here's what I'd actually recommend spending your prep time on, ordered by priority. First, write out fifteen STAR stories covering conflict, failure, ethical dilemma, teamwork, time management, adaptation, advocacy, and clinical reasoning. Second, practice delivering them out loud to a friend or recorder. Third, research the specific clinic or facility and prepare three tailored answers. Fourth, prepare five questions to ask them. Fifth, get a good night's sleep before the interview. That's it. No miracle techniques. No special outfits beyond professional attire. Just deliberate practice and basic preparation. The candidates who consistently perform well aren't the ones who memorized the most answers. They're the ones who practiced thinking clearly under mild pressure. Everything else is decoration.