TuringCoding & software eval
Scientific Coding - Mathematics and Python
Pay not published
About this role, in Turing's words
Turing is building one of the most rigorous STEM AI training datasets in the industry. The SciCode project involves creating high-quality scientific coding tasks that are used to train and evaluate frontier AI models. As a SciCode Trainer, you will be directly contributing to cutting-edge AI research by authoring, implementing, and reviewing complex scientific problems across core STEM disciplines.
What you'll do
Responsibilities
- Write scientific problem specifications consisting of one main problem and a minimum of 3 sub-problems, all logically connected and progressively building toward the main problem solution Implement verified golden solutions in Python with complete unit test coverage
- Design discriminative test cases that clearly differentiate correct from incorrect model outputs Run QC validation checks on the Turing Central Task Platform (CTP) including Tier 1 structure checks and Tier 2 quality rubrics Iterate on tasks based on QC feedback to meet Pass@K evaluation criteria across multiple LLM judges (GPT, Gemini, Nemotron)
- Maintain high output quality with a low rework rate, targeting consistent L1 approval on first submission
- Participate in sync calls for reviews, feedback sessions, and project standups during overlap hours
Candidate background
Required Qualifications
- Master's or PhD in Mathematics.
- Strong Python programming skills with experience in scientific computing
- Ability to write rigorous, well-posed scientific problems with clear constraints and expected outputs
- Attention to detail - tasks must meet strict rubrics for well-posedness, test case discriminativeness, scientific correctness, and determinism
- Prior experience in AI data annotation, research, or scientific writing
- Familiarity with LLM evaluation frameworks or coding benchmarks
- Experience with libraries such as NumPy, SciPy, SymPy, or domain-specific scientific tools .
- Published research or academic project experience in a STEM domain Quality Standards
Quoted from selected sections of Turing's posting. The full posting may state other conditions. Read the full posting
A closer look
More context, when you need it.
Full job descriptionThe original posting, in Turing's words
Posted by Turing, reproduced here so you can judge the role before clicking. Original posting ↗
Role Overview:
Turing is building one of the most rigorous STEM AI training datasets in the industry. The SciCode project involves creating high-quality scientific coding tasks that are used to train and evaluate frontier AI models. As a SciCode Trainer, you will be directly contributing to cutting-edge AI research by authoring, implementing, and reviewing complex scientific problems across core STEM disciplines.
Responsibilities:
• Write scientific problem specifications consisting of one main problem and a minimum of 3 sub-problems, all logically connected and progressively building toward the main problem solution Implement verified golden solutions in Python with complete unit test coverage
• Design discriminative test cases that clearly differentiate correct from incorrect model outputs Run QC validation checks on the Turing Central Task Platform (CTP) including Tier 1 structure checks and Tier 2 quality rubrics Iterate on tasks based on QC feedback to meet Pass@K evaluation criteria across multiple LLM judges (GPT, Gemini, Nemotron)
• Maintain high output quality with a low rework rate, targeting consistent L1 approval on first submission
• Participate in sync calls for reviews, feedback sessions, and project standups during overlap hours
Required Qualifications:
• Master's or PhD in Mathematics.
• Strong Python programming skills with experience in scientific computing
• Ability to write rigorous, well-posed scientific problems with clear constraints and expected outputs
• Attention to detail - tasks must meet strict rubrics for well-posedness, test case discriminativeness, scientific correctness, and determinism
• Prior experience in AI data annotation, research, or scientific writing
• Familiarity with LLM evaluation frameworks or coding benchmarks
• Experience with libraries such as NumPy, SciPy, SymPy, or domain-specific scientific tools .
• Published research or academic project experience in a STEM domain Quality Standards
Offer Details:
• Commitments Required : Overlap of 4 hours with PST and 40 hrs/week
• Engagement type : Contractor assignment/freelancer (no medical/paid leave)
• Duration of contract : 8 weeks
• Location : Bangladesh, Brazil, Colombia, Egypt, Ghana, India, Pakistan, Indonesia, Kenya, Nigeria, Turkey, Vietnam
Working with TuringPay, getting started and work, from Turing's own pages
What the platform publishes in general. These are not extra terms confirmed for this particular role.
- Getting paid
- Paid monthly, around the 5th, straight to your bank account, or inside Deel on projects run through Deel. Its help articles disagree on whether that is the 5th calendar day or business day. help.turing.com/articles/9691407757-project-onboarding, help.turing.com/articles/6582454854-what-if-i-haven-t-rec..., help.turing.com/articles/1226770947-project-offboarding
- Before your first paid task
- A short application, with tests on some roles. Turing's review article says an interview is typically required for all roles. Onboarding covers the terms, ID verification with a driver's license or passport, and tax and payment details. help.turing.com/articles/2020987592-apply-for-jobs-at-turing, help.turing.com/articles/9179629201-how-long-does-the-app..., help.turing.com/articles/9691407757-project-onboarding
- How much work
- Review takes from 48 hours to 6 weeks after you finish applying, and the client makes the final choice. No reply within 6 weeks usually means you were not selected. help.turing.com/articles/9179629201-how-long-does-the-app..., help.turing.com/articles/2020987592-apply-for-jobs-at-turing
- Contract
- Depending on the project, the engagement rests on Turing's Terms of Service and a Service Agreement, on Deel, or on a partner that provides the contract. help.turing.com/articles/6582454854-what-if-i-haven-t-rec...
Read on the pages linked above on 23 Sep 2026. Platforms change these terms, so check the linked page before you rely on one.
How does the pay compare?Across Coding & software eval roles, not this role alone
From our own daily reads of every open listing on the platforms we follow, not from Turing's posting. How we count.
Pay across the field: Coding & software eval
Across 394 roles in this field with a stated hourly rate in US dollars, on 14 platforms, the middle half pays $65 to $120 an hour at the top of the range, and the median is $95.
| Platform | Roles | Top of range, per hour |
|---|---|---|
| Alignerr | 137 | $50 to $400 · median $100 |
| micro1 | 46 | $35 to $350 · median $110 |
| Handshake AI | 43 | $47 to $125 · median $80 |
| Meridial (Invisible) | 34 | $22 to $150 · median $60 |
| Mercor | 33 | $60 to $200 · median $105 |
Sources and listing historyWhere this information comes from
This listing's history
- First seen here on 19 Sep 2026, and still on Turing's list when we last read it on 13 Oct 2026.
- Posted by Turing
- First seen by AIPayList
- Last seen live
- Listing ID
- 103650
Keep exploring
More like this
Related field, different requirements. Check each role's own page before you apply.