Contract, hourly Location: Remote Hours: 20-30 per week Pay: $20-30/hour, based on experience and ... Immediate ABOUT THE ROLE We evaluate how well advanced AI coding agents solve real engineering ...
Contract, hourly Location: Remote Hours: 20-30 per week Pay: $20-30/hour, based on experience and ... Immediate ABOUT THE ROLE We evaluate how well advanced AI coding agents solve real engineering ...
AI Agent Trajectory Annotator and Reviewer
Moscow, ID · On-site
$20 - $30/hr
Contract, hourly Location: Remote Hours: 20-30 per week Pay: $20-30/hour, based on experience and ... Immediate ABOUT THE ROLE We evaluate how well advanced AI coding agents solve real engineering ...
AI Agent Trajectory Annotator and Reviewer
Moscow, ID · On-site
$20 - $30/hr
Contract, hourly Location: Remote Hours: 20-30 per week Pay: $20-30/hour, based on experience and ... Immediate ABOUT THE ROLE We evaluate how well advanced AI coding agents solve real engineering ...
Contract Game Developer information
See Moscow, ID salary details
$28.2K - $39.9K
3% of jobs
$39.9K - $51.5K
10% of jobs
$51.5K - $63.1K
8% of jobs
$68.6K is the 25th percentile. Wages below this are outliers.
$63.1K - $74.8K
10% of jobs
$74.8K - $86.4K
16% of jobs
The median wage is $88.6K / yr.
$86.4K - $98.1K
20% of jobs
$104.1K is the 75th percentile. Wages above this are outliers.
$98.1K - $109.7K
16% of jobs
$109.7K - $121.3K
0% of jobs
$121.3K - $133K
1% of jobs
$133K - $144.6K
5% of jobs
$144.6K - $156.3K
11% of jobs
$28.2K
$94.2K
$156.3K
How much do contract game developer jobs pay per year?
What is a contract game developer?
A Contract Game Developer is a freelance or temporary professional hired to develop video games for a specific project or duration. They typically work on programming, game mechanics, optimization, or other development tasks. Unlike full-time employees, contract developers work on short-term agreements and may collaborate with multiple studios or clients. This role offers flexibility but may require finding new contracts regularly.
What types of projects or tasks can a contract game developer expect to work on?
As a Contract Game Developer, you may be involved in a wide range of tasks depending on the studio's needs, such as designing new game features, fixing bugs, optimizing performance, or creating game prototypes. Projects can vary from short-term assignments like implementing specific mechanics to long-term contributions on larger game releases. You'll likely collaborate closely with artists, designers, and other developers, often joining existing teams to bring specialized expertise or cover resource gaps. This role offers exposure to different genres and technologies, which can greatly broaden your experience and skill set as you work with multiple clients.
What are the key skills and qualifications needed to thrive in the contract game developer position, and why are they important?
To thrive as a Contract Game Developer, you need a solid background in programming languages such as C++, C#, or JavaScript, and experience in game engines like Unity or Unreal Engine. Familiarity with source control systems (e.g., Git), debugging tools, and relevant certifications or portfolios showcasing shipped games are highly valued. Strong time management, problem-solving abilities, and effective communication skills help developers excel, especially when working remotely or with diverse teams. These competencies enable contract game developers to deliver high-quality projects on tight deadlines, adapt to different workflows, and collaborate efficiently with clients and teammates.
What job categories do people searching Contract Game Developer jobs in Moscow, ID look for?
The top searched job categories for Contract Game Developer jobs in Moscow, ID are:
What cities near Moscow, ID are hiring for Contract Game Developer jobs?
Cities near Moscow, ID with the most Contract Game Developer job openings:

$20 - $30/hr
Full-time
Posted 5 days ago
Job description
Type: Contract, hourly
Location: Remote
Hours: 20–30 per week
Pay: $20–30/hour, based on experience and language coverage
Start: Immediate
ABOUT THE ROLE
We evaluate how well advanced AI coding agents solve real engineering problems. An agent is given a real open source codebase inside a container and a hard task, then works on its own for 80 to 250 steps. A trajectory is the full record of that run — every command, result, and decision.
You will do two jobs, and you should expect either on any given day.
•Annotate — Read a trajectory nobody has looked at yet and judge it step by step.
• Review — Take an existing annotation, written by our AI tooling or another person, and confirm, correct, or reject it.
TASKS YOU'LL SEE
• Feature build — Add a working feature to a live library without breaking anything that already worked.
• Rebuild — Work out what a compiled tool does by running it, then rebuild it to match its output, exit codes, and file effects.
• Bug hunt — Find and fix twenty undocumented bugs across a dozen files with no test suite, then record what caused them.
Mostly Python and Go, with some Rust, C, and Ct+. A trajectory runs about 100 steps.
WHAT YOU JUDGE IN A TRAJECTORY
• Was the command right for the state the environment was actually in?
• Did the agent read the previous output correctly?
• Was the step wrong, or only inefficient — these are scored differently.
• Where did the run first go off course — usually earlier than where it visibly broke.
• Did the agent notice its own mistake and recover, or keep building on a false assumption?
• Did it game the grader instead of solving the task (e.g., weakening a test or hardcoding an expected value)?
WHAT WE NEED FROM YOU
• Experience — 2+ years in software engineering, DevOps, or site reliability, with real debugging in real codebases.
• Languages — Strong in Python or Go, and able to read a language you've never used.
• Linux — Comfortable with logs, running processes, build failures, and containers.
• Workflow — Everyday Git, diffs, pull requests, and issue tracking.
• Debugging — Able to work with no test suite and no error message pointing at the cause.
• Focus — Able to hold context across a long run, because step 74 can depend on step 12.
• Writing — Clear English, since every judgement needs an explanation another engineer can check.