Most practice interviews test whether a candidate can describe themselves favorably for forty-five minutes — a skill with no correlation to answering phones kindly at 4:50 on a Friday. Better interviews test judgment with scenarios, because judgment is what you're actually hiring. Here's a question bank by role, with notes on what strong answers sound like.
For every role: the universal four
"Tell me about a time a customer or patient was angry at you for something that wasn't your fault." Listening for: ownership of the resolution without ownership of the blame, and no residual resentment in the telling. People who relitigate old grievances in interviews will relitigate yours at the desk.
"You have three things due at once: a ringing phone, a patient at the counter, and a doctor asking for something. Walk me through your thinking." Listening for: acknowledgment behavior — the strong answer greets the human first while managing the queue — and the instinct to ask what the practice's priority rules are. There's no perfect answer; there's a revealing one.
"What did your last workplace do inefficiently, and what did you do about it?" Listening for: the second half. Everyone can criticize; the candidates who improved something — even tiny — are the ones who will notice your broken processes instead of inheriting them.
"What would make you leave a job within the first year?" Listening for: honesty and fit. The answer names their real requirements — and lets you check them against the actual job before you both learn expensively.
Front desk and patient-facing roles
Scenario: "A patient calls saying their glasses are two weeks late and they're furious. You check and see the lab remade the lenses after a quality failure. What do you say?" Strong answers lead with empathy, tell the truth about the delay without blaming the lab in a way that undermines the practice, and end with a concrete next step and a specific follow-up commitment. Add: "A caller mentions new flashes of light in their vision while trying to book a routine exam." — the only right instinct is escalation per protocol, and candidates with eye care background should show it unprompted.
Technician roles
Scenario: "Your visual field printout looks unreliable — the patient was clicking randomly. The schedule is packed. What do you do?" Strong answers refuse to pass bad data downstream: rerun, flag, or annotate — anything but silence. Also: "Teach me something technical in one minute" — because techs teach patients constantly (insertion, drops, compliance), and the ability to explain simply is half the job. Certification questions ("where are you on the CPO or COA path?") reveal trajectory; our certification guides make good pre-reading for calibrating answers.
Optician roles
Scenario: "A patient hates the progressives they bought three weeks ago. Non-adapt? Fit issue? Buyer's remorse? How do you figure out which — and what do you do for each?" Strong answers show a diagnostic sequence (measurements first, adaptation coaching second, remake policy third) rather than jumping to refund or defensiveness. Add a values probe: "A patient with a modest budget asks about the premium lens the doctor mentioned. How do you handle it?" — you're hiring for honest translation, not maximal ticket.
Remote role candidates
Everything above applies, plus the remote-specific layer our vetting guide details: a live systems demo (watch them navigate your PM software or its sandbox), a written scenario response (remote work runs on precise writing), and the setup questions — workspace privacy, connectivity, hours alignment. The scenario bank works identically over video; judgment travels.
The structural advice
Score every candidate on the same scenarios, involve the person who'll manage them, and weight the interview no more than half — references and trial tasks carry the rest. And write down what "good" sounds like before the first interview: the bank above only works if the bar exists before the charming candidate walks in and moves it.
.png)
.png)
.png)
