What the work involves

You write and answer analytical prompts of the kind a business or research analyst actually faces — reading a small dataset and deciding what it supports, reconciling conflicting figures, working out a break-even, interpreting a trend without over-claiming causation. Two modes alternate. In authoring, you invent a realistic scenario with a defensible single correct answer, then document the reasoning chain and the evidence behind it. In evaluation, you read a model's attempt and annotate where it went wrong: an arithmetic slip, a misread table, a conclusion the data doesn't license, or a plausible-sounding answer built on an invented premise.

The written explanation matters as much as the verdict. Annotations are training signal, so "incorrect" with no diagnosis is worthless — reviewers want the specific step where the reasoning broke and what the correct step would have been. Expect Excel or Sheets for building and checking the numbers in your own items, and a rubric you are expected to apply consistently rather than reinterpret.

What the screen looks for

  • Evidence of real analytical writing in a job — BA, research analyst, technical writer, journalist, editor, translator. Turing names the degree fields it prefers but states outright that strong professional experience can substitute.
  • Arithmetic and data-interpretation reliability under mild time pressure. Percentage change, weighted averages, unit consistency, reading a table correctly.
  • Willingness to mark a fluent, confident answer wrong and say exactly why.
  • Task-authoring instinct: can you build a problem that is genuinely hard rather than merely long?

Logistics

Fully remote and asynchronous, with your own desktop or laptop and stable internet. Volume moves with project demand — some weeks are thin, others come with batch deadlines — so treat it as variable-hours contract work rather than a fixed schedule. Pay for this posting is undisclosed; comparable generalist reasoning work on the platform is typically hourly or per-task, and you should ask for the specific rate and expected weekly volume before committing.