Senior Software Engineer: C# (LLM Evaluation & Repository Validation)

What you'll do

The project builds verifiable software-engineering tasks from the histories of public repositories, with humans in the loop, so that LLMs can be trained and tested on realistic bugs. Your part is the hands-on engineering around that: making a repository runnable, judging whether an issue is a good test for a model, and checking whether the tests are any good.

From the ad:

• Analysing and triaging GitHub issues across popular open-source libraries
• Setting up and configuring repositories, including Docker and environment automation
• Evaluating unit test coverage and quality
• Modifying and running codebases locally to see how an LLM performs at bug fixing
• Working with researchers to find repositories and issues that challenge models
• Possible opportunities to lead a team of junior engineers

The ad describes the target as tech-lead level, though the minimum stated is 3+ years.

Who fits

• 3+ years of overall experience and strong C#
• Git, Docker and basic pipeline setup
• Ability to navigate complex codebases and run, modify and test real projects locally

Nice to have: open-source contribution or evaluation, past LLM research or evaluation work, building or testing developer tools or automation agents.

What it pays

The ad does not publish a rate. Turing sets rates per project; see Turing.

Worth knowing

Good:

• Engineering work you can reason about, with real repositories
• Choice of 20, 30 or 40 hours a week
• Possible lead role over junior engineers

Less good:

• Open only to candidates in India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey or Mexico
• At least 4 hours a day with 4 hours of overlap with Pacific Time
• No rate and no stated contract length
• Contractor assignment with no medical or paid leave
• A long-running posting (first listed in July 2025)

How hiring works

About 75 minutes of evaluation: a 60-minute technical interview and a 30-minute technical and cultural discussion.

About this listing

Posted by Turing in July 2025 and read on 18 October 2026. Locations, hours and interview format are Turing's own text; the framing is ours. See Turing.