Mercor and Turing both place credentialed contractors with frontier AI labs, but their DNAs are different. Turing built its business vetting software engineers for full-time remote roles, then pivoted into AI training as the lab spend scaled. Mercor was AI-training-native from day one and built its evaluation engine around a much wider catalog of expertise — not just engineering. That history shapes who each one hires, how the interviews feel, and what the pay tiers look like.
This is the honest comparison: pay, applicant profile, vetting process, and which to apply to first depending on your background.
TL;DR — the verdict
- Mercor pays higher across more domains. Mid-tier $90–$150/hr; top-tier roles for frontier labs hit $175–$200+/hr across software, medical, legal, finance, and PhD-level work.
- Turing's strength is software engineering. Pay clusters $50–$120/hr for AI training contracts; the software-engineering interview is widely considered the most rigorous in the contract-engineer market.
- Mercor's evaluation is AI-led and résumé-probing. A conversational AI agent runs a 45–90 minute interview that follows up specifically on your work history.
- Turing's evaluation is multi-stage and live-coded. For engineering roles: timed coding challenge → live technical interview with a senior engineer → role match. For non- engineering roles, the pipeline is faster and lighter.
- Mercor onboards faster on average. Time from application to first paid engagement is typically 2–6 weeks on Mercor versus 3–8 weeks on Turing.
Pay: where the dollars actually land
Mercor
Mercor's published per-role ranges run $60/hr at the floor to $200+/hr at the ceiling. The mode for accepted contributors is around $90–$120/hr. Top-tier ($175–$200+/hr) is reserved for verifiable senior credentials — practicing physicians, M&A attorneys, senior software architects, audit-partner- level accounting, mathematics PhDs at publication level. See the full breakdown — Mercor review.
Turing
Turing's AI training contracts publish per-role ranges $50–$120/hr. The mode for software engineers is around $70–$100/hr; for senior engineers with niche stack experience (Rust, ML systems, distributed databases) it pushes toward the upper end. Non-engineering domains exist on Turing but are a thinner catalog — Turing's network is engineer-heavy. Payment is typically biweekly. See the comparison with micro1 — micro1 vs Turing.
The ceiling difference
Mercor's top tier is genuinely higher than Turing's for equivalent talent. A senior software engineer with 8 years at a top-tier company and verifiable system-design depth will earn $150–$200/hr on Mercor and $90–$120/hr on Turing. Same engineer, different platforms, ~50% more on Mercor at the top of the band. This is the single biggest reason the senior engineers we hear from end up running both.
Who each platform actually hires
Mercor's core hire
- 5+ years at FAANG-tier engineering, top-tier financial services, major law firm, or research hospital
- Practicing physicians evaluating clinical reasoning in their specialty
- M&A attorneys evaluating contract analysis output
- Audit-partner-level accountants and CFAs for financial reasoning work
- PhDs in mathematics, physics, chemistry, biology, economics for research-grade evaluation
Turing's core hire
- Software engineers with verifiable production code (FAANG and FAANG-adjacent, well-funded startups)
- Specialized engineering stacks: ML engineering, distributed systems, embedded, security, mobile
- Some data scientists and ML researchers with applied work history
- A growing but thinner catalog of non-engineering SMEs — finance, healthcare, legal — at lower rates than Mercor
Application process: what to expect
Mercor
Apply at mercor.com — upload résumé, get a scheduling link within 1–3 days, run a 45–90 minute AI-led video interview. The AI agent probes your résumé with follow-up questions like "tell me about the specific decision you made when…" — looking for verifiability, not credentials-as-shorthand. Placement decisions in 5–10 business days.
Turing
Apply at turing.com — submit a résumé and GitHub link. For engineering roles, you'll get scheduled into a timed coding challenge (typically 90–120 minutes, algorithms + system design depending on level). Pass that and a senior Turing engineer runs a 60–90 minute live technical interview. Pass that and you're entered into the Turing talent pool for matching to AI-training contracts. Non-engineering roles skip the coding challenges and go straight to a domain-specific screen.
The Turing engineering vetting is harder than most contract- engineer interviews. Plus side: passing it is a credential in itself. Minus side: the time investment is real (4–6 hours of focused interview time before you've earned a dollar).
Which one should you apply to first?
- You're a senior software engineer (5+ years FAANG- equivalent) → Mercor first, Turing second. Mercor's pay ceiling is higher; Turing as a fallback for engineering-only inventory.
- You're a mid-level software engineer (2–5 years) → Turing first. Mercor's interview leans senior — you'll do better at Turing's structured technical vetting at your career stage.
- You're a non-engineering SME — medical, legal, finance, PhD → Mercor first. Turing has these tracks but the catalog is thinner and the pay tier is lower.
- You're a specialized engineer (ML systems, embedded, security) → both, same evening. Both platforms pay well for rare-stack engineering, and you have low marginal effort applying to the second.
- You don't want to invest 4+ hours in interviews before earning → Mercor. Faster time-to-first-engagement.
Can you run both at the same time?
Yes. No exclusivity at the platform level. Some senior engineers we hear from run Mercor as their primary (higher per-hour rate) and Turing as their secondary (steady weekly hours when Mercor's spot market is quiet). Track hours separately, expect a 1099-NEC from each, and read per-engagement NDAs — those are role- specific, not platform-wide.
The honest weakness of each
Mercor's downside
Spiky placement. After acceptance, you may wait 1–6 weeks for your first paid engagement depending on what labs are sourcing in your niche. You don't pick engagements; the matching engine does. If you need income starting next week, this is a real constraint.
Turing's downside
Long, demanding vetting before you've earned anything. The engineering pipeline (timed challenge + live interview) is 4–6 hours of focused interview time. For senior engineers, the pay tier doesn't fully justify it when Mercor would pay 25–50% more for equivalent work with less interview friction.
How to apply to both efficiently
If you're an engineer: budget a Saturday morning for the application path. Submit to Mercor early (résumé + scheduling link, ~10 min), then submit to Turing (résumé + GitHub + coding challenge, ~2 hours). Mercor's interview lands 1–3 days later. Turing's live technical interview is scheduled separately. Keep your code samples polished and your résumé verifiable.
For interview tactics that work in AI-led screens, see our AI training interview guide. For pay context across the broader market, see the AI training pay breakdown. If you want to compare all four featured platforms at once, the four-way roundup covers Mercor, micro1, Turing, and Handshake AI side-by-side.