Senior Software Engineer – C++ (LLM Evaluation & Repository Validation)

The paradigm of software development is undergoing a permanent transformation. As artificial intelligence models scale in capability, the industry faces a critical engineering challenge: ensuring that Large Language Models (LLMs) can safely, accurately, and robustly reason through complex, real-world source code repositories. Rather than relying on synthetic prompts alone, building reliable AI systems requires rigorous, verifiable evaluation tasks derived from authentic software histories.

Turing—one of the world's fastest-growing AI companies accelerating the advancement and deployment of powerful artificial intelligence systems—is engaging elite C++ software engineers for a high-impact contractor assignment: the Senior Software Engineer – C++ (LLM Evaluation & Repository Validation) role. This opportunity places senior systems developers at the absolute frontier of AI training and evaluation infrastructure.

About the Project and Role

This initiative focuses on building comprehensive LLM evaluation and training datasets explicitly designed to train models on realistic software engineering problems. By utilizing a synthetic approach with a human-in-the-loop, Turing constructs verifiable SWE tasks based on public repository histories, expanding dataset coverage across varied programming languages, complexities, and architectural styles.

As a Senior Software Engineer at a tech-lead level, you will perform hands-on technical work that goes far beyond standard labeling. You will automate development environments, triage GitHub issues, and meticulously evaluate unit test coverage and quality.

Required Skills and Experience

To succeed in this rigorous evaluation role, candidates must demonstrate deep technical maturity and practical systems engineering competence:

• Professional Background: Minimum 3+ years of overall software engineering experience, ideally operating at a tech-lead level.
• Core Language Mastery: Strong, professional experience with C++.
• Toolchain Proficiency: Solid working knowledge of Git, Docker, and standard software pipeline configurations.
• Codebase Navigation: Exceptional ability to understand, navigate, and debug complex multi-layered codebases.
• Local Execution: Comfortable running, modifying, and testing real-world software projects directly on local machines.

Nice-to-Have Qualifications: Previous participation in LLM research or evaluation projects, experience building developer tools or automation agents, and prior contributions to major open-source repositories.

Engagement Details & Work Commitments

This role offers exceptional flexibility as a fully remote contractor assignment. Contributors can choose from three structured time commitment options: 20 hours per week, 30 hours per week, or 40 hours per week, requiring a minimum of 4 hours per day with a 4-hour daily overlap with Pacific Standard Time (PST).

Perks of Freelancing with Turing

• Complete Location Freedom: Work remotely from approved regions including India, Pakistan, Nigeria, Kenya, Egypt, Ghana, Bangladesh, Turkey, and Mexico.
• Cutting-Edge Exposure: Collaborate directly with industry-leading AI labs and top-tier researchers.
• Career Growth: Position yourself at the forefront of AI-assisted software engineering.

Onboarding, Stability, and Access to Tasks

To ensure long-term engagement stability and unlock advanced, high-tier tasks on the platform, new contractors must complete the formal onboarding sequence and successfully log their initial 10 hours of quality work. Meeting this milestone demonstrates workflow reliability, establishes pipeline synchronization, and integrates you smoothly into Turing’s core engineering evaluation network.

The Evaluation Process

Turing maintains a rigorous vetting standard to ensure elite caliber teams. The evaluation process takes approximately 75 minutes total and consists of two streamlined rounds:

1. Technical Round (60 minutes): In-depth evaluation of coding ability, systems design, and debugging proficiency.
2. Technical & Cultural Discussion (30 minutes): Alignment on collaboration standards, remote workflows, and technical communication.