Training Turk

Interview experiences

What the real interview was like

Short accounts from people who sat AI-training interviews and tests on Mercor, micro1, Outlier and more.

Each one is told in our own words, from a post the candidate shared publicly.

AI trainer applicant, general track

DataAnnotation · Sep 2026 · Data annotation and evaluation

The DataAnnotation assessment asked which of two chatbot replies was better. The applicant later learned each pair came from two different AI systems and wished it had been said up front.

  • Community report, paraphrased
  • 1 round
Read the full experience

How it ran

  1. An assessment of side-by-side response comparisons.
  2. Later saw practice material showing each pair came from different systems.

What was asked

  • Choose the better of two chatbot responses, and explain why.

What the interviewer or test was like

  • No interviewer: written, self-paced tasks.

Tips

  • The two responses may come from different models. Judge each on its merits.

Outcome

Not known when the review was posted.

AI trainer applicant, game design and 3D background

DataAnnotation · Jun 2026 · Data annotation and evaluation

An applicant with game design, programming and 3D experience found the assessment full of technical, niche scenarios rather than everyday chatbot use. No reply ever came.

  • Community report, paraphrased
  • 2 rounds
Read the full experience

How it ran

  1. An application form, including demographic questions.
  2. An assessment built on technical, unusual prompt scenarios.

What was asked

  • Highly technical, niche scenarios instead of typical user requests.

What the interviewer or test was like

  • No interviewer: a written assessment.
  • Did not seem to test everyday reasoning and communication.

Tips

  • Expect specialised prompts rather than everyday chatbot questions.

Outcome

No response after submitting.

Programmer, coding track

DataAnnotation · Jun 2026 · Software engineering

An experienced programmer took the DataAnnotation coding test, which took about three hours. The problems felt easy and were answered in detail, but no reply came two weeks later.

  • Community report, paraphrased
  • 1 round
  • 180 min
Read the full experience

How it ran

  1. Applied after seeing an advert.
  2. A coding test of roughly three hours.
  3. Two weeks with no decision.

What was asked

  • Review functions and explain which are right and which are wrong.
  • A puzzle-style programming problem.
  • Python was the main expected language.

What the interviewer or test was like

  • A self-paced written test with no live interviewer.

Tips

  • Set aside about three hours for the coding test.
  • Do not count on quick feedback.

Outcome

No response two weeks after submitting.

Interviewed recently? Tell us how it went.

We summarise it in a few lines and never publish your name.

Practise for a roleShare your experience

Roles still waiting for a first report

If you interviewed for one of these, your account would help the next candidate.

Community reports are paraphrased from public posts and may be out of date. Platforms change their process often.