AI labs need code checked by people who have shipped and maintained it. A model can write code that compiles and passes the obvious test, then fall over under real traffic or a bad edge case. Seeing that takes an engineer who has been paged for it.
This listing is a waitlist, not an open position. No project is attached to your application. Applying puts you in the network we draw from when a software engineering project opens. We ask for one thing: a short AI interview about your field, about 20 minutes, that you take once you have applied. We review applicants from time to time, check whether each profile fits the kind of projects we run, and reach out directly with the scope, hours and rate when there is a match. Timing depends on demand, so you may hear from us soon or only after a while, and we will not contact everyone on the list. You commit to nothing by applying.
Work varies by project. Depending on the project you might write programming tasks with reference solutions in your main languages, review other engineers' solutions against a checklist, or grade AI-written code and explanations for correctness, security and maintainability. Hours, scope and rate are set per project and sent to you in writing before you start.
On a project you write realistic engineering tasks and the solution a senior engineer would ship, review other experts' work against an acceptance checklist, and evaluate AI answers for bugs, unsafe patterns and wrong claims about how a system behaves. Reviewers check everything, and you are paid for approved work.
KEY RESPONSIBILITIES Write realistic programming and system design tasks with the solution a senior engineer would ship Review other experts' work against an acceptance checklist and explain what is wrong and why Evaluate AI-generated code and explanations for correctness, security and maintainability Document your reasoning so a colleague could follow it line by line Apply reviewer feedback and revise until the work is accepted Work from public or illustrative code only, with nothing proprietary from an employer or client IDEAL QUALIFICATIONS Professional experience writing and reviewing production code Strong command of at least one mainstream language and its tooling Able to explain a design decision in plain written English NICE TO HAVE Experience with distributed systems or databases Open source contributions On-call or incident response experience Prior work on an AI training or data platform WHAT SUCCESS LOOKS LIKE You apply and complete the short AI interview When a project matches your background we contact you with the scope, hours and rate You decide whether to take it, with no obligation either way Work you do is reviewed and you are paid for approved work.