What is clawded.ai?

World Model (world-model.xyz) is launching a job-matching tool for remote AI data work. It matches paid subscribers to verified openings across AI training platforms such as Mercor, Handshake AI, micro1 and Toloka.

Subscribe now

A paid subscriber, a biology PhD in California, wrote to me last month with a problem I keep hearing in different forms. One platform removed their account the moment they confirmed they live in California. Another offer was gone by the time they applied. Their question: which platforms still accept California contractors, and are there any W-2 tracks?

They’re not alone. Of the 10 paid subscribers I currently match jobs for, 6 have hit a wall that had nothing to do with their skills and everything to do with where they live. One is outside the US and can’t get through a platform’s identity check from his location; VPNs are blocked too. One is a French national authorized to work only in the EU. Two are in California. Two are in the UK.

So I went back through every role I track. On October 1 that was 2,384 open roles across 27 platforms, each confirmed live at the source, and I sorted them by who is actually allowed to apply.

Here’s the first finding, free. (Mercor links in this post are my referral links; you pay nothing extra.)

There is a W-2 track, and it’s the cleanest answer for Californians. Mercor currently lists 9 roles that are W-2 employment through Cincinnatus LLC, not independent contracting. Because you’re an employee, the contractor restrictions that keep pushing California residents out don’t apply the same way. The one I’d look at first if you’re a life scientist:

Mercor — Molecular Biology Experts (US)
$70–105/hr · Remote, US only · W-2 employee, 20+ hours a week
A leading AI lab needs PhD molecular biologists to design and review tasks on primers, plasmids, guide RNAs and repair templates.
Strong fit if: you’ve done hands-on cloning or CRISPR construct design and can show it.
➤ https://work.mercor.com/jobs/list_AAABoJEZsx-GA2FkHqpMwZV9
Confirmed live 10/1

Below the paywall:

• The eligibility map: 15 platforms sorted by US-only, worldwide, UK, EU and Asia, plus how many listings never say where you can work from

• All 9 W-2 roles, with pay and where each is open (one is UK-only, one is open in the UK, US and Canada)

• The California and “strict-state” problem: which platforms exclude California, and the one listing that also excludes New Jersey, Massachusetts, Connecticut and Vermont

• If you’re outside the US: the two platforms where every role I track is open internationally or worldwide

• Identity checks: how they block people, and what to check before you spend hours on an assessment

• A 5-minute eligibility checklist to run before you apply anywhere

• What to do this week, whether you’re in California, outside the US, or EU/UK-only

Read more

The experts are busy with the big picture this month. Goldman Sachs put out a full conversation on how AI is affecting GDP growth, productivity and jobs. Its estimate for AI’s current net contribution to measured US GDP growth is about 0.1 percentage point.

It’s all macro. None of us can hide from it, and none of it tells you what to do on Monday.

Paul Millerd asked the personal version in July: will you train the models for pay? He doubted many people would want work whose only reader is a model.

My inbox says plenty of you do. On a personal level the question is simple. You can get paid to train models. I have been, on more than ten Mercor projects, as a contributor and as a reviewer.

Today I’m launching the tool I wish I’d had for that work. It’s called clawded.ai.

What’s different about remote work this time?

Remote work is old. Fiverr has sold gigs since 2010, and Upwork’s predecessors go back to the late 1990s.

My friend SH is an illustrator in China. On Fiverr, she drew the wedding illustrations for a couple in Indonesia.

She used AI to write to her clients in English, which isn’t her first language, and to keep track of the back-and-forth. Her delivery got better. The work was still hard. Work is work.

The old model has a simple shape. You sell a finished piece to one buyer. That buyer compares you with every other seller on the platform, mostly on price. Fiverr keeps 20% of every order.

That market is also shrinking for people like SH. A study of a major freelance platform found that within a year of AI image generators arriving, job posts for image creation fell 17% relative to manual-intensive work (Demirci, Hannane and Zhu). Fiverr’s own annual report says AI adoption is pulling its high-skilled and low-skilled services apart.

The new buyer is an AI lab. The lab wants her judgment about the picture: what makes a wedding illustration good, where a model’s version falls apart, and how to score the difference. That judgment gets reused every time the model draws. Mercor’s creative-roles page says creative professionals there earn $60 to $120 an hour, paid weekly.

So I told her to look at design roles at AI training companies instead. The four I named were Mercor, Handshake AI, micro1 and Surge AI. She applied that week.

Where you live decides which of those doors are open. Handshake AI requires US work authorization, and the work itself has to be done from inside the US. Surge AI doesn’t publish an eligibility list, and third-party reviews report that DataAnnotation, the open platform it runs, accepts six English-speaking countries. micro1 says it hires globally. Mercor sets location rules listing by listing, so read each one.

Subscribe now

Should designers leave Fiverr and Upwork for AI training work?

My dear experts: delete your Fiverr and Upwork accounts. Do it on the day your first AI-lab project pays out.

Keep them until then. AI training work is spiky. Queues go quiet for weeks, and projects end early. The old account is your floor while the new work proves itself.

After that, stop spending your taste on gigs priced against every other seller in the world. Taste is what models lack, and it’s what the labs are paying for.

Is AI training work going to last?

Nobody knows, including me. Here is what I’d bet on.

Each time models improve, the easy tasks get solved and the remaining ones need someone more senior. The work moves up the expertise curve. It also gets smaller. A job became a project. A project became a stream of tasks, each with a timer. When the work is that atomic, finding the next piece of it becomes a big part of the job.

The demand is large right now. SemiAnalysis, quoted in Paul Millerd’s piece, reports that Mercor logged about 2.5 million expert hours in the second quarter of this year. That’s roughly 4,800 people working full time.

The skill that carries from project to project is the one Mercor’s CEO named on Conversations with Tyler: finding where the model makes a mistake. I’d add one thing. Explaining why, in writing, is what gets you paid.

What is AI training work actually like?

I know how it goes. I’ve done this work on more than ten Mercor projects. It is often exhausting. Some weeks it’s suffocating. This newsletter exists because of it.

Here is what readers send me, and what I’ve lived:

• The queue goes quiet for three weeks, and nobody tells you why. I broke down the mechanics in Why Your Mercor Queue Went Quiet.

• The matcher sends a radiologist a music-tagging task.

• A stated $90 an hour becomes $25 once the handling-time cap bites. The AHT Game has the math. I have stopped my own timer when a task ran long, so my handling time wouldn’t flag me. I’m including that as a disclosure. The cap does that to people.

• Projects end without warning. Business Insider reported last November that Mercor ended a large Meta project with more than 5,000 contractors, who had been told it would run to year-end, then offered similar work for $5 an hour less. Mercor called the report inaccurate without saying which part. In March, Business Insider reported that Handshake AI suspended contractors, told them the decision was final with no appeal, and paid four of the five it spoke to nothing for completed work.

• The search eats months. In public forum threads I read this summer, one contractor listed the ten platforms she’d registered with. Nine produced nothing. Others describe one to five months from application to first contract. That’s contractor testimony, and I label it that way.

Some of this is the nature of project work. Every Mercor listing I opened for this post carries the same line: “Projects can be extended, shortened, or concluded early depending on needs and performance.”

Some of it is structure. You see one dashboard. The platform sees every project, every rate and every contractor’s numbers. When a project ends, the platform draws from a queue of replacements, and you start again from an empty one. That’s a weak position to bargain from, and most experts are in it alone.

What is clawded.ai?

clawded.ai is a job-matching tool for remote AI data work, incubated by World Model (world-model.xyz) community. It matches your profile to verified openings across AI training platforms, including Mercor, Handshake AI, micro1 and Toloka. Every opening is checked at the source before you see it.

World Model is the community. Every week, readers write to me about which projects paid, which went quiet and which listings were dead. clawded.ai is where that intelligence goes to work for one person: you.

The first thing it does is matching. A platform’s matcher exists to fill its clients’ projects. clawded.ai starts from your profile and looks across platforms.

My own page, updated September 29. Each match says why it fits me and what gap to close before I apply. When I rechecked all three on September 29, #3 had stopped taking applications. That’s how fast this market moves, and it’s why every match gets rechecked.

What paid subscribers get in clawded.ai:

• Three verified openings a day, hand-picked for your profile. Each one is taking applications on the day it’s checked.

• Region screening. A role that needs US work authorization won’t be sent to you in Berlin or Bangalore.

• Pay flags: handling-time caps and payment problems, noted where I know about them.

• A save button, so you can come back to a role and apply later.

• No form to fill in twice. It picks up what you’ve already told me in DMs and email. That information is used for your matches and nothing else, and I’ll delete it whenever you ask.

• Your own private page, behind your own login.

  Subscribe now

Why is it called clawded.ai?

I’ve written before that experts do this work bare-handed. You find the listing yourself, check it yourself and apply alone. A claw is the simplest tool there is: something to grab with. clawded.ai is meant to be that tool.

How clawded.ai checks an opening

World Model (world-model.xyz) checks every opening before it reaches clawded.ai. An opening counts as verified when it is taking applications on the company’s own careers page or applicant system on the day it’s checked. Region locks, payment rails and handling-time caps are noted when the listing or reader reports show them. For this post, on September 29, 2026, I rechecked the three openings on my own page and five Mercor design listings. Three of the eight had closed. Anything that fails the check doesn’t ship.

How does clawded.ai work?

I check openings in public every week. Paid subscribers get the same work done for one profile: theirs. clawded.ai is in beta, for paid subscribers first, and it will open wider later.

1. Become a paid subscriber

   Subscribe now

2. Reply to the email I send you with three things: your background, where you live and are allowed to work, and your resume. New paid subscribers get that email right after joining. Already a paid subscriber? Mine is on its way to you this week.

3. I reply with your clawded.ai login. Your first matches will be waiting.

Everything else paid subscribers get stays. The insider posts continue. Past ones include the Hands-On Mercor Playbook (one reader followed it to $37,000 in four months), the Mercor profile prompt from AI Tools for Nomads #1, The Mercor Location Trap, and the Inside the Data Factory series. The prompts from those posts are being built into clawded.ai.

You are not alone

Working for an AI lab from a laptop can feel like working for nobody. A project ends, the Slack goes quiet, and there’s no one to ask.

There are over 26,000 of us here, spread across the world and across Mercor, Handshake, micro1, Surge AI and the rest. You’re not alone in this, and you shouldn’t have to do it bare-handed.

PS: If you’re outside the US, Handshake is closed to you unless you live and work there. micro1 says it hires globally, and the Mercor design study above states no region lock. clawded.ai screens every match for where you can actually work, so you stop opening US-only listings.

FAQ

What is clawded.ai? A job-matching tool for remote AI data work from World Model (world-model.xyz). It matches paid subscribers to verified openings across AI training platforms such as Mercor, Handshake AI, micro1 and Toloka.

Who can use clawded.ai? World Model paid subscribers, anywhere in the world, during the beta.

Does clawded.ai work outside the US? Yes. Every match is screened for where you live and are allowed to work, so roles that need US work authorization, like most Handshake AI roles, only go to readers who can take them.

Landing a $50 to $100+ per hour AI data evaluation gig is one of the best life hacks in the entire digital nomad world right now. You open your laptop in a beachside café in Da Nang, a coworking space in Lisbon, or an apartment in Buenos Aires, fire up your task queue, and make senior developer or legal consulting money just by reviewing frontier AI models.

In our earlier posts on world-model.xyz, we showed you how to beat the front-door algorithms. Post #1 broke down the exact field-mapped profile prompt that lands instant job offers, and Post #2 handed you the conversational playbook to crush asynchronous AI video screenings and sidestep automated hiring filters.

Once you pass the initial tests, prove your identity, and get dropped into an active queue on platforms like Mercor, Micro1, or Handshake AI, the rules of the game change completely.

The main danger to your paycheck isn’t finding open projects anymore. It’s surviving the weekly purge.

Welcome to the most ridiculous Catch-22 in the entire remote work world: The Anti-AI Detection Paradox.

A frontier AI lab hired you specifically for your sharp human brain. The platform then expects you to work at a superhuman speed that no normal person can pull off by hand. But the second you try using AI to speed things up, the platform’s background tracking software spots it, locks your account, and kicks you off the project without letting you appeal.

Surviving in this game means learning how platform surveillance actually tracks you, understanding why generic AI writing gets people fired, and setting up an isolated setup that cuts your work time in half while keeping your human touch front and center.

The Big Irony: Training Frontier Models While Banned from Using Them

If you spend any time browsing Reddit—checking out r/mercor, r/mercorai_workers, r/micro1_ai, or r/joinhandshakeai—you’ll notice one big trend: people are terrified of getting quietly dropped.

The numbers back it up. Experienced task reviewers on top-tier Mercor projects regularly mention that between 15% and 50% of domain specialists get kicked off projects every single week just for using AI. These are high-earning roles paying $100+ an hour to check complex answers in coding, healthcare, law, and high-level STEM, yet people are getting cut in waves.

Why are AI labs so paranoid about workers using the very tools they build?

It comes down to a core technical issue: model collapse. AI labs are spending fortunes on human experts because of one main threat. When newer AI models are trained on content written by older AI models, they get dumber over time. They develop weird habits, repeat the same generic phrases, and lose the ability to think through real-world edge cases.

The labs don’t need more machine-written answers; their servers are already flooded with them. What they need—and what they pay you $100 an hour to provide—is genuine human thinking: your messy troubleshooting, your real experience, and your ability to spot subtle logical mistakes.

If you ask ChatGPT or Claude to draft your task feedback and you just paste it in, you’re feeding synthetic patterns back into a system trying to learn how humans think. To protect their data, platforms run automated checks designed to find and ban anyone submitting machine-like writing.

Under the Hood: How Platforms Catch You (Typing Trackers, AI Scanners, and Unfair Bans)

A lot of workers assume platforms just copy-paste their text into a free online AI checker.

In reality, the surveillance runs much deeper. Modern platforms watch what you type, how you type it, and the underlying rhythm of your sentences.

Typing Rhythm and Keystroke Trackers

Platforms track what you do inside the task page. When you’re typing inside their portal, built-in code measures how long you hold down individual keys, how many milliseconds you pause between keystrokes, and how often you hit backspace.

Normal human typing is naturally messy. You pound out a sentence fast, pause for five seconds while thinking about a point, fix a typo, and delete half a sentence to reword it.

If someone copies a block of text from an external chat window and drops it in, the platform sees a sudden 400-word jump with zero typing activity beforehand. Even auto-typer extensions usually fail here, because they type at robotic, perfectly even speeds that trigger automated alarms anyway.

Tone Detectors: Sentence Bounce and Predictability

When you submit your feedback, the platform’s scanning tools look at two main patterns in your writing: how predictable your words are, and how much your sentence rhythms bounce around.

Language models pick words based on statistical probability, meaning their writing flows smoothly and predictably. Natural human writing—especially from experts—is far more erratic. Real people throw in informal observations, shift topics abruptly, and use unusual technical terms without over-explaining them.

Sentence variety matters just as much. Real people naturally mix things up: you might write a punchy four-word sentence, followed right away by a long, winding explanation. AI, on the other hand, usually writes paragraphs where every sentence is roughly the same length and rhythm.

Automated detectors look for classic AI habits:

• Overusing generic transitions like “Moreover,” “Furthermore,” “In conclusion,” “It is crucial to note,” and “Delve.”

• Predictable five-sentence paragraphs that start with an introduction, offer three neat examples, and wrap up with a tidy conclusion.

• A polite, watered-down tone that tries to please everyone instead of taking a clear, critical stance.

The “Too Smart” Trap: When Writing Well Gets You Banned

The most frustrating part of these automated scanners is how often they misjudge real human writing.

Professionals with serious credentials—like doctors, corporate lawyers, and PhD researchers—are trained to write in a formal, passive, and measured style. If an expert types: “The provided clinical reasoning is insufficient; furthermore, the diagnostic pathway fails to account for secondary hypertension,” an automated scanner might flag it as AI-generated text just because it sounds polished.

Contractors regularly share stories of getting warned or dropped simply because they write in formal English. Reviewers rushing to hit their own quotas will often side with the automated scanner, removing great contributors whose only mistake was writing like an academic.

Why Grammarly Will Get You Fired

This strict monitoring creates an unexpected casualty: everyday writing extensions.

Contractors often wonder if they can leave tools like Grammarly or spell-checkers running while working. The answer is a clear no.

Writing extensions work by plugging directly into the web page to watch your text boxes. When Grammarly highlights a mistake and you click to accept the fix, it injects the new word directly into the page code.

To the platform’s tracking tools, that automatic fix looks like an unauthorized text-injection script or a paste command. People have lost steady gigs just because a browser extension quietly fixed a comma inside the answer box.

The Speed Trap: Why Doing Everything by Hand Kills Your Hourly Rate

If using AI risks an account ban and writing too formally gets you flagged by mistake, the safest bet might seem to be doing every step completely by hand.

The problem is that the platform’s own pacing targets make that nearly impossible.

On advanced reasoning projects across Mercor and Micro1, platforms track your Average Handling Time (AHT). In a typical task, you’re handed a user prompt along with four or five competing AI responses. Each response can run 600 to 800 words.

Before writing a single sentence of feedback, you have to read over 3,000 words of technical text, fact-check obscure citations, and make sure every claim follows 60 pages of client project guidelines and rulebooks.

The target handling time for these tasks is often set at just 30 to 45 minutes.

Break down the clock:

1. Reading 3,500 words of dense reasoning: 15 minutes.

2. Verifying technical citations and math: 15 minutes.

3. Checking the 60-page client project guidelines to confirm edge-case rules: 10 minutes.

4. Writing out a thorough, multi-part critique: 15 minutes.

Doing the job thoroughly takes around 55 minutes. Take that long, and your handling metrics drop into the red. Soon, you get an automated email warning you about your pacing. If your times don’t improve, you get silently dropped from the queue for working too slowly.

On the flip side, if you rush to beat the 35-minute timer, you miss things. You overlook a small hallucination or mess up a formatting rule. When your task hits a peer reviewer, they reject your work, your quality score sinks, and you get removed for poor accuracy.

Contractors get stuck in a corner: work entirely by hand and get cut for being too slow, or lean on standard AI tools and get banned for synthetic content.

The #1 Golden Rule: Keep Insightful Trapped on its Own Machine

Before setting up any AI workflow to speed up your work, you need to understand the main way platforms catch people: direct desktop monitoring.

Mercor requires workers to run a desktop app called Insightful (which used to be named Workpuls) to log billable hours, track activity, and catch unapproved software. Insightful isn’t just a simple clock you start and stop; it’s enterprise-level monitoring software sitting directly on your computer.

Here is what Insightful is actually doing while your timer runs:

• Periodic Screen Captures Across All Monitors: Insightful takes regular screenshots of your workspace. If you use multiple monitors or virtual workspaces (like macOS Spaces or Windows Virtual Desktops), it takes pictures of all connected screens and spaces, not just the window you’re looking at. If you leave ChatGPT sitting on a side monitor or another virtual desktop, it will show up in a compliance screenshot.

• Logging Running Apps and Window Titles: The software constantly logs the names of your open programs, background processes, and browser window titles. Even if you minimize an AI tool or let it run in the background, its web address and window title end up in the platform’s audit log.

• Automatic AI Alerts: Insightful’s dashboard comes with automated alerts designed specifically to catch unauthorized AI tools. When an unapproved AI site or app opens on that machine, management gets an automatic flag.

The Rule: Complete Hardware Separation.
Don’t bother trying workarounds like incognito tabs, alternate browser profiles, hidden virtual desktops, or virtual machines on your work computer.

You need to use two physically separate machines:

• Machine A (The Work-Only Machine): The computer running Insightful, your client browser, and the task portal. Keep this machine completely clean. No ChatGPT accounts, no AI desktop apps, no research extensions, and no shortcuts. Treat Machine A as if your project manager is sitting right next to you looking at your screen.

• Machine B (Your Personal Research Machine): A separate personal laptop, desktop, or tablet sitting next to your work machine. This is where you search rulebooks in Google NotebookLM, run fact-checks with Perplexity, and draft initial points using custom prompts. Machine B has zero surveillance software on it and never connects to your client’s accounts.

Never connect these two machines using shared clipboard features (like Apple Universal Clipboard or clipboard-sharing tools). Copying something on Machine B and pasting it directly onto Machine A will immediately trigger paste-tracking alerts on your work computer.

The Golden Rule of Content: Never Copy-Paste. Always Proofread, Hack Apart, and Rewrite.

Even with two separate machines, there’s another major mistake that gets people banned: letting raw AI writing slip through.

Some contractors think that as long as Insightful can’t see their screen, they can generate an answer on their second laptop, retype it word-for-word, and hit submit. That’s an easy way to lose your account.

Never copy and paste text into your submission box under any circumstances.

Beyond the technical risk of triggering paste listeners, there’s a bigger issue: AI models are bad at judging other AI models.

When you ask an AI model to evaluate a task, it will routinely:

• Make up a claim that another model broke a guideline when it actually followed the instructions.

• Miss subtle factual errors or fake math steps while obsessing over minor formatting.

• Fall back on sterile phrasing that automated detectors immediately recognize.

The rule for staying safe on high-tier projects is simple: Always proofread, verify, and rewrite.

Think of any AI output you generate on Machine B as an unpolished rough draft. It’s there to save you five minutes of staring at a blank screen, not to do your thinking for you.

You have to look at the draft with a skeptical eye, verify every claim against the original prompt, cut out every generic filler sentence, and rewrite the points in your own words. If you skip the rewrite, you will eventually submit a fake critique or a robotic phrase that gets flagged during a manual review.

The $100/Hour Queue Weapon

If you’ve followed our series on world-model.xyz, you know we don’t publish generic productivity advice. We break down the exact algorithmic systems running the modern remote knowledge economy.

• Post #1 gave you the field-mapped profile prompt that triggered instant offers.

• Post #2 gave you the conversational guideline to clear the AI video interview without triggering fraud filters.

What follows below is an operational asset we’ve been refining to help top-tier specialists survive aggressive handling times on $80 to $100+ per hour queues.

Think about the math for a second:

• On an $80–$100/hr contract, losing your queue due to an automated pacing warning or a false-positive detection flag wipes out $4,000 to $8,000 in monthly recurring income.

• A thorough manual evaluation takes 50+ minutes, putting your handling metrics in the red.

• Standard AI prompts produce predictable, balanced text that sets off detection alarms within your first ten submissions.

A monthly subscription to world-model.xyz costs less than 7 minutes of your billable rate. Think of it as operational insurance for your remote contracts.

To tackle this bottleneck, we’ve been testing and iterating on The Stealth-Rater Prompt (Beta).

Let’s be completely transparent upfront: this framework is still experimental. There is no push-button miracle prompt that will do $100/hr domain evaluation work for you on autopilot—and anyone promising you that is setting you up to get blacklisted.

Instead, think of this as an evolving testing scaffold built specifically for domain raters in STEM, coding, law, and medicine. It won’t give you a finished, ready-to-paste deliverable, but it is engineered with strict negative constraints to strip out typical AI clichés, break up repetitive sentence rhythms, cross-reference candidate completions directly against your project guidelines, and generate structured expert data content tailored to the client’s rubric.

Its purpose isn’t to replace your brain; it is an experimental starting canvas designed to cut down initial analysis time and save you 15 to 20 minutes of blank-page fatigue per task, while leaving the critical thinking and mandatory rewrite firmly in your hands.

Paid subscribers unlock:

1. The Stealth-Rater Prompt (Beta): The complete, field-tested system prompt engineered with negative linguistic constraints, guideline mapping, and multi-input formatting (Guidelines, Prompts, and Model Responses).

2. Instant Access to the Full Paid Archive: All previous tactical deep dives, including the field-mapped Mercor Profile Prompt (Post #1) and the complete AI Video Interview defense script (Post #2).

3. Weekly 3 Personalized AI-Native Remote Jobs: Hand-curated, verified remote opportunities ($50–$100+/hr expert contractor roles and high-upside AI positions) delivered directly to your inbox every single week.

Read more

Staring at an empty Mercor dashboard for the fortieth day in a row?

Refreshing Slack and checking your email every twenty minutes, wondering if you failed an opaque quality audit, if an automated anti-cheat bot flagged your tab switching, or if you got ghost-banned because an AI evaluator woke up on the wrong side of the server rack?

Here is the cold, unvarnished truth: It is probably not your work. It is your ZIP code.

While 22-year-old Thiel Fellow founders are hailed as tech billionaires operating out of luxury towers at 181 Fremont in San Francisco, the data factories powering the frontier AI boom have quietly erected geographic firewalls. If you live in California—or a handful of other legally radioactive states—platforms have turned off your tap while keeping your profile active to show venture capitalists a sparkling roster of “available talent”.

If you have been out of work, sitting on the bench, and wondering where the flood of $60 to $150/hr evaluation tasks went, welcome to the jungle. Here is the real story behind the California stealth freeze, the Reddit whistleblower leaks, the nationwide location risk index, and the tactical playbook to get your queue humming again.

The Ghost-Ban: Why Your Mercor Queue Is a Desert

For months, contributors across California noticed a sudden, eerie silence. Highly credentialed specialists—attorneys, senior software engineers, and domain researchers who previously logged 30 to 40 billable hours every week—saw their active projects evaporate without explanation.

When you log in, everything looks normal. Your profile is verified, your assessments show passing scores, and your dashboard invites you to submit more unpaid video samples. But the project invites never arrive.

This is ghost-gating.

Behind closed doors, project leads have admitted that Mercor instituted an unannounced operational freeze on all California independent contractors. They haven’t banned your account because your credentials inflate their marketing numbers. Instead, internal routing rules automatically drop California ZIP codes to the absolute bottom of allocation queues.

The $12.5 Million Reason for the Freeze

This isn’t platform malice; it’s sheer corporate terror.

Mercor watched its arch-rival, Scale AI (and its subsidiary Outlier), get dragged into San Francisco Superior Court in the explosive class-action lawsuit McKinney v. Scale AI. The lawsuit laid bare the data factory playbook: treating elite contributors as “freelancers” while subjecting them to continuous algorithmic surveillance, unpaid training webinars, unpaid assessment carrots, brutal handling timers, and arbitrary pay cuts.

Scale AI settled for a staggering $12.5 million.

Under California’s Assembly Bill 5 (AB 5) and the statutory “ABC test,” hiring companies must prove that a contractor performs work outside the hiring company’s core business. When your entire $10 billion enterprise is based on selling human reasoning datasets to OpenAI, Anthropic, and Meta, telling a California labor judge that your human annotators are “incidental” is legal suicide.

Terrified of being hit with an identical multi-million-dollar class action under California’s Private Attorneys General Act (PAGA), Mercor slammed the emergency brake. While they still slip a handful of Bay Area specialists into labs via formal W-2 third-party staffing agencies like Cincinnatus LLC, everyday remote 1099 contracts across California have been completely shut down.

Field Leaks: What Reddit and Contributor Groups Are Saying

If you rely on official company communication, you will never hear about this. But across Reddit (r/mercorai_workers, r/recruitinghell) and worker leak channels, contributors have pieced together the puzzle:

• Aggressive Forum Censorship: When California contributors took to official Mercor forums to ask why new project distributions had ceased, community moderators systematically rejected and deleted their posts. The goal? Keep the pipeline full of hopeful applicants while hiding the fact that California talent is barred from receiving tasks.

• College-Age Leads Panicking over Labor Codes: Contributor field reports reveal that frontline project managers are frequently recent college grads who had no idea what independent contractor classification laws entailed. When senior attorneys and veteran tech workers on $100 to $150/hr legal/coding queues began quoting California Labor Code § 2775, management panicked and rapidly offboarded anyone raising compliance concerns.

• Unlawful Pre-Employment Credit Checks: Contributors reported being required to submit to consumer credit checks during onboarding. In California, Labor Code § 1024.5 strictly bars employers and hiring entities from demanding credit reports for non-fiduciary positions, exposing the platform to immediate statutory liability.

• Retroactive Quality Clawbacks: Other taskers have flagged bait-and-switch compensation terms: jobs advertised as hourly engagements were revised after work was submitted, with platforms demanding uncompensated revisions or threatening pay deductions if subjective quality metrics were missed—a practice that runs afoul of California wage protections.

• The LiteLLM Security Crisis: Making matters worse, five federal class-action lawsuits were filed against Mercor in California and Texas federal courts following an open-source LiteLLM vulnerability. The breach leaked contractor Social Security numbers, W-9 tax forms, home addresses, and AI video interview recordings. Following the disclosure, major enterprise clients like Meta paused project pipelines, compressing task queues nationwide.

The Non-US Path vs. The Domestic Minefield

As we examined in earlier world-model.xyz breakdowns like “Two queues beat ten: Mercor, Handshake, and the non-US path,” the global data pipeline has bifurcated:

• The Non-US Path: High-volume, generalist data tasks have migrated to low-cost digital hubs in Kenya, the Philippines, and Latin America. At $3 to $8 per hour, platforms don’t have to worry about the California ABC test, overtime pay, or lunch breaks.

• The Domestic Reasoning Tier: Frontier AI labs building models like Claude 3.5 Sonnet, Gemini 1.5 Pro, and GPT-4o cannot offshore complex code verification, intricate legal edge-cases, or doctoral-level safety alignment. They require domestic specialists.

Because frontier labs still need domestic US experts, platforms cannot simply abandon the United States. Instead, they run an algorithmic game of geographic avoidance, cutting off entire states where local laws threaten their profit margins.

The Geolocation Danger Zone: Risk Scores Ranked

Where do you live? Here is how hazardous your home state is to your AI data queue, ranked on a 1-to-10 Danger Score based on platform exclusion policies:

California: Danger Score 9.8 / 10 (Ground Zero)

Read more

In Episode #1, we walked through the exact profile prompt that rewrites your Mercor fields to trigger instant offers. We looked at how models read documents, why 15-word summaries win, and why bringing an unoptimized resume to an automated platform is like bringing a knife to a laser fight.

Today, in Episode #2, we are going behind the camera.

We are tackling the part of the pipeline where most qualified domain experts get quietly eliminated: the AI evaluator.

I have sat on both sides of the Mercor table.

As a contributor, I have pulled in five-figure months working remote AI projects. As an Expert Project Manager (EPM), I have sat on the vetting side, watching thousands of candidate profiles stream through the intake queue.

When people apply to these platforms, they imagine a tired recruiter skimming their PDF over a cup of coffee. They think someone is reading between the lines to spot their hidden potential.

That is not how it works.

On platforms like Mercor, your interviewer is an LLM, and your first gatekeeper is an algorithm.

As an EPM, my job was never to hunt for raw potential. My job was variance reduction. In plain English: my job was to filter people out. Enterprise AI labs do not want creative surprises. They want domain authority, predictable execution, and zero fraud risk.

Every single day, roughly 10,000 candidates sit down across from Monty, Mercor’s AI interviewer. Most of them blow it before they say a single word. They get filtered out because of an ambiguous job title, an unverified account, an awkward pause, or an unforced camera mistake.

Passing the evaluator is not about being a genius. It is about understanding the mechanical rules of the machine scoring you.

Here is how the system actually works, and how to make sure you come out on the other side with an offer.

The Profile Match (Where Most People Lose Before Starting)

Before you ever see an interview link, a vector search engine evaluates your profile. It converts your profile into structured data: domain, seniority, tooling, and rate band. Then it calculates a mathematical similarity score against the client’s open requisition.

If that similarity score is high, you get an interview. If it is exceptionally high, you can trigger an instant offer. If it is low, you sit in silence.

Here are the four profile rules that dictate whether the matcher surfaces you.

1. Job Titles Matter More Than Your Bullets

Most people treat job titles as casual labels and spend all their energy polishing bullet points. That is backwards.

The vector matcher weights the title field far more heavily than descriptive text. If an enterprise client asks for an “AI Evaluation Specialist” or “RLHF Domain Expert,” but your profile title says “Operations Consultant,” you lose. The machine interprets standardized titles as verified structural categories.

Do not try to look like a jack-of-all-trades. A profile that claims three identities matches none of them. Pick the exact role you are targeting and use standard industry titles that match what the platform is hiring for.

2. The 3-Year Experience Floor

Read more

In May I did one thing on Mercor. I did not add a job, a degree, or a skill I do not have. I rewrote the profile I already had, using a prompt, and an instant offer arrived. I wrote that up at the time in I updated my resume and got an instant Mercor offer.

Since then the prompt has gone out by DM to every paid subscriber who asked, and a lot asked.

This is the first post in a new series. AI tools for nomads: prompts and routines I actually use to get and keep remote AI work. The tool is not the point. The point is that the people hiring for this work are models, and if you are not using a model to talk to them, you are bringing a resume to a vector search.

The part of Mercor everyone skips

People polish the resume PDF. They sweat the AI interview. Then they leave the Profile tab half-filled with whatever the resume parser guessed on day one, and never open it again.

That is the wrong place to be lazy, because of what the profile is for.

Mercor does not read your profile the way a recruiter reads a resume. From what I can see working the platform from both the contributor and the reviewer side (this is my read of the mechanics, not Mercor’s published documentation), it parses the document into a structured representation: skills, domain, seniority, tooling, project shape, rate band, availability. It parses each job the same way. Then it matches by similarity. High similarity surfaces you. Very high similarity can produce an offer with no human in the loop. That is what an instant offer is.

So your reader is an LLM. Write for it.

Three things I found on the live profile page this week

I went through my own Mercor profile tab by tab on September 13 and checked every field against how the prompt was telling readers to fill it. The v1 prompt got three things wrong, and all three are worth knowing even if you never run the prompt.

The Summary field takes about 15 words. A paid subscriber found this the hard way: the field cuts off well before a normal profile summary ends, so the v1 prompt was producing summaries that could not be pasted. This limit is not in Mercor's published docs. It is a firsthand product observation, so test it in your own account. Either way, 15 words is the right target, because the matcher weighs the first nouns heaviest.

Skills are tags, entered one at a time, and the parser's guesses stay until you delete them. My own profile had "Smart Parking Solutions" sitting in Skills. That is a product I once worked on. It is not a term any job description on Mercor contains. It was pure noise in what is probably the highest-weight field on the page, and it had been there for months because I never looked.

Mercor's own LinkedIn widget says verified profiles have 6x higher chances of an offer. That is Mercor's claim, in Mercor's words, on Mercor's page. Roughly half the people who DM me about quiet queues have never clicked it.

What is below the paywall

The rest of this post is the v2 prompt in full, rewritten this week so its output follows Mercor’s profile page section by section (Summary, Education, Work experience, Projects, Certifications, Awards, Coding Profiles, Links, Skills, Languages, Hobbies), in the order you fill it. Around it: the four-step routine I run every time I change target roles, what the output looks like when it is right, the answer to the “does re-targeting flag my account” question, and a reply-to-get-it offer where I fill the template for your role myself.

Upgrade to read the rest

The four-step routine

Step 1. Pick one role, and copy the whole job description. I know you apply to several tracks at once. So do I. But the profile can only argue one identity at a time, and a profile that argues three matches none of them. Choose the role you want most. Open its page on Mercor and copy the full description text into the prompt. Not the link. Your AI tool cannot open Mercor pages behind your login, and a link gives it nothing to match against.

Read more

What the paid tier actually is

It is this newsletter’s verification work, done for one profile instead of a public list. Yours.

You tell me where you are. I go find what fits, and I tell you what I would do if I were you, in addition to the paid posts.

1. The profile prompts. The Mercor one that produced the offer above, plus versions for micro1, Handshake AI, and the smaller platforms. Updated when the platforms change, which they do.

2. Matched openings, sent to you weekly. AI training and expert-data roles across the big platforms and the small ones, filtered against your background, your region, and your license. Including postings that never surface on aggregators because they close before anyone indexes them.

3. Advices for remote work operations. Running a distributed week, handling tasks across a nine hour gap, managing Slack so it does not manage you, tracking your own hours independently so you can dispute a shortfall in the same week it happens.

4. The offboarding-risk playbook. Where the handling time corridors sit on projects I have run, what the assessment gates actually test, and how to exit a project without it costing you the next one. Built from more than ten projects on both the contributor and the reviewer side.

I cover Mercor, Handshake AI, and micro1 in the same place, which matters more than it sounds like. They are not substitutes. Mercor pays higher at the top and goes quiet for weeks at a time. Handshake is steadier and lower, and has its own payment problems that I have documented and will keep documenting. Holding both queues open is how a bad month on one stops being a zero month.

How to start, in one reply

Upgrade here, then reply to the welcome email with three lines:

Subscribe now

1. Which platform or platforms you are on.

2. Which stage you are at: not applied, applied and waiting, onboarded and idle, or actively on a project.

3. Your background, your region, and any license or specialty.

That is enough for me to start matching. You get the profile prompt back the same week, and your first matched roles in the next customized email.

Not sure if you have noticed, but you are in a cult.

Not a robed one. A professional one. It has a name for its members (contributor, fellow, expert), a private language (AHT, R2I, rubric, gate), a shared enemy (the models that get everything wrong), and a promise that the work you are doing matters more than the pay rate suggests. It has initiation rituals that cost you unpaid hours. It has channels where you can see everyone else’s devotion but nobody’s invoice. And it has the one feature every group like this shares: leaving feels like losing something you cannot get back.

I want to name it plainly, because I am part of it too. I have worked more than ten Mercor projects on both the contributor and the reviewer side. I read the Slack channels. I know the feeling of a queue that goes quiet for three weeks and the relief when it comes back. That relief is the mechanism. It is the thing that keeps very smart people accepting whatever arrives.

This post is about how the expert-data economy works on you, what a sane remote working life looks like inside it, and what I do for paid subscribers who want somebody on their side of the table. Most of all it is about being free inside this jungle, which is not the same as leaving it.

Why the AI expert economy feels like a cult

The playbook for building a movement is well understood. You need a compelling story about the future, an in-group with its own vocabulary, a sense that outsiders do not get it, and a founder who can articulate why the mission justifies the sacrifice. Every one of those pieces is present in AI data work.

The story. The pitch is that the next decade of knowledge work is about encoding your expertise into models. Mercor’s CEO has said the network passed 4 million vetted experts and pays out more than $2 million a day. Handshake AI reports $100 million paid to more than 100,000 fellows. Frontier labs are spending over $1 billion each on training environments. None of that is fake. The money is real and the mission is real. That is exactly what makes the rest of it work.

The initiation. Onboarding and assessments are unpaid on most platforms. You give hours before you see a rate. Many get onboarded, few get retained, and the gates that decide who stays return no score and offer no appeal. You learn to treat acceptance as a gift instead of a contract.

The vocabulary. Once you know what AHT means, you are inside. Maximum handling time caps the paid hours per task no matter how long the task takes. A nominal $60 to $100 an hour becomes an effective $8 to $25 once the cap bites. On Handshake’s Project HH in May 2026, workers were paid 20 to 50 percent of the hours they logged. I covered the mechanics in The AHT Game and the Handshake failures in the Handshake issue. Inside the group, these become normal facts of life. From outside, they look like what they are.

The silence. Nobody tells you why the queue stopped. Nobody tells you why the radiologist got a music-tagging task. Silent offboardings run at a roughly 7.5 percent rate on one platform, with no appeal. You fill the silence with your own explanations, and most of the explanations you reach for are about you.

I want to be careful here. I do not think this is designed by villains. It is a sieve. The platforms are built to select for people who tolerate uncertainty, unpaid ramp time, and rate compression without complaint. The people who stay are the people the system fits. That is a selection effect, not a plot. But the result for you is the same either way: you adapt to the sieve instead of the sieve adapting to you.

What the paid tier actually is

It is this newsletter’s verification work, done for one profile instead of a public list. Yours.

You tell me where you are. I go find what fits, and I tell you what I would do if I were you, in addition to the paid posts.

1. The profile prompts. The Mercor one that produced the offer above, plus versions for micro1, Handshake AI, and the smaller platforms. Updated when the platforms change, which they do.

2. Matched openings, sent to you weekly. AI training and expert-data roles across the big platforms and the small ones, filtered against your background, your region, and your license. Including postings that never surface on aggregators because they close before anyone indexes them.

3. Advices for remote work operations. Running a distributed week, handling tasks across a nine hour gap, managing Slack so it does not manage you, tracking your own hours independently so you can dispute a shortfall in the same week it happens.

4. The offboarding-risk playbook. Where the handling time corridors sit on projects I have run, what the assessment gates actually test, and how to exit a project without it costing you the next one. Built from more than ten projects on both the contributor and the reviewer side.

I cover Mercor, Handshake AI, and micro1 in the same place, which matters more than it sounds like. They are not substitutes. Mercor pays higher at the top and goes quiet for weeks at a time. Handshake is steadier and lower, and has its own payment problems that I have documented and will keep documenting. Holding both queues open is how a bad month on one stops being a zero month.

How to start, in one reply

Upgrade here, then reply to the welcome email with three lines:

Subscribe now

1. Which platform or platforms you are on.

2. Which stage you are at: not applied, applied and waiting, onboarded and idle, or actively on a project.

3. Your background, your region, and any license or specialty.

That is enough for me to start matching. You get the profile prompt back the same week, and your first matched roles in the next customized email.

Below the wall: the habit system that makes remote work run without a boss, and the monthly focus exercise I use when the platform silence starts writing stories in my head at 3am.

Read more

What the paid tier actually is

You tell me where you are. I go find what fits, and I tell you what I would do if I were you. The paid posts come with it.

Profile prompts. The Mercor one, plus micro1, Handshake AI, and the smaller platforms. Rewritten when the platforms change, which they do.

Matched openings, weekly. AI training and expert data roles filtered against your background, your region, and your license. Including postings that close before an aggregator ever indexes them.

Remote work operations. Running a distributed week across a nine hour gap. Keeping Slack from managing you. Tracking your own hours so you can dispute a shortfall in the same week it happens.

The offboarding risk playbook. Where the handling time corridors sit on projects I have run, what the assessment gates actually test, how to leave a project without it costing you the next one. Built from more than ten projects, contributor side and reviewer side.

Subscribe now

Previous Highlights

He had taken the Mercor profile prompt I send to paid subscribers, rewritten his profile to target the Generalist track, and hit save. Within minutes he had an offer in his inbox. No interview. No waitlist. No “we will get back to you.”

Two days later he wrote again, and this is the half most newsletters would cut. The role was not what he expected. He was thinking about pausing, and he wanted to know whether re-targeting his profile a second time would get his account flagged.

Getting the offer turned out to be the easy part.

That gap, between landing the work and keeping it, is the whole reason I am opening the paid tier up properly this week. But first, here is the actual thing he changed, free, because I would rather show you the work than describe it.

Where this newsletter came from

Four months on Mercor, thirty seven thousand dollars, and no idea at the start whether any of it was real.

I wrote that up in How I made $37k in 4 months on Mercor and the response is what created World Model.

My inbox filled with people asking the same thing: not “what is this,” but “how do I actually survive it.” So I wrote the Hands-On Mercor Playbook, and then I kept going.

I started this because I could not find a jobs list I trusted. Every roundup was copy-pasted from aggregators, half of it stale, some of it never real. So I built the opposite: I apply to the listings myself, from my own account, and I keep the receipts. When I cannot confirm something, I say so in the post. In the last free issue I applied to twelve Mercor tracks by hand across three days and told you which three turned me down.

Twenty three thousand of you now read this, from every timezone I can name. World Model is currently rising in Substack’s Technology category. I still do the checking by hand.

The part I have to be straight with you about

You have noticed the shape of the deal.

The platforms train AI. The platforms also, on most projects, prohibit you from using AI to do the work. And then they set a maximum handling time that assumes a pace a careful human can barely hold. Go too slow and you are flagged for efficiency. Go too fast and you are flagged for quality. Nobody tells you where either wall is. I mapped what I could in The AHT Game.

That is a real bind and I am not going to pretend otherwise.

I am also not going to sell you a way around it. Accusations of LLM use are one of the live termination reasons on these platforms right now, and termination usually means the work you already finished does not get paid. Advice that gets you offboarded is not a shortcut. It is the most expensive thing you can buy.

So the World Model position on speed is narrow, unglamorous, and it holds up:

Speed comes from what you do before the timer starts.

• Know the rubric cold before you open task one.

• Build your reference sheets, templates, and answer patterns between sessions, on your own time, where no project policy applies.

• Learn the corridor on your specific project, because the cap and the tolerance are both set per project, not per platform.

• Find out what tooling your project actually permits. It varies more than people assume, and the answer is usually written down somewhere nobody reads.

• Recognize when a cap is unwinnable and decline the project. This is the highest-value decision on the list and almost nobody makes it.

None of that is a trick. It is just the difference between contractors who last nine months and contractors who last three weeks.

What the paid tier actually is

It is this newsletter’s verification work, done for one profile instead of a public list. Yours.

You tell me where you are. I go find what fits, and I tell you what I would do if I were you, in addition to the paid posts.

1. The profile prompts. The Mercor one that produced the offer above, plus versions for micro1, Handshake AI, and the smaller platforms. Updated when the platforms change, which they do.

2. Matched openings, sent to you weekly. AI training and expert-data roles across the big platforms and the small ones, filtered against your background, your region, and your license. Including postings that never surface on aggregators because they close before anyone indexes them.

3. Advices for remote work operations. Running a distributed week, handling tasks across a nine hour gap, managing Slack so it does not manage you, tracking your own hours independently so you can dispute a shortfall in the same week it happens.

4. The offboarding-risk playbook. Where the handling time corridors sit on projects I have run, what the assessment gates actually test, and how to exit a project without it costing you the next one. Built from more than ten projects on both the contributor and the reviewer side.

I cover Mercor, Handshake AI, and micro1 in the same place, which matters more than it sounds like. They are not substitutes. Mercor pays higher at the top and goes quiet for weeks at a time. Handshake is steadier and lower, and has its own payment problems that I have documented and will keep documenting. Holding both queues open is how a bad month on one stops being a zero month.

How to start, in one reply

Upgrade, then reply to the welcome email with three lines:

1. Which platform or platforms you are on.

2. Which stage you are at: not applied, applied and waiting, onboarded and idle, or actively on a project.

3. Your background, your region, and any license or specialty.

That is enough for me to start matching. You get the profile prompt back the same week, and your first matched roles in the next customized email.

Subscribe now

What this is not

I do not sell jobs, and I have no back door into any platform. Nobody does, and anyone telling you otherwise is selling you something worse than a subscription.

What I have is a list of roles I checked myself, several years of contractor scar tissue across both sides of these projects, and enough hours in the queue to know which silences mean something and which ones do not.

The subscriber at the top of this post got an instant offer and then found out the role was wrong for him. He is not a testimonial. He is the accurate version of this work: the door opens faster than you expect, and then the real question starts.

I would rather be in your inbox for that second part.

A subscriber wrote to me last week after a bad month. His task queue had stopped refilling, a project he had onboarded to paused without explanation, and the assignment he did get had nothing to do with the expertise on his resume. His summary of the platform was three words long: merciless and messy.

Then he asked the question I now get several times a week, and the one you may have a tab open for right now. Should he go find a new platform?

The instinct behind it is right and the conclusion is wrong. Concentration is genuinely dangerous, and I have written before that no single project should carry more than about sixty percent of your income. But the fix is not more platforms. For most people the fix is two platforms and much harsher selection inside them.

I can now show you why with something better than my own opinion. Contractors have been running this experiment in public, and four threads I read this week converge on one uncomfortable finding: for a lot of people, leaving does not change the work at all.

Start with what you are actually selling

Every argument about which platform is better collapses into one fact: you are selling hours. Not deliverables, not a product, not a business that compounds while you sleep. Hours.

That framing kills a lot of bad reasoning. A platform is not a company you join, it is a buyer for inventory that is finite and does not carry over. An hour spent reading a guideline doc for platform number four is an hour you did not bill anywhere.

It also means the most important fact about any project is not the headline rate. It is whether the project pays for time or pays for tasks.

Time based projects pay for hours logged, usually with a cap on how many hours a task may take. Your risk is the cap.

Task based projects pay per completed and approved unit. Your risk is everything: how long the task takes, whether the tool lags, whether the reviewer approves it, whether the guideline changed between your submission and the review.

Task based work moves approval risk from the buyer to you. Read it as a signal about how much a project trusts its own instructions. When the specification is clean, buyers are comfortable paying for time. When it is a moving target, paying per accepted unit lets the buyer stop paying for the confusion they created.

The thing nobody told you: the client follows you

Here is the finding that should change how you think about switching, and I had not seen it stated plainly anywhere.

In a Mercor workers thread, a contractor described leaving for Handshake and being offered the same project, from the same client, for about a dollar more per hour. Others in that thread and a related one describe the identical pattern: one client running one project simultaneously across Mercor, Handshake, and Outlier, pay differing by a couple of dollars, tasks recognizably the same work. One contractor noted that when tasks dry up on one platform they dry up on all of them, because it is a single client queue underneath.

That dismantles the usual escape plan. When you switch platforms in frustration, there is a real chance you are renting the same work from a different landlord. The chaos you are fleeing often originates with the lab that commissioned the project, not the marketplace that staffed it.

Which means the honest question is not “is there a better platform.” It is “is there a better project,” and that question has a completely different answer.

What contractors report about the platforms themselves

Three things showed up repeatedly across these threads, and none of them are what people expect.

The access and pay relationship is inverse, and it is steep. One contractor tested five platforms and summarized it in a line worth memorizing: high pay means harder and more selective, easy access means much lower pay. His own numbers ran from about a dollar per task for basic audio evaluation up to roughly $85 an hour for specialized legal work, on the same resume. Every platform you can join this afternoon sits at the bottom of that curve.

Mercor’s chaos is relative, and multi platform contractors rank it well. This surprised me. Several experienced contractors independently rated Mercor first on organization, naming the per domain management and project Slack channels specifically, while criticizing its pay and volatility. One said they would take a pay cut to have Mercor’s project management everywhere. Your frustration is real. It is also, apparently, the good version.

The mechanics differ more than the rates do. Contractors on one client’s project across two platforms report very different effective earnings purely from timer rules: one platform requires the timer stopped and restarted at every submission, logs no time during mandatory training videos, and takes quality screenshots after the clock stops. The other lets it run continuously. Same tasks, same client, about two dollars an hour apart on paper, and the contractor concluded the higher nominal rate lost. Another described three day review latency during which no further tasking was possible, capping a good rate at roughly two hours of real work.

Nominal rate is the number you compare. Effective rate is the number you get paid.

A note on sourcing: everything in this section is contractor testimony from public forums, not something I verified myself. I am labeling it as such because that is the deal here. Where it matches my own experience across ten plus Mercor projects I say so.

Share

Mercor and Handshake AI, by the numbers

Mercor pays more at the top. Domain experts at frontier labs reach $175 to $200 and above per hour, mid tier roles $90 to $150. Handshake clusters tighter, mostly $75 to $125. A genuinely senior resume makes Mercor’s ceiling worth the friction.

Handshake is steadier. Structured part time blocks, typically 10 to 20 hours a week. Mercor is spiky, with a one to six week wait after acceptance and no choice of assignment.

They screen differently, and this decides which fits you. Mercor runs a 45 to 90 minute AI video interview that probes your resume hard and targets senior professionals. Handshake runs shorter human led interviews and openly recruits PhD students, postdocs, and recent graduates. Early career, Handshake. Senior specialist, Mercor.

Both cap your hours. Handshake also carries an undisclosed weekly earnings ceiling, and in May 2026 one large project paid out between 20 and 50 percent of logged hours. A nominal $60 to $100 an hour can become an effective $8 to $25 once a cap bites.

One hard eligibility fact. Handshake AI requires US work authorization. F-1 students may qualify through CPT or OPT, STEM OPT is excluded, and only a minority of postings are open worldwide.

If that rules you out, read this part carefully. Most of you are not in the US, so for you the sentence “hold Mercor and Handshake” is not advice, it is a locked door. Three things still apply. The two queue rule is about structure, not about those two names: your second queue is whichever platform actually hires from your region, and the logic for choosing it is identical. Everything below the paywall is platform neutral, because the filter, the timer questions, and the drop rule describe mechanics that every one of these marketplaces runs. And Handshake is not entirely shut: its broad fellowship track is open worldwide, which is the one door on that platform I would send a non US reader to. I am testing the platforms that do not require US work authorization now, and that roundup is the next free issue.

So: hold two queues, whichever two your passport permits. Replace neither.

And if you have decided Handshake is your second queue, do not paste your Mercor resume into it. The two platforms reward opposite things, and the profile that got you through Mercor’s funnel is close to the worst version of you that Handshake can see. Below, I walk through the conversion.

Below the paywall:

• How to convert your Mercor profile into a Handshake one, field by field, and the single setting that blocks most non students from registering at all

• The contractor who registered with ten platforms, and what exactly one of them was paying her

• The real waiting times contractors report, platform by platform, and why that is the number that kills the scatter strategy

• My seven question filter for accepting or declining any project, including the contract clause that should end the conversation

• How I allocate my own hours right now, and the mechanical rule that decides when I drop a project

• The ten hour test budget, if you insist on trying a third platform anyway

• What the sieve actually selects for, and why breadth is the expensive mistake

Read more

My inbox this month is one long complaint about Mercor. The queue goes quiet for three weeks. The matching sends a radiologist a music-tagging task. Nobody tells you why. I broke down the mechanics in Why Your Mercor Queue Went Quiet, and the mail I got back was mostly people asking the same question: what else is there?

So this week I went to the other large AI-data employer: Handshake AI. Ten roles, every URL opened and checked by hand on the morning of August 21, 2026.

Two things before the list, because I’d rather lose your click than waste your weekend.

Eight of these ten are US-only. Handshake’s own program page requires participants to be US-based with valid work authorization (F-1 students may qualify under CPT or OPT; STEM OPT is excluded). I’ve labeled the region on every single role. Two are open worldwide.

Remote AI jobs for data and quantitative people

Handshake AI pays domain specialists to produce, grade, and stress-test the material that frontier models train on. For quantitative people that generally means building problems, checking model reasoning, and flagging where it breaks.

Statistician — grade and correct statistical reasoning that AI models produce, and write the problems they get tested on. United States. Remote, part-time, hourly. ✅ Verified — applied 8/21. Strong fit if: you’ve done real applied statistics — study design, inference, a defensible p-value — and you can explain why a wrong answer is wrong.

AI Evaluation Specialist (Canada) — score model outputs against a rubric and document the failure cases. Listed for Canada; the posting metadata shows worldwide. Handshake publishes this role at up to $40/hour — the lowest-paid role on this list, and the one with the widest door. Confirmed live 8/21. Strong fit if: you want the fastest realistic entry point into AI work and you’re genuinely careful — this is a judgment job, not a clicking job.

Data Expert — structure, label, and quality-check datasets used for model training. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you’ve been the person who cleans the messy spreadsheet before anyone can analyze it, and you have a domain you know cold.

Remote AI jobs for writers, editors, and creatives — no coding required

This is the part of the AI labor market almost nobody tells non-technical people about. Models need taste, prose, and judgment, and none of those come from engineers.

Technical Writers — write and correct technical documentation and explanations that models learn from. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you can explain a complex system in plain sentences and you’ve shipped documentation someone actually used.

Video Editors — edit, annotate, and assess video so models learn what a competent cut looks like. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you edit professionally in Premiere, Resolve, or Final Cut and can articulate why one cut works and another doesn’t.

Music Professional — evaluate and annotate music and audio for model training. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you’re a working musician, producer, or audio engineer — session credits and a trained ear count more here than a degree.

AI Tastemaker — judge which model output is better when both are technically correct. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you have defensible aesthetic judgment in a real field — design, editorial, film, fashion — and can defend a preference in writing.

Handshake AI Fellow — Human Intuition — the fellowship’s broad track: bring domain intuition to problems models handle badly. Open worldwide — one of only two on this list that is. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you’re outside the US and have been shut out of these roles, or your expertise doesn’t fit a neat job title. This is the door.

Remote AI jobs for licensed professionals and engineers

Credentialed roles pay the most on this platform. Handshake’s published rates run to $300/hour for radiologists and nuclear specialists and $200/hour for physicians, with engineering roles averaging around $106/hour.

Healthcare and Nursing Professionals — apply clinical judgment to medical questions and evaluate model answers for safety and accuracy. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you hold an active RN, NP, PA, MD, or allied license and you’re tired of the only remote nursing work being triage phone lines.

CAD Expert — produce and evaluate CAD work so models learn real mechanical design. United States. Remote, part-time, hourly. Confirmed live 8/21. Strong fit if: you work daily in SolidWorks, Fusion 360, or CATIA and have shipped parts that got manufactured.

How we verify

World Model (world-model.xyz) checks every listing before it runs. On August 21, 2026 I opened all ten of these Handshake AI job URLs and confirmed each one resolves to a live, role-specific posting on Handshake’s own platform — not a 404, not a filled position, not an aggregator copy. Handshake AI passed the company background check: real entity, ~$3.5B valuation, $1B+ ARR, $100M in documented payouts to fellows.

Two limits worth stating plainly. The Statistician role is the only one I applied to myself, so it is the only one carrying the ✅ Verified label; the other nine are labeled Confirmed live, meaning the posting is real and open but I have no application receipt. And Handshake’s job pages render their descriptions via JavaScript that this week’s tooling could not read, so the role summaries above are built from the posting title, the region in the posting metadata, and Handshake’s own published program description — not from quoted job-description text. Pay figures come from Handshake’s official program page and from independent platform reporting, and are labeled as such rather than presented as per-listing comp.

Labels: ✅ Verified — applied [date] means I submitted a real application. Confirmed live [date] means the listing is real and open at source. ⚠️ Unverified means I could not confirm it at source, and nothing in this issue carries that label.

Get the roles that actually match you

I checked ten listings publicly this week, flagged the eight that lock out international readers, and told you about a payment failure that most job newsletters would have left out — because the checking is the product, not the list.

Paid subscribers get that work done for one profile: yours. Tell me your background, your region, and your license or specialty, and each week I send the roles I’d apply to if I were you — with the region trap and the pay-cap risk already screened out. Plus the running month-by-month record of which projects on these platforms are paying on time.

If you are reading this as a free subscriber, you have already learned the high level framework that generated $37,000 across my first four months on Mercor. But applying these strategies in real time requires tactical execution, precise communication, and individual troubleshooting.

When you upgrade to a Paid Subscription to World Model today, you unlock full access to our complete strategy vault and private subscriber benefits:

• Complete Archive Access: Dive into our top converting guides including The Dark Side of Mercor You Should Know Before You Start, How to Pass the Mercor AI Interview, and Every AI Screen After It, I Updated My Resume and Got an Instant Mercor Offer, Hands On Mercor Playbook, and How I Made $37k in 4 Months on Mercor.

• Direct DM Consulting Access: My direct messages are open exclusively for paid subscribers. Get direct one on one support to review your active contracts, troubleshoot bad reviewer feedback, and optimize your portfolio stacking setup.

Over the past four months, I have worked across more than ten Mercor projects, generated over $37,000 in remote earnings, and mapped out the exact operational mechanics of the global AI training market.

In previous installments of World Model, we unpacked how to pass the initial AI voice screening, how to structure your resume to trigger instant client matches, and how to survive the chaotic onboarding sprints that define this ecosystem.Today, in this final episode of the Data Factory series, we are tackling the high level strategy that separates struggling contractors from remote workers earning five figures every single month.

If you treat Mercor as a single job, you will inevitably hit a wall. You will experience sudden project pauses, incompetent team leads, contradictory Slack announcements, and long dry spells where no work is available. To thrive in this space, you must view Mercor not as an employer, but as an engine for stacking projects, leveraging cross project reputation, securing high paying reviewer seats, and brutally optimizing your hourly yield.

Here is the complete operational playbook on how to build a resilient remote income shape, climb into leadership roles, and know precisely when to walk away.

The Invisible Reputation Network: How Projects Actually Talk to Each Other

Most contractors assume that every new project application starts from scratch. They complete the automated voice interview, wait in the candidate pool, and hope a client selects their profile.

Behind the scenes, Mercor operates a centralized reputation layer that tracks your exact performance metrics across every contract you touch. When a project gets paused or canceled by a client, your work history does not disappear.

Internal project records track your output quality, sandbox pass rates, peer review scores, and adherence to submission guidelines. If you rank in the top fraction of a percent on a high difficulty task, that reputation carries over directly to internal project teams.

Strategic Project Leads (SPLs) and Engagement Project Managers (EPMs) regularly bypass public job postings when staffing new initiatives. When a high value client demands elite talent on short notice, project leads pull directly from internal top performer rosters.

The progression follows a direct line: high quality contractor performance triggers an internal quality audit. Reaching the top tier puts your profile directly in front of Engagement Project Managers and Strategic Project Leads, who bypass the general applicant pool to assign you directly to reviewer and leadership positions.

Understanding this system changes how you approach entry level tasks. Your goal on your first project is not just to bill hours; it is to establish a flawless quality score that unlocks direct invites to high tier positions.

Tier 1 (Entry Expert)

• Primary Objective: Zero error rate on sandbox tasks

• Value Unlocked: Cross project quality flag

Tier 2 (Reviewer)

• Primary Objective: Audit expert work, resolve prompt edge cases

• Value Unlocked: Higher hourly floor ($50 to $100+ per hour)

Tier 3 (Team Lead / EPM)

• Primary Objective: Operations, OG creation, backend sourcing

• Value Unlocked: Stable oversight hours and direct client contact

The Fast Track to Reviewer, Team Lead, and EPM Roles

Baseline expert tasks on Mercor can range anywhere from $16 to $30 an hour for general writing, up to higher rates for specialized domain expertise. However, reviewer and leadership positions carry significantly higher compensation, often pushing rates past $100 per hour for senior domain leads.

Reviewers and leads enjoy far greater stability because their hours are tied to management, quality assurance, and project coordination rather than volatile prompt queues.

So how do you transition from a frontline expert to a reviewer or EPM within days?

• Master the First 24 Hours: When a project opens, demand for reviewers spikes immediately as hundreds of new experts submit sandbox entries. In multiple instances, contractors who demonstrated pristine accuracy and high activity during the first 48 hours were promoted to reviewer or Team Lead within a week. Submit your initial benchmark tasks quickly, double check every guideline, and ensure your work requires zero corrective feedback.

• Practice Active Operational Support: Project leads are constantly overwhelmed by repetitive questions in Slack channels. If you read the operational guidelines thoroughly and assist other contractors by answering common onboarding questions, project leads notice. Leadership positions are rarely awarded solely on technical skill; they are given to contractors who reduce administrative chaos for the EPMs.

• Handle Rogue Reviewers Defensively: One of the most frustrating aspects of frontline work is encountering reviewers who use raw ChatGPT outputs to grade human submissions, resulting in wrong feedback or arbitrary rejections. When faced with unfair reviews, never engage in emotional arguments in public Slack threads. Document the exact guideline requirement, cite your sources clearly, and present a concise, neutral appeal to the project lead. Demonstrating calm, evidence based reasoning under poor oversight is often what gets you noticed for promotion above those very reviewers.

Upgrade to Unlock the Vault

If you are reading this as a free subscriber, you have already learned the high level framework that generated $37,000 across my first four months on Mercor. But applying these strategies in real time requires tactical execution, precise communication, and individual troubleshooting.

When you upgrade to a Paid Subscription to World Model today, you unlock full access to our complete strategy vault and private subscriber benefits:

• Complete Archive Access: Dive into our top converting guides including The Dark Side of Mercor You Should Know Before You Start, How to Pass the Mercor AI Interview, and Every AI Screen After It, I Updated My Resume and Got an Instant Mercor Offer, Hands On Mercor Playbook, and How I Made $37k in 4 Months on Mercor.

• Direct DM Consulting Access: My direct messages are open exclusively for paid subscribers. Get direct one on one support to review your active contracts, troubleshoot bad reviewer feedback, and optimize your portfolio stacking setup.

Do not navigate the AI data engine alone. Upgrade to World Model Paid today and turn unpredictable remote gigs into a reliable, high earning system.

Portfolio Stacking: Building a Resilient Remote Income Shape

Read more

Beyond Mercor, this issue adds an Alphabet company paying up to $293K, seven AI product teams hiring designers and PMs, four Handshake AI Fellowship tracks at up to $100/hr, and three Chinese-friendly remote roles. Not one of the 24 requires writing code.

Jump in: Mercor Featured ×9 · AI-company roles ×8 · Handshake AI Fellowship ×4 · Chinese-friendly ×3 · How we verify · FAQ · Go paid

🤖 Mercor Featured — Contract Work at the Frontier Labs

Disclosure: links in this section are referral links; applying through them supports this newsletter at no cost to you.

Long-time readers know the drill: one Mercor profile plus one AI interview matches you to contract work at frontier AI labs. All nine tracks below come from my own accepted applications, August 10–12; three engineering tracks that sent polite no-thank-yous the same days are gone. What’s left is the most non-engineer-friendly Mercor set we’ve ever run: design, law, insurance, audio, and technical writing.

Getting accepted is the easy half: Mercor keeps evaluating you after you’re in, and that review system decides whether your account compounds or quietly dies. The full breakdown is this week’s paid deep-dive, Cat and Mouse: How Mercor Audits You. Read it before your first task, not after your first warning.

New to the AI interview itself? Issue #19’s companion guide covers the format — it rewards preparation.

1. Design Expert — evaluate how well AI performs real-world design work: typography, layout, visual hierarchy, brand systems. Taste is the qualification.

✅ Verified. Confirmed live on Mercor’s public board 8/12. Strong fit if:you’ve spent years at a design studio or leading a brand’s visual identity, and you have opinions about kerning you’re willing to defend. ➤ https://t.mercor.com/etFKO

2. Litigation Expert — practicing litigators evaluating how AI models reason through disputes, procedure, and case strategy. Courtroom judgment, not legal-tech skills, is what they’re buying.

✅ Verified. Strong fit if: you’re a current or recent litigator who can explain not just what wins a motion, but why the tempting argument loses. ➤ https://t.mercor.com/uMf1R

3. Insurance Experts — underwriters, claims professionals, and actuaries teaching AI models how insurance actually works: policy language, risk assessment, claims reasoning.

✅ Verified. Strong fit if: you’ve priced risk or fought claims for a living and can spot the clause everyone else skims past. ➤ https://t.mercor.com/NMLKI

4. Audio Specialist (Speech / TTS) — German — evaluate and shape synthetic German speech: pronunciation, prosody, naturalness. Listed as “Audio Engineer,” but the core skill is a native-level ear.

✅ Verified. Strong fit if: German is your native or near-native language and you notice when a voice assistant’s stress lands on the wrong syllable. ➤ https://t.mercor.com/Ii7GK

5. Audio Specialist (Speech / TTS) — French — same track in French: judge whether AI-generated speech sounds human, and document exactly where it doesn’t.

✅ Verified. Strong fit if: you’re a native French speaker with a background in voice work, language teaching, or audio production. ➤ https://t.mercor.com/MUWGv

6. Mechanical Engineering Writer — Engineering FRQ — write and grade free-response questions that train AI models in mechanical-engineering reasoning. A writing-and-teaching job that happens to require an engineer’s brain.

✅ Verified. Strong fit if: you hold a mechanical engineering degree and classmates begged you to explain thermodynamics the night before the exam. ➤ https://t.mercor.com/pzYjl

7. Aerodynamics Writer — Engineering FRQ — the same free-response track focused on aerodynamics: airflow, lift, drag, the physics of flight, written for AI training rather than a classroom.

✅ Verified. Strong fit if: you studied aero/astro or work in aviation and can write a problem set that’s rigorous without being cruel. ➤ https://t.mercor.com/P9oPW

8. CAD / Mechanical Design Writer — Engineering FRQ — author questions on CAD and mechanical design practice: tolerances, assemblies, design intent.

✅ Verified. Strong fit if: you’ve lived in SolidWorks or Fusion and can articulate why a design choice is right, not just draw it. ➤ https://t.mercor.com/PhpE7

9. Circuit Design Writer — Engineering FRQ — free-response questions in circuit design and analysis. Like the other three engineering-writing tracks: expertise plus prose, not coding.

✅ Verified. Strong fit if: you’re an electrical engineer who enjoys writing the exam more than taking it. ➤ https://t.mercor.com/zX4F9

All nine tracks share the same logistics: fully remote, set your own hours, weekly payouts via Stripe or Wise.

Before you hit apply: what Mercor’s audit watches, what triggers a review, and what gets accounts quietly shelved — Cat and Mouse: How Mercor Audits You. Paid, and the most consequential thing I’ve published about this platform.

🌍 Which AI-Era Companies Are Hiring Non-Engineers Right Now?

This week: an Alphabet company, a GenAI ad platform, a cybersecurity unicorn, and four AI product teams hiring designers and PMs — via RemoteOK and We Work Remotely. Job boards couldn’t be opened directly this week, so every role below was cross-confirmed via search index on August 12 and carries the confirm-before-applying label. Where I couldn’t confirm a canonical URL, none is given — search the role title plus company and apply at the source.

10. Head of Business Operations @ Wing ($235K–$293K, US remote) — Wing is Alphabet’s drone-delivery company: real aircraft, two continents. You’d translate corporate strategy into operational execution. 15+ years expected. Strong fit if:you’ve run business operations at scale and want your spreadsheet decisions to move actual flying robots.

11. Director of Customer Success @ Pencil (US remote) — a generative-AI ad-creation platform used by global brands. Own the CS function as enterprises adopt AI-generated advertising. Strong fit if: you’ve led CS teams in SaaS and can walk a skeptical CMO from pilot to renewal.

12. Marketing Campaign Operations Associate @ Huntress (~$85K, remote) — a managed-cybersecurity company with a strong remote culture. The ops engine behind marketing: campaign builds, workflows, attribution. Strong fit if: you’re the marketer who actually enjoys the HubSpot/Marketo plumbing everyone else avoids.

13. Bilingual Customer Success Manager @ Acuity Insights (remote) — admissions-assessment tools used by universities (you may know Casper). Bilingual CSM supporting higher-ed customers. Strong fit if: you’re fluent in English plus French or Spanish and love the education sector more than the org chart.

14. AI Product Designer @ SlideSpeak (remote, team of 10) — an AI presentation platform, 3M+ presentations generated. First design hire, working directly with the founder; salary plus equity. Strong fit if: you want your design decisions shipped weekly, not routed through three review layers.

15. Product Designer, AI-Driven @ Cloudwalk (remote) — the Brazilian fintech behind InfinitePay, a profitable unicorn rebuilding payments around AI. Design the AI-first user flows. Strong fit if: you’d rather invent the AI-native pattern than copy last year’s dashboard.

16. Product Manager, AI Desktop App @ M3 Software Solutions (~$110K, 100% remote, async) — early-stage startup funded by two SaaS founders ($20M+ ARR elsewhere), building a desktop AI that helps before you ask. First product hire, 0→1. Strong fit if:you’ve shipped as a founder or first PM and can cut scope without cutting quality.

17. Senior Product Designer & UX Researcher @ Stack Influence (remote, 4-day week) — an AI-powered micro-influencer marketing platform. Design plus research in one seat; the four-day week is in the listing title. Strong fit if: you’re a senior designer who interviews users yourself and wants Fridays back.

🎓 Handshake AI Fellowship — Get Paid to Train AI, Up to $100/hr

Handshake’s AI Fellowship pays domain experts to create training content and evaluate AI outputs for frontier labs — remote, asynchronous, no minimum hours, over $100M paid to fellows so far. The catch: US-based with work authorization, and most tracks want graduate-level expertise. All four confirmed via search index on August 12.

18. Data Expert — subject-matter experts in business communication, strategy, and corporate storytelling, teaching models what a good memo or exec summary looks like. Strong fit if: you’ve spent years in consulting, corp strategy, or comms and can grade an argument, not just format it.

19. Psychology Expert (Master’s) — apply clinical and research psychology judgment to AI training: evaluating how models handle human behavior and mental-health nuance. Master’s required. Strong fit if: you hold a psych master’s and want flexible research-adjacent income between clients or semesters.

20. Adversarial Prompt Expert — probe large language models for failure modes: craft prompts that test guardrails, then document what breaks. Red-teaming as a fellowship. Strong fit if: you find the edge case in every system you touch — and can write it up clearly.

21. Biology Expert (Master’s) — biologists evaluating and authoring AI training content in the life sciences. Master’s required. Strong fit if: you have a biology master’s and miss explaining mechanisms more than you miss the bench.

🇨🇳 Chinese-Friendly Remote Jobs — Eleduck

Three roles from eleduck, China’s oldest remote-work community. These expect Mandarin; comp in RMB where stated. Posts were confirmed via search index on August 12.

22. HR — US Tech Unicorn China Team (full-time remote) — a US tech unicorn with 50+ remote staff in China needs one HR owning the full recruiting cycle. Contracted through a Singapore HR entity, 40 hrs/week, flexible hours. Strong fit if: you can hire engineers for a US company without ever entering an office.

23. Head of Product Design — Remote (team in Singapore, no timezone stretch) — a foreign company hiring a product design lead; 5+ years of product design experience. Apply by resume to the email in the post. Strong fit if: you’re a senior designer ready to own design direction, in Mandarin, without relocating.

24. Remote Full-time Product Manager — Requires Fluent English (25K–50K RMB/month) — foreign enterprise in fintech/gaming marketing hiring a full-time remote PM: 3+ years of experience, fluent spoken English as the working language. Strong fit if: you’re a bilingual PM who wants overseas-market pay while staying where you live.

How We Verify

World Model (world-model.xyz) checks every listing by hand before publishing. The 9 Mercor tracks in this issue were personally verified on August 10–12 from the editor’s own account; every submission receipt is in our inbox, and tracks that rejected us were cut. Job boards could not be opened directly this week, so RemoteOK, We Work Remotely, Handshake, and eleduck roles were cross-confirmed via search index on August 12 and carry a confirm-before-applying label. We never label a listing above the evidence we actually hold, and no role repeats a previous issue.

FAQ

Is Mercor legit? Based on firsthand use: yes. Mercor matches domain experts to paid contract work at frontier AI labs, with weekly payouts via Stripe or Wise. I applied to 12 tracks on August 10–12; nine were accepted into review the same days. What newcomers underestimate isn’t getting in — it’s the ongoing quality auditing, which is why we published a full teardown of that system for paid readers.

Do I need to code to get paid AI-training work? No. All 24 roles in this issue are code-free. AI labs in 2026 pay for domain judgment: designers, litigators, insurance professionals, native speakers, engineers who can write, psychologists, biologists.

How much does AI-training work pay in 2026? Handshake advertises up to $100/hr for graduate-level experts. Mercor rates vary by domain — tracks verified in recent issues ran $28/hr (survey work) to $250/hr (employment lawyers). Both pay weekly.

Get Personalized AI Job Recommendations Every Week

I verified these jobs as open myself before recommending them — that’s the free tier, in your inbox every week. If this issue saved you an afternoon of link-checking, subscribe free and get next week’s batch before everyone else.

Paid subscribers get the same verification treatment pointed at their own profile: tell me your background, and each week I send the roles I’d apply to if I were you — via DM plus a customized weekly email. Paid also unlocks the platform deep-dives, starting with this week’s Cat and Mouse: How Mercor Audits You — the audit system every new Mercor contractor should understand before their first task.

Mercor audits are a sample, not a census. Reviewer verdicts swing with the reviewer. And offboarding usually arrives as silence, not as an email. This video walks the four rooms of the enforcement machine in about two minutes, drawn from my own runs across more than ten Mercor projects and time spent on the reviewer side of the queue. World Model (world-model.xyz) covers this platform from the inside; this is Episode 3 of the Inside the Data Factory series.

Why did my Mercor queue go quiet?

Usually one of four mundane causes: a client rebalanced headcount, a budget line closed, a fraud sweep caught bystanders in the net, or one bad audit sample became your whole file. You will almost never be told which one it was. Episode 3 maps each cause, and what the machine is actually sampling when it judges you.

The free half of Episode 3 explains the machine: audit sampling, the model usage police, reviewer roulette, and the anatomy of a silent offboarding. You can read every word of that half without paying.

The paid half is the part that took me three offboardings to learn. Not more vigilance. An energy system:

• The real hours arithmetic for stacking Mercor on a day job, and the weekly cap I refuse to cross

• The 90-minute block schedule that also reads spotless to an audit

• The one-task Zen protocol for submitting without spiraling

• The weekly energy ledger, and the two-strike rule I use to fire a project

• The calm exit protocol for the day the machine decides anyway

Spend ten minutes on r/mercor_ai and you will find the same story told in different fonts. A thread called Gut Punch. A thread called In Need of Some Encouragement. A thread about being offboarded for no reason, where the comment section lands on the sentence that haunts this whole platform: there is always a reason. You just don’t get to hear it.

The accounts were in good standing. The queues went quiet. The email, when there was one, explained nothing. And a room full of strangers is left doing forensic analysis on their own work history.

I’ve onboarded onto more than ten Mercor projects, and I have read the queue from the reviewer side too. Episode 2 mapped the corridor: the band of acceptable speed and quality that metrics decide you’re inside. Episode 3 is what happens when someone decides you left it. The free half of this piece is how the enforcement machine actually works: audits, model-usage policing, reviewer roulette, silent offboarding. The paid half is the part nobody expects: an energy management system. Because once you understand the machine, you’ll see why the contractors who last aren’t the most vigilant. They’re the least depleted.

The four rooms of the machine

1. Audits are a sample, not a census

Every mature project runs a quality apparatus: daily audit dashboards, a quality matrix that grades dimensions of your work, an error lookup tool where your mistakes get catalogued by type. What new contractors miss is that nobody reads everything. Thousands of tasks flow through these projects daily; the audit is a sample.

So the real question is what raises your sampling odds. Being new does. Sitting at either wall of the speed corridor does, because outliers get pulled first. A reviewer flag does. A client spot check landing on your batch does, and that one is pure lottery. Meanwhile the monitoring layer never sleeps: the timer apps log active windows and idle gaps, idle time gets reviewed and deducted weekly, and charging time outside active work is written into guideline docs as a termination offense.

Here is the uncomfortable implication: audits don’t see your average. They see the three tasks that got pulled. Your representative work, as far as the machine is concerned, is whatever you produced in your most tired hour. Hold that thought; it’s the hinge of this whole episode.

2. The model-usage police

Projects that exist to train AI models mostly forbid you from using AI models to do the work, or license it so narrowly that the safe assumption is no. The irony is noted, usually in the same breath as the policy tab.

Enforcement is a stack, not a single tripwire. The monitoring software sees your open windows. The task tools can see paste events and timing patterns. Your prose gets compared against the baseline you set in onboarding quizzes, some of which are one attempt, graded by the client’s own team, with no second chances and no appeal. And somewhere in the pipeline, AI detectors run on work submitted to a company that trains AI. False positives exist. Honest contractors absorb the friction created by whoever botted the assessments last quarter, which is Episode 1’s arms race wearing a badge.

The one free tip I’ll give above the paywall: when a usage rule is ambiguous, ask once, in the public channel, and work to the written answer. That message is both a clarification and a shield.

3. Reviewer roulette

Between your submission and your pay sits another contractor. Which one you draw matters. Which version of the rubric they read matters, on projects where the guideline doc changed twice in one week. What their own metrics look like that day matters most of all, because reviewers work under quotas and error budgets, and reviewers get audited too. The machine audits its auditors, which makes strictness swing in random directions.

Read more

The full written investigation is at the link below. The five patterns are free to read in the preview; the preparation playbook (the 15-minute guideline triage, the defensive paper trail, and the money and data self-defense rules) is for paid subscribers:

Subscribe now

Quick answers

Is Mercor legit or a scam? Legit. Real AI-training work for frontier labs, market rates, weekly payouts. The risk is volatility, not fraud: projects pause, cancel, and re-staff at lower rates with little notice.

Did Mercor get hacked? Yes. A March 2026 breach exposed more than 40,000 contractor files, including government IDs, banking details, biometric interview video, and screenshots captured by monitoring software. Use a dedicated email and a separate browser profile for monitored work.

Why did my Mercor project pause or disappear? Client-lab priorities shifted. The operating unit is the project, not the person; pauses, waves, and silent offboardings are the normal lifecycle, not a judgment of your work.

What is AHT on Mercor? Average handling time per task. Both extremes get flagged: too slow reads as overbilling, too fast reads as low-effort work. Episode 2 of this series covers the corridor in detail.

How much can you make on Mercor? It varies by project mix and hours. I documented $37,000 across four months in early 2026. Nothing about that is guaranteed, and no single project should carry more than about 60 percent of your income.

Last episode I wrote that every Mercor project has a corridor of acceptable speed, that nobody tells you where its walls are, and that people get terminated for hitting either one. Dozens of you wrote back with the same question.

So what’s the number?

I want to answer that properly, because it’s the wrong question in a way that costs people their contracts. And the fastest route to why is a single line I found buried in a coding project’s guideline.

Time tracking was mandatory on every task. And the same document stated, plainly, that pay on that work was not calculated from the tracking at all.

Sit with that for a second. Logging was compulsory on a task where the money didn’t depend on it. Further down, the reason: the project screened for fraud by reading output quality, volume, and time records against each other.

Your time log is not a timesheet

That reframe explains almost everything confusing about speed on this platform.

On an hourly project, working faster does not earn you more. It earns you less. Twenty tasks in ten hours pays worse than twenty tasks in fifteen. So when an ops lead looks at a low average handling time, they are not admiring your efficiency. They’re asking whether the work actually happened, or whether it was skimmed, pattern-matched, generated by a model, or handed to a friend. And when they see a high one, they ask the mirror question: is this person padding hours, or just not good at this?

The upper wall has arithmetic behind it, and the arithmetic belongs to the client lab rather than to Mercor. The lab budgets per datapoint and pays per hour, so cost per task equals your handling time times your rate. That same coding project published both halves: $85 an hour, against a task the guideline sized at roughly one hour. That isn’t pacing advice. That’s the unit price of the dataset, stated in advance. Work at ninety minutes a task and every datapoint you produce costs the lab fifty percent more than the budget it was approved against. Nobody emails you about that. It surfaces as a capacity review you’re not in.

So the corridor is real, and both walls have owners. The upper wall is the client’s unit cost. The lower wall is the fraud model.

There's one more thing the instrument does, and it's the only good news in this episode, so I'll come back to it at the end: handling time is also an input when writers get promoted to reviewer. It's watching for fraud, and it's quietly building a shortlist.

The rules contradict each other across projects

Here’s why “what’s the number” has no answer, and it’s worse than most people assume.

I went back through the billing language on four projects I’ve worked. On one, the rule was blunt: charging time outside onboarding and active task work would end the contract and follow you to future work with Mercor. Sitting and waiting for a task to appear was explicitly not loggable.

On another project, running on the same platform in the same period, reading the documentation and keeping up with Slack were put on the clock as work you were expected to log.

Those are opposite rules. Log your Slack reading on the first project and you’ve committed a terminable offense. Fail to log it on the second and you worked for free, and you also depressed your own handling time in a way that reads as suspiciously fast.

There is no platform-wide billing policy at Mercor. There is a per-project policy, written by whoever stood up that engagement, and the only safe assumption is that your last project’s rules do not transfer. Which means the instinct you built on your first project is not an asset. It’s a liability you carry into your second.

And it gets one layer worse, because the written rule and the enforced rule are not the same rule either. Every project has a special project lead, the SPL, and some are markedly more tolerant than others. The same logged hour that draws a warning under one lead passes without comment under the next. Neither of them changed the document. They’re just different people reading it.

The rates that are arithmetically impossible

Then there’s the case where no amount of calibration helps, because the number was never reachable.

The clearest instance I’ve seen described recently: a project asking contractors to read roughly eighty pages of dense technical material they had never seen, produce a careful analysis, use no AI whatsoever, and finish inside forty-five minutes. The role required a professional doctorate. Contractors ran the obvious numbers. A page a minute is already brisk for technical reading, which leaves zero minutes for the analysis they were actually hired to write.

And the enforcement is not theoretical. One contractor reports being removed from two separate projects for exceeding handling time. The ramp problem compounds it: several describe project managers who allow no settling-in period at all, so the week when you are slowest by definition, your first, is the week you get measured in.

There is a much less frightening version of how those thresholds actually bite, and I’ll give it to you below the paywall, because it’s the single most useful thing I know about this and it changes what you should worry about. But I’m not going to soften the front half. People do get cut for this.

The sieve

There’s a darker reading of all this that circulates constantly among contractors, and it deserves stating plainly even though I can’t prove anyone intended it.

Put the pieces side by side. A rate that cannot be hit honestly. A rule against the one tool that would close the gap. And a contractor pool deep enough that anybody who objects is replaceable by Friday.

Whatever was intended, that combination selects. It filters toward people willing to make up the difference with unpaid time, or with tools they’ve been told not to use. It filters out the people who log honestly and work at human speed. Nobody at Mercor has to have designed that for it to be what the machine does. And the people it selects for are the ones who look, on the dashboard, like the good workers.

If that’s right, the number isn’t a target. It’s a sieve.

So the real question was never what the number is. It’s how you find the number, on a project you’ve never worked, under a lead whose tolerance you haven’t measured, at a rate that may not be reachable, before you’ve logged an hour you can’t take back.

I’ve been paid on time, every week, across ten-plus projects, and I’m still here. So the corridor is survivable. The rest of this episode is how, and it’s the part I charge for, because it took me ten-plus projects and a few offboardings to assemble.

What’s below the paywall:

• What the four numbers on your dashboard actually mean, and which one holds veto power over the other three

• Why the offboarding threat in your project Slack lands far less often than it’s stated, and the single factor that decides whether it lands on you

• How to price a project’s expected pace from documents already in your hands, before you accept one task

• The three moves that work when the rate is impossible, including the question to a reviewer that usually reveals the real bar is lower than what you’ve been producing

• Which parts of a task you can safely automate, and which will get your logged hours stripped

• Which of your two timers your handling time is computed from, and the second time record you’re creating without knowing it

• One thing I do that I don’t recommend, and why I’m telling you anyway

• Whether an AHT offboarding follows you to the next project. A subscriber asked me directly; this is the real answer

• The reading of your handling time that works in your favour, because it’s also an input when reviewer seats get filled

Episodes 3 and 4 build directly on this one, and both are paid.

And paid gets you the thing this newsletter is actually built on. I read job listings the way I just read those four guidelines. Tell me your background, and each week I send the roles I’d apply to if I were you, by DM and in your own weekly email, with what I found when I checked them.

One placement pays for years of this.

Read more