What should you ask a dental insurance coordinator in an interview? Questions and what good answers sound like
What to ask, the answers that signal real claims experience, the red flags, and the practical task that settles the rest.
Most of this job is testable: the work you are hiring for is CDT coding, benefit verification, denial follow-up and clean posting, and a good interview makes a candidate prove all four.
The questions below are grouped by skill, with notes on what a strong answer sounds like.
Pair them with a short practical task on your own practice management system, and the hiring decision stops being a gamble on a résumé.
Before the interview
Write the role before you write the questions.
"Insurance coordinator" and "billing coordinator" are not standardized titles — the BLS has neither title, and no standard source we found defines the difference — so two candidates with the same title may have done entirely different jobs.
List the duties you need covered, weight them, and aim your questions at the heaviest ones; if the opening is mostly claims production rather than patient-facing verification, our dental billing coordinator interview questions may fit better.
The process around the conversation is in our guide to how to hire a dental insurance coordinator, and the posting wording is in the job description.
There is no license to look up the way there is for a hygienist — our research found none for this desk, and one state board says the point outright: the Nevada State Board of Dental Examiners says it has no jurisdiction over dental office personnel such as receptionists and billers/coders.
What you verify up front is work history: practices, systems, the kind of claims handled.
That is what your reference calls are for; the interview is for competence.
Know your own numbers before the hour starts: claims per week, top payers, the denial reasons that recur, how verifications get done today.
You don't have to share them, but you cannot judge a candidate's answers without them.
Plan the practical task now, not on the day.
No source we found describes a standard practical test for this role, so the task is your design: a sample EOB to work, a verification call to role-play, or a sandbox in your practice management system.
EEOC's ADA regulations expressly let you ask an applicant, before an offer, to describe or demonstrate how they would perform job-related functions — that is exactly what the task is.
If you go further and run a working interview where the candidate performs real work, pay them for the time: in 2018 the U.S. Department of Labor found a Nashville dental practice violated federal minimum wage requirements by requiring candidates to complete an unpaid working interview, and the FLSA test is whether the person was suffered or permitted to work — not what you called the session or how short it was.
Our guides to running a working interview and skills assessments cover the mechanics.
Technical questions: CDT coding, software and the ledger
Walk me through the last CDT code dispute you had with a payer — what was billed, what the payer said, and how it ended.
What to listen for: A specific story with a beginning and an end: the procedure, the payer's objection, the resolution.
Someone who has worked claims narrates the back-and-forth; someone reciting a course describes the concept.
If the story feels secondhand, ask when it happened.
How often does the CDT code set change, and what did you do the last time it did?
What to listen for: An annual cycle tied to the calendar year — each CDT edition is effective January 1 through December 31; CDT 2027 runs January 1, 2027 through December 31, 2027.
Strong candidates describe a January routine: loading the new edition, updating defaults, rechecking the codes they use most.
No routine means their coding knowledge quietly ages every year.
A claim comes back unpaid because the payer doesn't recognize the procedure code as a dental code. What happened, and what do you do?
What to listen for: They recognize a code-set problem: dental claims are billed with CDT, the Code on Dental Procedures and Nomenclature, maintained by the ADA and the standard code set for dental services under HIPAA's code-set rules.
The fix is rebilling with the right CDT code, not arguing with the payer.
Which practice management systems have you worked in — Dentrix, Eaglesoft, Open Dental, something else — and what did you actually do in each?
What to listen for: Tasks, not logos: posting, claim creation, working rejections, the ledger, treatment plans.
Follow up with a screen-level question — where do you resubmit a denied claim in that system?
A vague answer suggests the résumé outgrew the person.
Switching systems is learnable; not knowing the claim cycle is not.
An EOB pays differently from what you expected. Step by step, what happens before you post it?
What to listen for: Compare the payment and adjustment lines against the plan's rules, look for downgrades or frequency limits, work out the true patient portion, and document the reason code.
The dangerous answer is posting blindly — the ledger then lies to everyone who touches the account afterward.
What does a clean ledger look like to you, and how have you handled inheriting a messy one?
What to listen for: Unambiguous habits: every adjustment coded with a reason, refunds documented, no balance moved without a note.
For inherited accounts, a method — one provider or date range at a time, reconciled against EOBs, errors fixed forward rather than buried.
Ledger indifference in an interview becomes unreconcilable books a year later.
Verification and denial-handling questions
A patient is about to start a large treatment plan. What exactly do you verify, and what do you write down?
What to listen for: Eligibility, remaining maximum, deductible status, waiting periods, frequencies, downgrades, alternate-benefit and missing-tooth clauses, coordination of benefits — captured in writing, dated, and attached to the account so anyone can quote the patient without calling again.
A verification that lives only in their head dies on their day off.
How did you balance verification speed against accuracy in your last role?
What to listen for: A method rather than a temperament: batching, deadlines tied to the schedule — verified before the appointment, not the morning of — and double-checks on high-dollar plans.
Be wary of candidates who volunteer that they are simply fast.
Speed here is a byproduct of a repeatable process, and the errors speed creates are expensive.
Tell me about a denial you appealed and won. What was the reason, and what did your appeal include?
What to listen for: A cause — coding, documentation, frequency, eligibility — plus the evidence attached: narratives, radiographs, chart notes, and the submission path.
"They eventually paid it" with no mechanism is a coin-flip story.
If they have never won one, ask whether they have ever written one; never appealing usually means never following up.
How do you find out which denial reasons repeat in a practice, and what do you do about them?
What to listen for: Tracking by payer and reason, then fixing causes upstream: stronger narratives at treatment planning, cleaner chart notes, scheduling rules, patient conversations about non-covered services.
Someone who reworks each denial one at a time is doing the job; someone who kills the pattern is doing it well.
When would you ask the doctor to request a pre-treatment estimate, and when is it a waste of the patient's time?
What to listen for: Judgment: large or multi-phase plans, coverage with frequency or alternate-benefit risk, anything unusual.
Strong answers name the tradeoff — wait time against certainty — and know the practice owns the financial conversation either way, with or without the payer's opinion.
Scope, license and compliance questions
A family member calls and asks what insurance paid and what the patient still owes. How do you handle the call?
What to listen for: Confirms who is authorized on the account before disclosing anything, and offers a callback while checking.
Strong candidates describe their practice's authorization process and treat "but I'm their daughter" as a reason to verify, not a pass.
Casual disclosure of account details is how HIPAA incidents start.
A patient asks the practice to waive their copay because money is tight. What do you do?
What to listen for: They know the practice cannot quietly absorb it: under the ADA's Code of Ethics (Section 5.B.1), a dentist who accepts an insurer's payment as payment in full without disclosing that the patient's portion will not be collected is engaged in overbilling.
Strong answers offer legitimate routes — a payment plan, or disclosure to the insurer that the patient's portion is not being collected — and never just zero the copay out.
Where is the line between what you can decide on an account and what you escalate? Give me an example from your last role.
What to listen for: A concrete boundary — write-off limits, refund approvals, payment-plan caps — and comfort operating inside it.
Someone who "just fixes things" without authority creates ledger chaos nobody can audit; someone who escalates everything becomes the bottleneck.
You want a line, and examples of respecting it.
If part of this role could be done from home, how would you keep patient information secure?
What to listen for: A practice-issued machine or locked-down access, no printing at home, no family members at the screen, and awareness that a remote employee still falls under HIPAA's definition of workforce — employees, volunteers, trainees and others whose conduct the practice directly controls — so calling the arrangement remote does not make them a business associate.
Anyone who treats "remote" as "off the record" is describing your next breach.
Have you worked alongside an outside billing service or clearinghouse? How did you divide the work?
What to listen for: Real experience with the handoff: who enters, who submits, who works rejections, who answers patient questions.
A plus: knowing that an outside company processing your claims is a business associate under HIPAA — claims processing and billing are the activities HHS names — not part of your workforce.
Team and patient questions
A patient is at the desk, upset: the EOB paid less than your estimate and they were told they'd owe nothing. What do you say?
What to listen for: Owns it without blaming the patient or the payer — pulls the verification notes, explains what changed in plain language, puts the balance in writing, offers next steps.
Then fixes the cause so estimates get quoted tighter.
Blaming "the insurance" signals the same call recurring every week.
The doctor changes the treatment plan chairside and the patient books before the new procedures are verified. What do you do?
What to listen for: Re-verification becomes an immediate task with a deadline before the appointment, the patient is told honestly that a final figure follows, and the change is documented.
The failure mode is letting the original verification ride — the patient then hears a number the plan never promised.
Tell me about a time you had to tell a clinician their chart notes wouldn't support the claim. How did it go?
What to listen for: Directness without drama: specific about what was missing, framed as protecting the practice and the patient, aimed at the pattern rather than the person.
A coordinator who cannot push back on clinical staff writes claims that fail quietly — until an audit finds them.
How do you keep information flowing from the clinical team so claims go out clean — and what do you do with a charge slip you can't decipher?
What to listen for: A defined intake: a standard slip, a checklist, a huddle — plus the habit of going back to the source instead of guessing a code.
"I figure out what they meant" is how a practice ends up refunding patients and rebilling payers.
A patient is at the counter, the payer phone line finally answers, and a claim batch has to go out today. What order, and why?
What to listen for: The patient in front of them first, a callback time for the payer, the batch anchored to a fixed slot.
Listen for the reasoning: live patients damage the practice's reputation fastest, and deadlines get handled with structure rather than panic.
Candidates who describe triage have done the job.
Red flags
None of these is automatically a no, and each deserves a follow-up question before you decide.
But weight them heavily for this role: a coordinator sits between your production and your payment, and a 2007 ADA study found 17.5% of surveyed dentists were aware their primary practice had been embezzled.
- Speaks in generalities about coding, payers and denials, with no specific story they can date or name.
- Vague about which practice management systems they have actually worked in and what they did in each — or treats the ledger as someone else's problem.
- Willing to make codes fit coverage when a claim denies; that instinct is the one this interview exists to catch.
- Casual with patient information — no verification step before discussing an account with a caller.
- Years of claims work with no appeal written, followed up or won.
- No story about catching their own mistake and what they did next.
After the interview
Score while it is fresh.
Rate the same dimensions for every candidate so two interviews a week apart are comparable: coding and systems, verification discipline, denial handling, compliance judgment, and patient and team communication.
Mark each strong, mixed or weak, and write one line of evidence under it — a rubric without notes is just a mood.
Strong technical with weak compliance is a coaching problem; strong compliance with weak technical is a training plan; weak on both is a no. Note what the rubric cannot hold, too: a candidate who asked about your payers, your denial patterns and your software has told you they have run this function before.
Then finish the checks you started: make the reference checks do real work — ask the former supervisor what the claims backlog looked like when this person left, and whether they would put them near the ledger again.
Also run the hire through the Office of Inspector General's List of Excluded Individuals and Entities (LEIE) before the first day: OIG advises health care entities to routinely check the list so new hires and current employees are not on it, and the exclusion payment ban reaches administrative and management services payable by federal health care programs even when they are not separately billable.
For a role whose job is billing, that check is not a formality.
Hiring an insurance coordinator?
Post the role on DentistryHires and reach dental office staff looking for their next position.