What the work actually is

You are not analysing a company's data; you are manufacturing the analytical problems a model gets wrong and then supplying the reasoning it should have produced. A typical day means reading a dense passage or a table of monthly sales by location and decomposing it into logical blocks; building a constrained scheduling or ordering puzzle with one defensible answer; prompting a model, watching where it fails, and writing an annotation that names the failure precisely. Other tasks lean on research — checking whether a claim in a piece of content survives a few minutes of online verification, and documenting what you found. Turkish matters throughout: some items are authored or reviewed in Turkish, and the point is that reasoning quality must hold up in both languages rather than English work being loosely translated.

What the platform screens for

Turing's screen is analytical before it is linguistic. Expect to be given a small data scenario or a logic puzzle and asked to explain your steps, not just your answer — the usual failure mode is a right conclusion with reasoning that cannot be audited. Bilingual ability is tested as working fluency in both directions, not as a checkbox; Turkish that is fluent but cannot carry technical or statistical vocabulary will show. The rest is craft: whether your written feedback is specific enough to be actionable, whether you can spot the ambiguity in a badly posed question (should we trim the volatile first month? which growth measure — absolute or relative?), and whether you'll hold a considered position when a model argues back confidently.

Logistics and honest caveats

  • Fully remote, contractor engagement — no paid leave, no benefits, extension contingent on performance and project demand.
  • Up to 40 hours/week preferred, with 2–5 hours daily overlapping America/Los_Angeles (UTC-8). From Türkiye that means late afternoon through evening at minimum.
  • You supply your own desktop or laptop and reliable internet.
  • Pay is not disclosed in this listing. Turing typically sets rates per project and per seniority; ask for the band, the unit (hourly vs. per task), and the expected contract length before you accept.
  • No specialised domain background is required. A degree in engineering, statistics, literature, journalism or communications is preferred, and professional writing experience — analyst, editor, translator, technical writer — is treated as a substitute.