Turing is hiring senior Rust engineers to turn real GitHub issue histories into verifiable software engineering tasks that LLMs can be trained and tested against. Day-to-day work is hands-on: Dockerizing repositories, triaging issues, judging test coverage, and running candidate fixes locally to see where models break.

Summary, eligibility guidance and screening preparation are prepared by Sidequest from the platform's posting. Check the source listing before applying.

What the work involves

This is a data-construction role that happens to require real engineering skill. You pick trending open-source Rust repositories, dig through their issue and commit history, and reconstruct a moment in time where a genuine bug existed and a test could prove it fixed. That means pinning the repo at a pre-fix commit, building a reproducible environment (usually Docker), confirming the fail-to-pass test behaves deterministically, and documenting the task so a model — and a human reviewer — can evaluate it unambiguously.

The other half is judgment. You will be asked whether a repository's test suite is strong enough to validate a fix at all, whether an issue is under-specified, and whether a task is hard for the right reasons (real reasoning depth) versus the wrong reasons (missing context, flaky async tests, network dependencies). You collaborate with researchers on repository selection and may lead a small group of junior engineers on task batches.

What the screen looks for

Rust depth that survives follow-ups. Cargo workspaces, feature flags, build scripts, `cargo test` versus integration test layout, `unsafe` boundaries, async runtime differences. Expect probing rather than trivia.
Reproducibility instinct. Can you make an arbitrary repo build and test identically on a clean machine, and explain what you do when it won't?
Evaluation judgment. Distinguishing a valid verifiable task from a trap, and articulating why.
Named repositories. Vague familiarity with "the Rust ecosystem" reads poorly; concrete repos, PRs, and issues read well.

Logistics

Fully remote contractor assignment, roughly 3 months, with 20 / 30 / 40 hrs-per-week options. The floor is 4 hours per day and 20 hours per week, including 4 hours of overlap with US Pacific time — plan your answer on that overlap before the call, because it is checked. Hiring is restricted to India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, and Mexico. No medical or paid leave. Evaluation is about 75 minutes total: a 60-minute technical round plus a 30-minute technical and cultural discussion. Pay is undisclosed on this listing; Turing's Rust bands are typically quoted as an hourly rate at offer stage.

Senior Software Engineer – Rust (LLM Evaluation & Repository Validation)

What the work involves

What the screen looks for

Logistics

Interview prep — 10 questions