1

Temporary Ai Game Developer Jobs in Arizona (NOW HIRING)

Rather than a standalone AI module, this program integrates AI as a continuous thread through all ... If eligible, the benefits available for this temporary role may include the following: • Medical ...

Rather than a standalone AI module, this program integrates AI as a continuous thread through all ... If eligible, the benefits available for this temporary role may include the following: • Medical ...

Showing results 41-60

Temporary Ai Game Developer information

What is the difference between Temporary Ai Game Developer vs AI Game Developer?

AspectTemporary Ai Game DeveloperAI Game Developer
CredentialsTypically requires a degree in computer science, game development, or related field; certifications in AI or game engines are commonSame as temporary; often requires a degree and relevant certifications
Work EnvironmentContract-based, short-term projects, often freelance or agency workFull-time or long-term employment within game studios or tech companies
Industry UsageUsed for specific projects needing temporary AI expertiseIntegrated into ongoing game development teams for continuous AI development

In summary, a Temporary Ai Game Developer is hired for short-term projects requiring AI skills, whereas an AI Game Developer typically works full-time on ongoing game development. The main differences lie in employment type, project duration, and work setup, though both roles require similar skills and qualifications.

What are the most commonly searched types of Ai Game Developer jobs in Arizona?

The most popular types of Ai Game Developer jobs in Arizona are:

What cities in Arizona are hiring for Temporary Ai Game Developer jobs?

Cities in Arizona with the most Temporary Ai Game Developer job openings:

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Flagstaff, AZ • On-site

$20 - $30/hr

Full-time

Posted 4 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.