Mercor Work Trial: What It Is, How It Is Paid, and What Happens After

A work trial is the part of Mercor's hiring path that its documentation covers in a few paragraphs and that contributors ask about more than almost anything else: whether it is paid, how long it takes, whether you can retake it, and what passing gets you. This guide puts Mercor's published rules in one place, with the page each rule comes from, and sets a first-hand account of a project's own trial next to them. Where the two differ, the guide says so rather than averaging them. It applies to AI evaluation, AI training and data annotation work alike; the trial format follows the project, not the job title.

The short version

• There are two kinds of trial. The documented one is a take-home assessment before an offer; the other is a project's own test after the offer is signed, which Mercor's pages do not describe and this guide knows first-hand. Which one you have depends on where it arrived: the Offers tab before any contract, or a project channel after signing.
• It is paid, and the payment does not depend on the result. Mercor describes the work trial as a paid assessment, paid through Stripe after review: one to two weeks by its support page, up to 14 business days plus the bank transfer by its work trial page. Low-effort or incomplete work can go unpaid.
• The documented trial is one per person, before an offer, about four to six hours, over up to fourteen days. You can do it in several sittings and save as you go.
• The project's own trial, first-hand: around two hours, proctored, built on the project's guideline, with a pass threshold between 70% and 80% and, on some projects, one retake.
• Passing guarantees nothing on the documented trial and no feedback is given. On the project trial, first-hand, a pass email came within hours and opened the work.
• Every trial tests the same four skills: following the guideline, attention to detail, reasoning, and a written justification.

Which trial do you have?

Mercor's documentation describes a single thing it calls the work trial: "an assessment instrument employed to evaluate candidates prior to extending an offer", as distinct from the contract offer that "formalizes the employment relationship between you and Mercor's clients" (work trial page, read 5 November 2026). It arrives in the Offers tab or under Important Tasks, comes with a fourteen-day window, and is one-time: "each talent is eligible for only one work trial, regardless of the number of offers received", and only "the project lead who issued the offer has the authority to reassign a new one if necessary".

First-hand, there is a second thing that goes by the same name. Our founder, Mo Zohourian, has worked on more than 15 Mercor contracts, and on some projects a trial came after the offer was signed, run by the project itself: shorter, proctored, scored against a threshold, and paid in the project's normal cycle. Mercor's pages do not describe that version, so this guide treats it as one project's experience, not a platform rule, and marks it first-hand throughout.

The tell is where it sits. A trial in your Offers tab before any contract, with a trial end date two weeks out, is the documented one. A trial announced in a project's onboarding channel after you have signed, with a session to book and a camera check, is the project's own. If you are unsure, ask in that channel before the clock starts.

The documented trial, step by step

Mercor's own rules, read on 5 November 2026, in the order you meet them.

1. The offer. "Offers will appear in the Offers tab or under the Important Tasks section", with an email from Mercor. The support page's test for legitimacy is exactly that: "if it appears in your Offers tab and you received an email from Mercor, it is valid" (project and onboarding FAQ). Mercor "never requests or requires any payment or fee from talents" (time tracking and pay policies). Accept it before it expires.
2. The checklist before the task opens. The trial does not start until a short list on the offer panel is done: sign the Terms of Work, sign the Confidential Information and Inventions Assignment Agreement, acknowledge Mercor's payout policies, set up payments (ID verification and bank details; the name must match your ID), complete work authorization where the trial requires it, and sign the trial's own offer letter. Do this the day the offer arrives, because the fourteen days run from acceptance.
3. The window. "The duration is fourteen days from the date of acceptance, with the option to complete the task in segments." "A typical work trial requires approximately four to six hours", and "the majority of individuals complete it within a total of three to five hours". You "may perform your work trial across multiple shifts"; progress "can be saved incrementally and submitted at a later time, provided that the final deadline is met". The trial end date in your dashboard is that deadline. Mercor's documentation says nothing about time tracking during a trial, and its referrals page calls work trials "deliverable-based trials" (referrals page); on that wording, what is judged and paid is the submission rather than logged hours.
4. The review. "A work trial does not guarantee a contract offer. Following submission, a work trial may be either rejected or accepted based on the quality of your responses." No feedback: "regrettably, we are unable to provide personalized feedback due to high volume."
5. The payment. "Payment does not depend on whether you are selected for the role", only on "a complete, good-faith submission"; trials with assessments "show a banner noting that Mercor can withhold payment for low-effort or incomplete work". Review and payment "shall be completed within a period of one to two weeks"; the work trial page says payment "is typically processed within 14 business days" after review, then "3 to 7 business days" for the funds to arrive. It is paid through Stripe, with Wise "employed solely in cases where Stripe is not supported", and "your initial Stripe payout is subject to a seven-day hold in accordance with Stripe's policy".

Read together, that is the shape of it: a take-home deliverable with a fixed payment, a two-week window to do it in, a quality review you will not hear the reasons for, and a contract that may or may not follow.

A project's own trial, first-hand

What follows is one project's version, and the details vary from project to project.

After the offer was signed, the project added new contributors to a general onboarding channel on Slack, where questions about the onboarding and the trial could be asked. The trial itself was a proctored, time-limited task: screen recording, webcam and microphone on, and a technical check that each of them worked before the task opened. It ran around two hours. It was built on the project's own guideline, which was not shared beforehand; the guideline was part of the trial.

Projects set a pass threshold somewhere between 70% and 80%, and some allow one retake at a higher threshold. Unlike the documented trial, whose payment does not depend on the result, this one was paid either way in the next weekly payment cycle through Stripe, with almost double the amount for a pass. A pass or fail email arrived within a couple of hours. A pass opened the project's task channels. Whether tasks were available at once depended on the project's stage: on a project that was already running they were, with a weekly hour cap that started low and rose with quality.

Two things about the time limit. It did not feel tight, and the design seemed to leave room to think; but someone who is too slow is filtered out, so the limit is real.

What a work trial tests

The content follows the project's core skill. A rubric-focused project tests rubric writing; a coding project tests code; a language project tests the language. Underneath that, first-hand, every trial tests the same four things, because every trial hands you a guideline and judges how you apply it:

1. Following the guideline exactly. The instructions are the test. A correct answer that breaks a stated rule is a wrong answer.
2. Attention to detail. Guidelines carry nuances, and the task is to notice which ones apply to the case in front of you.
3. Reasoning and inference. Many cases are not covered word for word; you have to work out what the guideline implies.
4. A written justification. Each decision has to be explained in the guideline's own terms, so a reviewer can see why, not only what.

Mercor's documentation adds the frame: the submission is judged on "the quality of your responses", and low-effort or incomplete work can go unpaid. A trial is passed on the submission, not on credentials; those four skills, reading a guideline closely, applying it to cases it does not spell out, and writing the justification, are what the AI Evaluator Certification teaches and examines, and no platform requires one.

How to prepare

• Keep the guideline open and check it as you go. There is not enough time to memorise every detail, and the detail is what is being tested.
• Clear the checklist on day one (documents, payout policy, payments and ID verification), so the fourteen days are for the task, not the paperwork.
• Test the camera, microphone and screen recording before the day if the trial is proctored; the technical check happens before the clock starts, but a failing setup costs a retake you may not have.
• Read the whole guideline once before the first task, then work case by case, going back to the relevant rule each time.
• Write the justification you would want to read: the rule, the fact in the case that triggers it, the decision.
• Do not rush, and do not stall. First-hand, the time limit left room to think; being too slow is what gets filtered.
• Submit before the trial end date. An expired trial is not reopened, and a half-finished one can go unpaid.

After you submit, and if something goes wrong

On the documented trial, the submission is reviewed, accepted or rejected, and paid after review (one to two weeks by Mercor's support page, up to 14 business days plus the transfer by its work trial page); no feedback follows, and acceptance does not itself produce a contract. On the project trial, first-hand, the result came by email within a couple of hours, a pass opened the task channels, and the weekly cap grew with quality from there. If a trial is not passed and the project allows a retake, the second attempt is held to a higher threshold.

If the payment has not shown after the documented window, Mercor's support page points to support@mercor.com and to your project's Slack channel; two documented causes of a late first payment are the seven-day Stripe hold and bank details that do not match the verified name, which Mercor's payments page says can take ten to fifteen business days to resolve (payments page). If the trial sits unreviewed, the same two channels are the route; only the project lead who issued the trial can reassign one.

For the steps around the trial, the Mercor interview preparation guide covers the AI interview that precedes most offers, Mercor instant work offers explains offers that arrive for roles you never applied to, and our Mercor review covers pay, screen tracking and the offboarding risk once you are on a project. Live Mercor roles with their published rates are on our Mercor jobs page.

Help us keep this current

If your trial worked differently, tell us roughly when and on what kind of project, and we will update this guide and note what changed. Mercor is welcome to respond, and any correction it sends will be published here with the date.

Sources: Mercor's talent documentation (work trial, project and onboarding support, time tracking and pay policies, referrals), read 5 November 2026; first-hand experience of a project-run trial, given by the founder on 5 November 2026. Last verified 5 November 2026.