Skip to content
aitrainer.work - AI Training Jobs Platform
Industry Analysis

The AI Training Labor Market (2026): A Cross-Platform Analysis of 1,615 Job Listings

We coded 1,615 active AI training job listings across 6 platforms. What each platform discloses about interviews, hours, and contract length varies sharply.

By Pietro R., aitrainer.work | Source: aitrainer.work proprietary data |
The AI Training Labor Market (2026): A Cross-Platform Analysis of 1,615 Job Listings β€” aitrainer.work

Abstract. We conducted a structured-data coding study of 1,615 active job listings across six AI training platforms: Mercor, Micro1, SME Careers, Turing, AfterQuery, and Alignerr. Each listing's prose description was coded for three attributes: interview requirement, weekly-hours commitment, and contract duration. Cross-platform comparison of these attributes has not previously been published; each platform discloses only its own listings, with no standardized reporting across competitors. We find substantial variation between platforms on every measured attribute, most notably in weekly-hours commitment: only a disclosed floor of at least 35 hrs/week, not merely a listing that mentions "up to 40," counts as full-commitment here (see Methodology), and on that basis Turing leads at 30% (46/153) while Mercor sits at 8% (14/168) and Micro1 at 0% (0/27). We report descriptive statistics with sample sizes throughout. No significance testing was performed, and findings should be read as descriptive, not inferential.

Key takeaways for job seekers

  • Interviews: SME Careers, Mercor, and Micro1 require one on essentially every disclosed listing. Turing skips a live interview on about 1 in 7.
  • Hours: Turing (30%) discloses the most listings with a genuine β‰₯35 hrs/week floor. Mercor (8%), AfterQuery (2%), Alignerr (0%), and Micro1 (0%) are, by disclosed hours, overwhelmingly part-time or flexible.
  • Watch "up to X hrs/week" language: a ceiling near 40 is not the same as a commitment near 40. Alignerr's listings almost universally state a "10–40 hrs/week, flexible" range β€” a wide range with a low floor, not a full-time role, even though the number 40 appears in nearly every one.
  • Contract length: varies more by domain than by platform. Turing's Business roles average 12 weeks vs. 4.7 weeks for Finance; Mercor's Voice Acting roles average 26 weeks.

Methodology

Population and sampling frame. The dataset comprises all listings marked active on each platform's public jobs board as of July 22, 2026, at the time of coding, including each platform's separately-tagged full-time listing pool where one exists (see note below). This is a census of active listings, not a random sample of a larger population: the "population" is the set of jobs each platform chose to keep posted on that date. Coverage per platform: Mercor (n=484), Micro1 (n=530), SME Careers (n=209), Turing (n=239), AfterQuery (n=108), Alignerr (n=45); total N=1,615.

Coding procedure. Three fields, interview requirement, weekly-hours commitment, and contract duration, were coded from each listing's description text via pattern-based parsing calibrated to each platform's phrasing conventions, with every coded value linked to the verbatim source sentence it was derived from. This traceability requirement, every published data point resolves back to a quoted sentence in a real, currently-live listing, is what distinguishes this from an unverifiable survey claim. A random sample of coded values was manually cross-checked against source listings prior to publication.

Missing-data handling and the disclosure threshold. Not every listing states every fact in its description; a field is coded as missing, not "false" or "zero," when the source text is silent on it. We report percentages only where the disclosed (non-missing) sample for that platform Γ— field cell is n β‰₯ 10. Below that threshold we report the finding as insufficient sample rather than publish a number, and we state sample size (n) alongside every percentage in this piece, in the text itself, not only in a methodology footnote, because a rate without its denominator is not a verifiable claim.

Operational definitions used throughout. "Full commitment" = a weekly-hours floor (minimum, not maximum) disclosed in the listing's prose as β‰₯35 hrs/week. We deliberately did not define this as "ceiling β‰₯40," an earlier version of this analysis: many listings state a wide range like "10–40 hrs/week, flexible," where the number 40 appears but the actual required commitment could be as low as 10 hours. A ceiling near 40 is not evidence of a full-time role; only a floor near 40 is. "Interview required" = the listing's description states a live interview step (human or AI-conducted) as part of selection, as distinct from an automated challenge or assessment with no interview component. "Contract duration" = the stated or inferable length of the engagement in weeks, broken out by platform-assigned domain category where domain-level n β‰₯ 10.

A note on the "Full-time" employment-type tag (click to expand)

Three platforms in this sample (Mercor, Micro1, AfterQuery) apply a structural employment_type: "Full-time" tag to a subset of their listings, separate from the prose weekly-hours field this piece measures. We checked whether that tag reliably predicts β‰₯40 hrs/week by cross-referencing every tagged-"Full-time" listing against its own prose. It does not, on two of the three platforms: of Mercor's 17 active "Full-time"-tagged listings, 11 state an explicit weekly-hours range in prose, and only 3 of those 11 state β‰₯40 hrs/week, the other 8 state 20–35 hrs/week despite the tag. Of AfterQuery's 6 "Full-time"-tagged listings, 2 state hours in prose, and both state 10–20 hrs/week. None of Micro1's 35 "Full-time"-tagged listings state weekly hours in prose at all. Because the tag and the prose disagree this often, we did not treat the tag as a stand-in for the weekly-hours field anywhere in this piece; Finding 2 reports only what listings say about hours, not how any platform labels the role.

Finding 1: Interview Requirements

The clearest cross-platform divergence is in interview requirements. SME Careers requires an interview on 100% of listings disclosing the fact (96/96), and Mercor and Micro1 both show 100% as well, on smaller disclosed samples (40/40 and 14/14 respectively). Turing is the outlier at 85% (68/80): approximately 1 in 7 disclosed Turing listings explicitly route candidates around a live interview step in favor of an automated review. One Turing listing states: "Shortlisted candidates will be sent automated analytical challenges. Once you clear them, you are ready to go!" A representative SME Careers listing, by contrast, reads: "Selection process involves an AI interview, a domain-specific task, and an interview with a recruiter."

Platform % of listings requiring an interview Sample size (n)
SME Careers100%96
Mercor100%40
Micro1100%14
Turing85%80

AfterQuery and Alignerr didn't clear the n=10 disclosure bar for this field in the current sample, so we're not publishing a percentage for either. It's a gap we'll revisit as more of their listings disclose the process in prose.

Finding 2: Full-Time vs. Part-Time Commitment

The largest effect size in the dataset is commitment structure (see Methodology for the β‰₯35 hrs/week floor definition of "full commitment," and why we don't use a ceiling like "up to 40 hrs/week" for this). Turing leads at 30% full-commitment (46/153 disclosed), versus Mercor at 8% (14/168). Alignerr and Micro1 both disclose 0% full-commitment (0/36 and 0/27 respectively); AfterQuery sits at 2% (1/41). These figures include each platform's "Full-time"-tagged listing pool, coded the same way as every other listing in the sample (see the Methodology note on that tag above).

Bar chart: share of listings with a disclosed floor of β‰₯35 hrs/week by platform. Turing 30% (n=153), Mercor 8% (n=168), AfterQuery 2% (n=41), Alignerr 0% (n=36), Micro1 0% (n=27).
Platform % full-commitment (β‰₯35 hrs/week floor) Sample size (n)
Turing30%153
Mercor8%168
AfterQuery2%41
Alignerr0%36
Micro10%27

In practice this means Mercor, AfterQuery, Alignerr, and Micro1 are, by disclosed hours, overwhelmingly part-time or flexible-hours marketplaces, while Turing is the only platform in the sample where a genuine near-full-time floor shows up in a meaningful share of listings, and even there it's a minority (30%) rather than a majority. SME Careers didn't clear the n=10 bar for weekly-hours disclosure in the current sample.

Alignerr deserves a specific note, because its raw numbers look dramatic and are not. An earlier pass at this analysis used "ceiling β‰₯40 hrs/week" as the full-commitment test and reported Alignerr at 94%. That number was an artifact of phrasing, not a signal about Alignerr's actual roles: 34 of Alignerr's 36 disclosed listings state a range in the form "10–40 hrs/week, flexible" or "Flexible hours, 10–40 hours/week" β€” nearly identical boilerplate repeated across almost every listing on the platform. The number 40 shows up because it's the top of a wide, flexible range, not because the role requires anywhere close to 40 hours. Once the test requires a floor near 40 rather than just a ceiling that touches it, Alignerr's rate drops to 0%. Turing is affected by the same pattern to a lesser degree: 74 of the 120 listings that would have counted under the old ceiling-only test turn out to state a similarly wide range (for example, "at least 4 hours per day and minimum 20 hours per week... we have 3 options of time commitment: 20 hrs/week, 30 hrs/week or 40 hrs/week"), and are correctly excluded here. Mercor's 14 qualifying listings, by contrast, mostly state a single fixed number ("40 hours per week," "35 hours/week") rather than a range, which is why its figure barely moved (8% under both definitions).

A caveat this finding still needs: this measures what platforms wrote in listing prose, not verified hours actually worked. A plausible alternative explanation is a difference in listing convention rather than a difference in actual work structure: Turing's listings read like traditional staff-augmentation postings, where stating a specific weekly-hours floor is standard boilerplate, while Mercor's, Alignerr's, and Micro1's listings more often read like task-based or flexible-engagement postings, where a genuine floor is often left unstated (or stated as a wide range) even when the underlying work is substantial for some workers. The gap could reflect real differences in how work is structured on each platform, differences in what each platform's template asks writers to disclose, or both. This dataset can't distinguish the two, and neither interpretation should be treated as settled by these numbers alone. Separately, Micro1's 0% figure should not be read as "Micro1 has no full-time roles": its disclosed sample is small (27 of 530 listings, 5.1%) and concentrated in one listing type (bilingual language-review postings at 10–15 hrs/week); it reflects what the platform's listings state about hours, not a verified count of full-time headcount.

Finding 3: Contract Duration by Domain

Contract duration is better explained by domain than by platform alone. On Turing, the only platform with enough domain-level disclosure to break duration out by category, mean contract length ranges from 4.7 weeks for Finance (n=10) to 12 weeks for Business (n=15), with Software Engineering, Turing's largest category by volume, averaging 9.8 weeks (n=50). On Mercor, only one domain cleared the n=10 threshold: Voice Acting, at a mean of 26 weeks (n=26), more than 2x the longest Turing domain measured, indicating Mercor's voice-acting engagements skew toward sustained rather than project-based work. AfterQuery's sole qualifying domain, Data Science, averaged 4.5 weeks (n=16).

Bar chart: average contract duration in weeks by platform and domain. Mercor Voice Acting 26 weeks (n=26) is the outlier; Turing Business 12 weeks, Software Engineering 9.8 weeks, STEM 9.2 weeks, Languages 7.8 weeks, Voice Acting 7.2 weeks, Finance 4.7 weeks; AfterQuery Data Science 4.5 weeks.
Platform Domain Avg. contract length Sample size (n)
MercorVoice Acting26 weeks26
TuringBusiness12 weeks15
TuringSoftware Engineering9.8 weeks50
TuringSTEM9.2 weeks19
TuringLanguages7.8 weeks16
TuringVoice Acting7.2 weeks13
AfterQueryData Science4.5 weeks16
TuringFinance4.7 weeks10

Finding 4: Disclosure Rates as a Signal

The missing-data pattern is itself a finding, not just a methodological caveat. Interview process fails to clear the disclosure threshold on AfterQuery and Alignerr; weekly-hours commitment fails to clear it on SME Careers; contract duration clears it on only a minority of domains across every platform except Turing. Turing is the only platform in the sample whose active listings cleared the nβ‰₯10 disclosure bar on all three coded fields. Whether that reflects a deliberate transparency practice or simply more verbose listing templates, the practical effect for a candidate is the same: Turing listings currently give a reader more machine-codable information to evaluate before applying than the other five platforms in this sample.

Disclosure scorecard: which platforms clear the nβ‰₯10 sample threshold for each coded field
Platform Interview requirement Weekly hours Contract duration
Turing βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10
SME Careers βœ“ cleared nβ‰₯10 βœ• below nβ‰₯10 βœ• below nβ‰₯10
Mercor βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10
Micro1 βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10 βœ• below nβ‰₯10
AfterQuery βœ• below nβ‰₯10 βœ“ cleared nβ‰₯10 βœ“ cleared nβ‰₯10
Alignerr βœ• below nβ‰₯10 βœ“ cleared nβ‰₯10 βœ• below nβ‰₯10

βœ“ = disclosed sample cleared the nβ‰₯10 threshold for that field in this dataset; βœ• = below threshold, reported as insufficient sample rather than a percentage.

Limitations

This is a cross-sectional snapshot of active listings on a single date (July 22, 2026), not a longitudinal study; platforms' practices may shift as listings rotate. The coding relies on pattern-based parsing of prose that was not written for machine readability, so per-listing miscoding is possible despite the source-sentence traceability check. The nβ‰₯10 disclosure threshold and manual spot-check were both applied specifically to bound that risk before publication, not eliminate it.

Three further limitations apply specifically to the percentages in Findings 1 and 2. First, this measures what a listing's prose states, not verified real-world practice; a platform's disclosed rate can move for reasons unrelated to actual hiring behavior, including changes to a listing template's wording, and (as noted in Methodology) a platform's own structural "Full-time" tag does not reliably agree with its own prose on two of the three platforms that use it. Second, the weekly-hours field itself required a definitional correction during this analysis: an initial pass counted any listing whose stated range touched a ceiling of 40 hrs/week as "full-commitment," which produced a misleading 94% figure for Alignerr driven almost entirely by one repeated "10–40 hrs/week, flexible" phrasing pattern (see Finding 2). The published figures now require a disclosed floor of β‰₯35 hrs/week instead; we flag this because the same class of error, treating a wide range's ceiling as a commitment signal, could in principle recur in future extraction passes on this or other fields, and readers relying on cached or screenshotted versions of this piece from before this correction should treat the ceiling-based Alignerr and Turing figures as superseded. Third, disclosed-sample percentages describe only the subset of listings that stated the fact in prose, and that subset is a minority of each platform's total active listings for interview requirement (SME Careers 45.9%, Turing 33.5%, Mercor 8.3%, Micro1 2.6%, of total active listings) and, for weekly hours, ranges from a minority on some platforms to a majority on others (Alignerr 80.0%, Turing 64.0%, AfterQuery 38.0%, Mercor 34.7%, Micro1 5.1%, of total active listings). If the decision to disclose a fact correlates with the type of role (for instance, higher-touch enterprise roles being described in more detail than high-volume task-based postings), the disclosed subset is not representative of the platform's full active listing set, and the reported percentage describes that subset, not the platform as a whole. Sample sizes also differ substantially by platform (Mercor n=484 vs. Alignerr n=45). Findings describe listing text as published, not verified outcomes for candidates who apply.

Conclusion

Six platforms competing for the same nominal pool of AI training talent show measurably different practices once compared on a common set of coded fields rather than read one careers page at a time. SME Careers, Mercor, and Micro1 gate essentially every disclosed listing behind an interview; Turing routes roughly 1 in 7 disclosed listings around one entirely. On weekly hours, no platform in this sample is majority full-commitment once "full-commitment" requires a genuine floor near 40 hrs/week rather than just a range whose ceiling touches it: Turing leads at 30%, and Mercor, AfterQuery, Alignerr, and Micro1 all disclose single-digit or 0% full-commitment rates. Contract duration varies more by domain than by platform, with a roughly 2x spread even within the single best-sampled platform. A candidate comparing "AI training jobs" across these six sites today is, on several measurable dimensions, comparing structurally different labor arrangements that happen to share a category label, and reading the actual hours language in a listing, not just a "Full-time" tag or a number that happens to be 40, is the difference between an accurate and a misleading picture of the commitment involved.

Sources

  1. aitrainer.work proprietary listing-facts extraction, active listings as of July 22, 2026: Mercor (484 listings analyzed), Micro1 (530), SME Careers (209), Turing (239), AfterQuery (108), Alignerr (45).
  2. Per-field sample sizes (n) reported inline throughout this piece reflect only listings whose description text disclosed that specific fact; platforms/fields below n=10 are reported as "insufficient sample" rather than a percentage.

Related reading

Best AI training platforms compared: full reviews of every platform in this analysis.

Turing job listings: see the underlying active roles behind Turing's numbers above.

Mercor job listings: see the underlying active roles behind Mercor's numbers above.

Pietro R., founder of aitrainer.work

Pietro R.

MSc Human-Computer Interaction | Founder & Product Owner

Pietro is the founder and technical lead of aitrainer.work. He builds and maintains the platform's data pipeline, certification infrastructure, and editorial standards.

Comments

Loading comments…
πŸ’¬

Share your thoughts on this article

Sign in to join the discussion.

Sign in to comment