What the work actually involves

You are not shipping a product. You are producing the training and evaluation signal that a model learns from. On a typical day that means writing clean, idiomatic JS/TS solutions to prompts, comparing two or more model responses to the same coding task and ranking them with a written rationale, or rewriting a flawed model answer into the version it should have produced. Some batches lean toward eval design — constructing test cases and benchmarks that expose a specific failure mode — and some lean toward SFT dataset authoring, where your code and your annotations become the gold reference. Peer review of other contributors' submissions is part of the job, not an occasional extra.

What the platform screens for

Turing's process is roughly 75 minutes: a 60-minute technical round plus a 15-minute cultural and offer conversation. The technical round probes real fluency in JavaScript and TypeScript — ES6 semantics, async behaviour, type modelling — plus depth in at least one framework or runtime (Node.js, Nest, React, Angular, or Vue). Expect follow-ups that push past your first answer: why that pattern, what breaks at scale, how you'd test it. Just as important is whether you can explain a judgment in writing. Screeners look for rationales that cite a concrete defect (a race condition, an unhandled rejection, a type that permits invalid state) rather than adjectives like "cleaner" or "more elegant".

Logistics

  • Fully remote, contractor assignment — no medical or paid leave.
  • Three commitment tiers: 20, 30, or 40 hours per week, with a minimum of 4 hours per day.
  • Four hours of daily overlap with PST is a firm requirement, not a preference.
  • Initial contract is stated as one month, with start dates moving quickly (the listing says next week). Renewals depend on project volume and your quality scores.
  • Pay band is undisclosed on this listing; rates on Turing's coding work vary by seniority, region, and project, so treat any figure you see quoted elsewhere as unverified.

Who does well

Developers who enjoy code review more than greenfield building. If you can look at two working implementations and articulate precisely why one is safer, more maintainable, or better typed — and write that up in clear English in a few minutes — this work fits. If you find writing rationales tedious, it will grind.