The work
Quality Analysts sit downstream of the people producing data — annotators, writers, evaluators, subject-matter contributors — and decide whether what they produced actually meets the standard. Day to day that means pulling a sample or a queue of work product, scoring it against a rubric, and writing up what failed and why in language the contributor can act on. Rejections that say "low quality" are worthless; rejections that cite the clause of the guideline breached and the specific span of text that breached it are the job.
The second half of the role is upstream. When the same error keeps appearing across ten contributors, that is usually a guideline defect, not ten separate performance problems. You are expected to notice that pattern, quantify it, and propose the checklist change or rubric clarification that closes it. Projects change shape mid-flight — rubrics get revised, edge cases get reclassified — and analysts who need a settled spec before they can work will struggle.
What the screen looks for
Mercor's screening is AI-led and conversational, and it pushes on specifics. Expect to be asked for a real quality standard you have worked against, how you handled a call that sat between two rubric categories, and what you did when you disagreed with the guideline itself. Vague claims about being detail-oriented get followed up until they either produce an example or collapse. A relevant domain — technical, editorial, medical, legal, analytical — helps, because review work is usually matched to the subject matter of the project.
Logistics
- Contract, hourly, fully remote; no fixed office hours
- Async collaboration across time zones — written handoffs, not standups
- Volume varies by project; some weeks are steady queues, others are burst work
- Requires stable internet and a quiet workspace for focused review sessions
- Pay observed in the $20–50/hr range, set by project and demonstrated domain depth; not guaranteed