Senior Software Engineer: Go (LLM Evaluation & Repository Validation)

What you'll do

Go projects tend to have tidy module layouts and fast test suites, which makes them good raw material for a benchmark where every task must be reproducible. This Turing project builds verifiable software engineering tasks from public repository histories, with a person validating each one.

Your part of that pipeline:

• Analyse and triage GitHub issues across popular open-source Go libraries
• Configure repositories so they build and test cleanly, including Docker and environment setup
• Evaluate unit test coverage and quality
• Edit and run the code locally to see whether an LLM can fix the bug
• Help researchers choose repositories and issues that are challenging for models

The ad also says there are opportunities to lead a team of junior engineers.

Who fits

• 3 or more years of overall experience and strong Go
• Proficiency with Git, Docker and basic software pipeline setup
• Comfort reading complex codebases and running real projects locally
• Open-source experience is a plus
• Nice to have: LLM research or evaluation history, or having built developer tools or automation agents

The ad calls for tech-lead-level engineers familiar with high-quality public repositories.

What it pays

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

Commitment and location

• At least 4 hours a day and 20 hours a week, with 4 hours of overlap with PST; 20, 30 or 40 hours a week are the three options
• Contractor assignment (no medical or paid leave)
• Locations named: India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, Mexico
• No contract length is stated

Worth knowing

Good:

• The work resembles ordinary maintainer chores, so Go experience transfers directly
• Remote, with weekly hours you choose from three options
• Leadership opportunities are mentioned

Less good:

• No pay rate published
• Pacific time overlap is a heavy constraint for many of the listed countries
• Limited to the countries named
• No benefits or paid leave

How hiring works

About 75 minutes in total: a 60 minute technical interview and a 30 minute technical and cultural discussion.

About this listing

Read from Turing's job board on 18 October 2026. It is one of a set of near-identical repository validation roles, each tied to a different language. See Turing.