How to Screen Pharmacy Technicians: 9 Questions and What to Listen For Screening Interview Template

What pharmacy settings have you worked in (retail chain, independent, hospital or health system, long-term care, mail-order, sterile or non-sterile compounding), how long in each, and roughly how many prescriptions did your pharmacy fill in a typical day? Describe what you personally did during a shift at the busiest one.

What this assesses: Setting and volume tell you more than years in the field do. Strong answers name the setting, give a real number, and then describe the actual shift rather than the job title: 400 to 600 scripts a day at a chain where they ran data entry and worked the rejection queue all morning, or a hospital where the day was unit-dose carts, Pyxis restock on three floors, and whatever the OR needed. They separate what they did from what the pharmacy did, which is the first thing to listen for. The second is the gap between the setting they have and the setting you are staffing. A tech with three years at a retail counter is not unqualified for a hospital, but they have likely never gowned up for a sterile hood, never worked to a USP 797 beyond-use date, and never been a second set of eyes on a hazardous prep. If that is your job, you are hiring for training time, and you should decide now whether you have it. The reverse gap is just as real. A hospital tech who has never touched third-party billing will be slow at a drop-off window for months. Volume is also a workload preview worth taking seriously. Someone whose heaviest day was 120 scripts may be excellent and still be flattened by your 700. Be cautious with a candidate who claims every setting equally with no detail in any of them, who cannot give even an approximate volume, or who describes the pharmacy's work entirely in we.

List the credentials you hold right now with their exact expiration dates: your certification (PTCB CPhT, NHA ExCPT, or another), your state board registration or license, and any specialty certificates such as sterile compounding or immunization administration. Where are you in your current continuing education cycle?

What this assesses: Asking for dates instead of a yes is what makes this question work. Strong answers give the dates, or say plainly that they will pull the card and confirm by tonight. Strong candidates also keep certification and state registration separate in their heads, because they are different things issued by different bodies, and most states require the registration whether or not the tech is nationally certified. Requirements vary more here than in almost any other allied-health role. Some states register technicians with no certification requirement, some require national certification outright, some run a trainee tier with an expiration that cannot be extended, and a few barely regulate the role. Know your own state's rule before you score this answer, because a candidate can be perfectly credentialed one state over and still unable to work for you on Monday. A lapsed credential is not automatically a no. A candidate who tells you it lapsed, says why, and names the date they expect it back is giving you something more useful than a vague yes. Be cautious with it is all current and no dates, with a candidate who does not know which state their registration is in, and with a registration described as in process, which can mean two weeks or a reinstatement measured in months. Verify the certification and the state registration yourself for every candidate before an offer, every time.

The queue is deep and there is a line at the drop-off window. What do you do on every single fill to keep from making an error, and have you worked anywhere that tracked your error or verification rate?

What this assesses: This question predicts the cost of a bad hire better than any other here, because a tech's errors land on the pharmacist's license and on a patient. Strong answers describe habits rather than intentions. They check the NDC against the stock bottle and the hard copy, not just the label. They name look-alike and sound-alike pairs they deliberately slow down for, and a tech from a pharmacy with a real safety culture will say tall-man lettering without being prompted. They flag anything ambiguous for the pharmacist instead of interpreting it themselves. The best answers mention what they do when interrupted mid-fill, which is where most errors are actually born. Strong answers also treat being measured as normal. A candidate who says their store tracked verification rejections and knows roughly where theirs ran is telling you they have been held to a number and survived it. Be cautious with three answers in particular. I have never made a mistake is either untrue or means nobody was checking. Calling accuracy metrics unfair tells you exactly how they will react the first time yours flags them. And an answer that amounts to working faster when the line gets long, with no mention of what they hold constant, is a near-miss waiting to happen on your shift. If the answer stays abstract, ask what their last near-miss was and what they did about it.

Walk me through exactly what you do with a third-party rejection at the window. Pick a real one you have handled: refill too soon, prior authorization required, NDC not covered, a quantity limit, or a DUR reject.

What this assesses: At a retail counter this single skill decides whether a tech is productive or whether the pharmacist ends up doing billing between verifications. Strong answers are procedural and specific. They read the reject code rather than guessing at it, name the actual fix for the example they picked, and show more than one path: run the prior authorization through the plan portal or a service like CoverMyMeds, switch to a covered NDC or a formulary alternative and get the prescriber to sign off, check whether the days-supply math is the real problem, call the help desk when the code is not what it appears to be. The best answers keep the patient in the story. They say what they tell the person at the window, what the wait actually looks like, and what the cash price is if the plan is not going to pay, without letting it turn into an argument. Be cautious with a candidate whose only move is to tell the patient it is not covered and hand the bag back, with one who has done nothing but fill and count and has never seen a reject, and with one who describes overriding rejections but cannot explain what the override did. Score this against the job you are filling rather than against a general idea of a good tech. Retail-only experience is a real gap for a hospital role, and billing-free experience is a real gap for retail.

What is your experience with controlled substances: perpetual inventory, counts, discrepancy resolution, CII ordering or receiving, secure storage, witnessed waste? Have you ever found a count that did not balance, and what happened next? Are you comfortable with the background check and drug screen this role requires?

What this assesses: The middle part of this question is the one that matters. Any candidate can say they are careful with controls. Strong answers describe a real discrepancy and the process that followed: recount, pull the dispensing log and the cabinet report against what was actually removed, look for an unrecorded waste or a mis-keyed quantity, and tell the pharmacist in charge the same day rather than trying to make it balance alone. That last part is the whole signal. A tech who quietly adjusts a count to close a gap is a serious liability, and a tech who escalates a two-tablet variance immediately is exactly who you want on your cabinet. Strong answers also show familiarity with the mechanics of the setting they worked in, whether that is a perpetual inventory log, a biennial inventory, witnessed waste with a second signature, or automated cabinet discrepancy reports. Be cautious with a candidate who is vague about how counts work at all, who treats controlled-substance rules as paperwork rather than law, or who has a clean description of the process but has never been the person who found a problem. On the clearance half, a straight yes is what you expect. Hesitation is not automatically disqualifying, and it is something you want surfaced now rather than two weeks into onboarding with a start date already promised to a hiring manager.

Which pharmacy systems and automation have you actually worked on: the pharmacy management or dispensing system, automated cabinets like Pyxis or Omnicell, a pouch or blister packager, IV workflow software, e-prescribing? Which one do you know well enough to train someone else on?

What this assesses: The training-someone-else half is doing the work here, because it separates having seen a system from knowing it. Strong answers name specific platforms and are honest about depth: fluent in one pharmacy management system including the parts most techs avoid, such as inventory ordering, cycle counts, or pulling reports, plus passing familiarity with another. They describe automation by what it did for them rather than by brand name alone. A tech who has really restocked a cabinet will mention stockouts and discrepancy reports. A tech who has run a pouch packager will mention jams and canister changes. What you are actually measuring is ramp time. Someone who has learned two or three systems across different employers will be productive on yours within a week or two. Someone who has used exactly one platform for eight years may still be an excellent tech, but plan for a slower start and tell the hiring manager that rather than being surprised by it in month one. Be cautious with a candidate who cannot name a single system, with one who lists six at identical claimed expertise, and with one whose entire system experience is a register and a label printer. None of that has to be a dealbreaker. It is the difference between a hire who is useful in week one and a hire who is useful in month two, and you should know which one you are making before you sign the offer.

Tell me about a time a patient asked you something you were not allowed to answer. What did you say, and how did you hand it off? Separately, tell me about the angriest patient you have dealt with at the window and how it ended.

What this assesses: A technician who gives clinical advice is a liability that no amount of speed makes up for, and this is the cheapest way to test that line. Strong answers are matter-of-fact about the boundary. They tell the patient the pharmacist needs to answer that, and then they actually walk it over instead of leaving the person standing there waiting. They also understand the line is wider than dosing advice: whether two medications interact, whether a side effect is normal, whether to keep taking something, all of it goes to the pharmacist. The best answers show they can hand off without making the patient feel brushed aside. On the angry-patient half, listen for what they could and could not fix. Strong answers name the real causes, which are almost always a prescription that is not ready, an insurance problem, a drug on backorder, or a wait time someone quoted too optimistically, and they describe staying flat and factual while fixing whatever was fixable. They do not pretend every interaction ended well. Be cautious with a candidate who cannot recall one difficult interaction in a job that is mostly a counter, with one who answers a clinical question inside their own example and does not notice the problem, and with one whose story is about winning the argument. The hospital version of this is quieter and still real: a tech who cannot say I do not know to a nurse will guess, and guessing on a floor is worse than guessing at a window.

Tell me about a time you thought something was wrong and the person who could fix it was busy, senior to you, or certain they were right. What did you do?

What this assesses: Everything above tells you what a tech does when the system works. This tells you what they do when speaking up costs them something, which is the shift where errors actually reach patients. Strong answers name a real instance with a real cost attached: a hard copy that did not match what was keyed and a pharmacist three verifications deep who did not want to be interrupted, a prescriber's office insisting a dose was correct, a lead tech who said to just fill it and move on. Then they describe what they did, and in a good answer it is almost always the same shape. They stopped the fill instead of continuing while they worked it out. They asked rather than accused. They took it to the pharmacist in charge when the first answer did not resolve it. Strong answers often include the times they turned out to be wrong, and that is a feature. A tech who says they have raised something twice and been mistaken once is describing a person who still raises things. Be cautious with a candidate who cannot produce an example at all, because in a busy pharmacy that usually means they let things go rather than that nothing ever came up. Be more cautious with an answer where the resolution was to fill it anyway because someone senior said so. And watch for the opposite failure: a candidate whose story is mostly about being right while everyone around them was incompetent will escalate everything and spend your pharmacist's attention on nothing.

What shifts can you actually work: days, evenings, overnights, weekends, rotating, holidays? Are you open to overtime when someone calls out, how soon could you start, and how are you getting to the site?

What this assesses: Availability is the most common reason a pharmacy hire falls apart in month two, and it costs nothing to find out now. Retail runs twelve-hour days, weekends, and holidays. Hospital pharmacies staff around the clock and somebody works Christmas. Long-term care runs early-morning cycle fills. Strong answers are specific and include a constraint, because a real schedule has one. Every weekday, every other Saturday, no overnights because of a childcare arrangement is both usable and credible. Strong answers also give a real start date and name a notice period they intend to honor, which is a small signal about how they will eventually leave you. Be cautious with whatever you need, which is the answer that collapses the first time a mandatory Saturday or a 9 PM close lands on the schedule. Ask the follow-up directly: what is the one shift you would turn down. Transportation matters more than it sounds for this role, because pharmacies open before transit gets going and close after it thins out, and a tech with no reliable ride to a site that is not on a bus line becomes a call-out problem by week three. None of this is a character test. You are matching a real schedule to a real life, and a candidate who names a hard constraint now is saving you a vacancy later.