What the work actually involves

You pick a high-quality public C++ repository and make it reproducible. That means reading the commit and issue history to find a defect with a clean before/after state, writing a Docker environment that builds the project deterministically, reproducing the failure locally, and confirming the existing test suite genuinely distinguishes the broken state from the fixed one. Where the tests are weak — passing on buggy code, or tautological — you say so and either strengthen them or reject the task. A large part of the output is judgment calls: this issue is too under-specified to be gradeable, this one is solvable by string search and will not challenge a model, this one has a hidden dependency on a CI runner that won't survive containerisation.

The C++ dimension matters more here than in most languages. Build systems (CMake, Bazel, autotools), toolchain and ABI pinning, third-party dependency vendoring, and flaky behaviour under different compilers or sanitizers all make environment setup a real engineering task rather than a checklist. Expect to spend meaningful time getting a project to build the same way twice.

What the screen looks for

Turing's screening process is conversational and follow-up heavy. It probes whether you have personally built and debugged large C++ projects from source, whether you can name specific repositories and their build quirks, and whether you can reason about test quality rather than test count. Evidence of open-source contribution or code review at a senior level helps; so does any prior exposure to LLM evaluation or agent tooling, though neither is required. Expect a technical assessment and at least one live conversation where claims get pushed on.

Logistics

  • Fully remote contractor assignment; no medical or paid leave.
  • Initial contract stated as one month, with a start date expected within a week of offer.
  • At least 4 hours per day and a minimum of 40 hours per week, with 4 hours of daily overlap with PST.
  • Hiring is restricted to India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, and Mexico.
  • Pay band is not disclosed in the listing; rates on Turing coding-evaluation projects are typically quoted hourly at offer stage and vary by seniority and region. Treat any figure you see quoted elsewhere as observed, not guaranteed.
  • Some contributors are offered a lead track supervising junior engineers on the same dataset.