Coding Jobs That Train AI: What Software Engineers Do on These Projects
Updated · 2 min read
AI coding assistants improve by learning from code that people have written, tested and judged. That has created a category of remote work for software engineers that sits somewhere between freelancing, code review and competitive programming.
The kinds of tasks
- Solving problems — writing correct, well-explained solutions to coding problems the model gets wrong.
- Reviewing model code — finding bugs, security flaws and bad practices in AI-generated code, then explaining them.
- Real-repository tasks — fixing issues or adding features in actual codebases, often open source, so the model learns from realistic work.
- Designing tests — writing test cases and problems that expose subtle failures.
Who gets hired
Projects look for engineers with strong fundamentals in a particular language or area: backend services, security, databases, GPU programming, front-end frameworks. Competitive programming experience helps for algorithmic work; open source maintainers are recruited for repository work. Listings such as 'Competitive Coder', 'GitHub Contributor' and 'Open Source Contributor' in the software engineering category are typical.
What's different from normal engineering work
You explain more. A fix is only half the task; the reasoning behind it is what the model learns from. You also work on short, self-contained problems more often than on long projects, and quality is measured closely.
Screening
Expect a coding assessment rather than a résumé screen. Write clean, idiomatic code, handle edge cases, and explain your approach briefly. Using an AI assistant during a test that forbids it is usually detected and ends the application.
What a strong submission includes
- Correct, readable code that follows the language's conventions.
- Handling of edge cases, with a short note on which ones you considered.
- Tests where the task allows them.
- A brief explanation of the approach and any trade-offs.
Reviewers often value the explanation as much as the code, because that reasoning is what the model learns to imitate. Two or three clear sentences are usually enough.
Common reasons submissions are rejected
Solutions that pass the visible tests but fail hidden ones, code that ignores the task's constraints (such as a required library or version), missing explanations, and anything that looks generated by an AI tool when the task forbids it.
How the pay compares
Rates for coding work on AI projects vary with the difficulty of the tasks and the depth of expertise required. Specialised areas such as security, systems programming and GPU work tend to pay more than general scripting. The software engineering category shows the ranges employers are publishing now.
Common questions
Do I need machine learning experience?
No. These roles need software engineering skill. ML experience is a bonus for a few specialised projects.
Which languages are most in demand?
Python, JavaScript/TypeScript, Java, C++, Go and Rust come up often, along with SQL and CUDA for specialised work.
Open Software & IT roles
39 listings hiring now, each with its pay shown.
