What the work involves

You receive coding scenarios — operative notes, discharge summaries, office visit documentation, sometimes full inpatient encounters — alongside an AI system's proposed code assignment. Your job is to judge whether the assignment is defensible under Official Coding Guidelines, and to explain why in writing that a model can learn from. That means naming the specific guideline, coding clinic reference, or payer rule that governs the decision, not just marking an answer wrong.

Typical tasks include: auditing profee E/M leveling and modifier use, checking principal diagnosis selection and MS-DRG assignment, flagging unsupported code capture or missed CC/MCC opportunities, comparing two AI outputs and ranking them, and writing corrected assignments with rationale. Some projects ask you to author new test cases from de-identified documentation patterns you know cause coders to stumble.

What the screen looks for

  • Credential and depth verification. CCS, CPC, RHIA, or RHIT plus a leadership record; expect follow-ups that go past the resume into how you actually ran audits and what your error-rate methodology was.
  • Judgment under ambiguity. Many coding questions have a defensible range rather than one answer. Reviewers who can articulate why a code is arguably correct but not optimally supported score better than reviewers who only mark binary right/wrong.
  • Written precision. Rationales are the deliverable. Vague feedback like "documentation insufficient" fails; "documentation supports acute respiratory failure but lacks the linkage language required to sequence it as principal per Guideline II.C" passes.
  • Resistance to plausible-sounding errors. AI coding output is often confidently wrong in ways that read fluent. The screen probes whether you catch that.

Logistics

Fully remote and asynchronous. Work is drawn from a queue, and most contributors run 10–20 hours a week, though throughput expectations vary by project phase. Pay is stated as $80/hr observed for this listing — Mercor sets rates per project and per contributor, so treat it as a reference point, not a guarantee. Onboarding runs through Mercor's AI-led interview plus credential verification; project assignment follows separately and is not automatic after a passing screen.