What the work involves

The day-to-day splits three ways, and most contributors do some of each. You author engineering problems drawn from systems you actually shipped — the requirements, the constraints that made it hard, the failure modes a naive implementation walks into — along with the reference answer a model's attempt gets graded against. You grade model-written code and design docs: does it handle the edge cases, is the complexity earned, does the test exercise the behaviour it claims to cover. And you flag the class of output that passes code review cleanly but falls over in production — under concurrency, at scale, when the downstream service is slow instead of down, or when the operating cost turns out to be the real constraint.

Most of the value is in the written reasoning, not the verdict. A rating with no explanation of why the retry loop amplifies load under partial failure is close to useless to the research team reading it.

What the platform screens for

Mercor verifies your background and runs a roughly 20-minute AI interview. It's looking for evidence you've owned code in production and dealt with the consequences — incidents, migrations, performance work, on-call — rather than credentials or coursework. Expect follow-ups that push on specifics: which service, what the traffic looked like, what you changed and what broke anyway. Vague seniority claims don't survive the second question. The pool spans frontend (React, TypeScript, Next.js), backend (Java, Go, Node.js), full-stack, mobile, embedded and IoT, DevOps and platform, systems and performance, QA and automation, and security engineering.

Logistics and honest expectations

  • This is a standing pool listing, not a job opening. It does not accept or reject you; there's no decision to wait for.
  • Remote and asynchronous. Project work is typically part-time and fits around other commitments.
  • Rates on Mercor software engineering listings have posted at $70–150/hr, set per project by scope and depth. The named rate, hours, and client appear on the specific project listing, and the hiring decision happens there.
  • Match timing is genuinely unpredictable — anywhere from a week to several months, depending on what clients are running. Completing the domain expert interview and joining every network you qualify for improves your odds.