Coding Supervisor Recruiters

What do we check before you see anyone?

Coding scope: Ask, “Which inpatient, outpatient, or professional services have you supervised?” Useful answers identify encounter types, coding systems, and hands-on review duties. A broad job title alone does not establish a match. Work assignment: Ask, “How would you assign accounts when absences and difficult cases occur together?”

• Look for attention to coder experience, aging accounts, and available reviewers rather than distributing work solely by account count.
• Audit follow-through: Ask, “Describe how you turned recurring audit findings into coaching.” Strong answers explain the error pattern, reference used, feedback given, and later review of similar cases.
• Escalation judgment: Ask, “What would you do with conflicting documentation before releasing a coded account?” Listen for clear escalation routes and a record of the unresolved issue, not unsupported assumptions.
• Team supervision: Ask, “How have you handled repeated errors after coaching?” Useful evidence includes documented examples, a specific improvement plan, follow-up reviews, and appropriate involvement of management or human resources.
• Credentials and tools: Ask which coding credentials they hold and which encoders, records systems, and reporting tools they have used. Verify credential status separately. Treat preferred certifications as selection criteria, not universal legal mandates.

Which mistakes stall the search?

A common mistake is hiring on production results alone. Fast, accurate coding does not show whether someone can explain an error, resolve disagreement, or hold a consistent review standard. Another is leaving audit ownership unclear. State who selects cases, interprets findings, delivers feedback, and approves corrective action before interviewing.