A patient whose progress doesn't match the expected timeline
The scenario describes a patient recovering from a described injury whose progress has plateaued earlier than the initial plan expected, and asks for the reasoning out loud, what to check first, whether the original evaluation missed something, and how the plan itself should change.
Follow-up questions push on specifics, which objective measure to reassess, whether the plateau suggests a modification to the exercises themselves or a deeper look at compliance, and how that reasoning would be explained to the patient without sounding like the original plan was wrong.
What the session actually asks
Expect the session to open with a described evaluation or treatment-planning scenario that has a specific clinical answer buried inside it, not an abstract question about treatment philosophy in general.
Follow-up questions test whether the reasoning holds together when a new detail is introduced, a plateau, an unexpected pain response, a change in the patient's home situation, since two candidates can describe the same starting plan and only one of them can explain clearly what changes and why when the case doesn't go as expected.
The session stays on clinical and biomechanical reasoning throughout, rather than branching into patient motivation or interdisciplinary questions, which the general and comprehensive types cover instead.
Scoring
How the Technical dimension gets scored here
Technical carries the most weight in this session specifically, and the written reasoning behind the score explains what drove it, whether the evaluation logic was sound, whether a plan modification was defended with a real clinical reason rather than guessed at, and whether the answer actually adapted when the scenario's details changed.
Calibration floors and caps apply here the same way they do everywhere else on Intervieux, so a confident-sounding but vague answer about treatment planning can't outscore one that's less polished but clinically specific. Communication still factors in on how clearly the reasoning gets narrated, since explaining a plan change to a patient or a referring physician is a real part of the job too.
Frequently asked questions
Does this test hands-on technique, or the reasoning behind a treatment decision?
It tests the reasoning. The session is a spoken conversation about evaluation and treatment-planning logic, not a demonstration of manual technique.
Will it ask about a specific diagnosis or a general case?
The scenario describes a specific case with enough clinical detail to test real reasoning, though it's built to apply across common orthopedic and neurological presentations rather than one narrow diagnosis.
How is this different from the general physical therapist interview?
General covers a setting-neutral round of evaluation, motivation, and coordination questions. This session stays specifically on treatment-planning and biomechanical reasoning.
Is it possible to dial up the difficulty for this session?
Yes. Choosing an analytical or challenging personality with a formal style sharpens the follow-up questions considerably.
Is this useful for a new graduate without much independent caseload experience yet?
Yes. The scenario tests clinical reasoning through a described case, which a new graduate can practice without needing years of independent evaluations behind them first.
Related pages
Practice the clinical reasoning, not just the plan
Run a technical AI interview to work through evaluation and treatment-planning reasoning out loud, then get scored on how clearly and specifically that reasoning holds up.