What the work actually involves

You are writing the instructions an AI agent follows when it reaches for an external tool — and then checking whether it followed them. A typical task cycle: read an API/JSON schema for a tool action (posting to a Slack channel, initiating a PayPal refund), write or revise the prompt and policy governing when and how that action may be taken, then review model transcripts to judge whether the parameters were correct, the policy was respected, and the response was safe. Expect to run simple SQL queries to sanity-check data behind an issue, document edge cases with a written rationale, and validate that prompts hold up when the locale or language changes. The output is rarely a score on its own; it is a score plus a written justification an engineer can act on.

What the screen is looking for

The stated evaluation is a single 60-minute technical interview. Realistically it probes three things: whether you can read a JSON schema out loud and say what a wrong argument would break; whether you have genuinely drafted operational policy — the kind with definitions, scope, and escalation paths — rather than merely followed someone else's; and whether your judgment holds on ambiguous cases where safety policy and user intent pull in opposite directions. Turing lists 3–6 years across AI operations, content review, QA, product operations, policy, or technical support. That range is broad on purpose; depth in one of those lanes plus credible API literacy tends to matter more than a title match.

Logistics and pay

  • Fully remote contractor assignment, no medical or paid leave.
  • Minimum 4 hours per day, 20 hours per week, with 4 hours overlapping PST — which means early mornings or late nights in most of the eligible regions.
  • Initial contract of 3 months, described as adjustable.
  • Hiring is restricted to India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, Brazil, and Mexico.

Pay is not disclosed in the listing. Turing's freelance rates vary considerably by project and region, so treat any figure you have seen quoted elsewhere as unverified and ask directly during the technical interview.