What the work involves
Each assignment is a closed case packet: an alert with supporting KYC/CDD profile and transaction history, an onboarding file with source documents, a batch of screening hits, or a queue of flagged communications and trade records. You read the packet, reach a defensible conclusion, and write the analyst deliverable — a disposition memo with a SAR narrative where the facts warrant one, a discrepancy and remediation list, an ownership chart resolving layered entities against 10% and 25% UBO thresholds, or a true-match / false-positive / escalate call with a short rationale attached to each hit. Client-style outputs always end as drafts. Reviewers grade against a rubric that weights whether your reasoning is traceable to the record, not whether you reached a popular answer.
What the platform screens for
Mercor's screen is AI-led and pushes on specifics. Expect follow-ups asking which typology a scenario matches, what you'd escalate versus close and why, how you'd word the "who, what, when, where, why, how" of a narrative, and where an OFAC hit stops being a fuzzy-name artifact. Vague framework name-dropping reads poorly; describing the alert volumes you handled, the systems you dispositioned in, and a call you made that a QA reviewer or examiner pushed back on reads well. Written clarity matters as much as domain knowledge — the deliverable is the product.
Logistics
- Contract, hourly, remote, US-based.
- Roughly 15 hours per week, largely asynchronous; you pick up case packets from a queue rather than sitting in scheduled shifts.
- Observed pay band is $75–100/hr, set by experience and assessment performance. Bands are as reported, not guaranteed.
- Entry is a timed exercise: one mock alert packet (disposition plus SAR narrative), one KYC packet (discrepancy and remediation list), and a batch of sanctions hits to adjudicate with rationales.