1

Contract Unity Game Developer Jobs in Fresno, CA

Contract Unity Game Developer information

See Fresno, CA salary details

$32.3K

$107.7K

$178.7K

How much do contract unity game developer jobs pay per year?

As of Sep 5, 2026, the average yearly pay for contract unity game developer in Fresno, CA is $107,702.00, according to ZipRecruiter salary data. Most workers in this role earn between $80,900.00 and $123,100.00 per year, depending on experience, location, and employer.

What is a contract Unity game developer?

Contract Unity Game Developers are professionals hired on a temporary or project basis to design, develop, and implement games or interactive experiences using the Unity engine. They work with studios or clients to create gameplay mechanics, visual elements, and software architecture, often collaborating with artists and designers. Unlike full-time employees, contract developers typically work on specific projects or for a set duration, providing flexibility for both the developer and the employer.

What skills and qualifications are needed to thrive as a contract Unity game developer?

To thrive as a Contract Unity Game Developer, you need strong proficiency in C#, Unity engine workflows, and experience developing and deploying games across platforms, usually backed by a relevant degree or portfolio. Familiarity with version control systems (like Git), asset management tools, and integrating APIs or SDKs is commonly required. Effective communication, self-motivation, and adaptability are essential soft skills for collaborating remotely and delivering on diverse client requirements. Mastering these skills ensures high-quality, timely game development and fosters productive client relationships in a competitive contract environment.

What are common challenges contract Unity game developers face when joining new projects?

Contract Unity Game Developers often encounter challenges such as quickly understanding the existing codebase, adapting to varying project workflows, and integrating seamlessly with remote or distributed teams. Since contractors typically join projects mid-development, they must efficiently onboard, communicate proactively with permanent staff, and adapt to different coding standards or tools. Strong documentation skills and the ability to ask clarifying questions are essential for overcoming these hurdles and contributing effectively from day one.

What is the difference between Contract Unity Game Developer vs Contract Unreal Engine Developer?

AspectContract Unity Game DeveloperContract Unreal Engine Developer
Required CredentialsExperience with Unity, C# programming, portfolio of Unity projectsExperience with Unreal Engine, C++/Blueprints, portfolio of Unreal projects
Work EnvironmentGame studios, freelance projects, mobile and indie developmentAAA and high-end game development, VR/AR projects, simulation
Employer & Industry UsageWidely used in mobile, indie, and casual gaming sectorsPopular in AAA titles, VR, and simulation industries

Both roles require strong knowledge of their respective engines and programming languages. While they share similar credentials and work environments, Unity developers often focus on mobile and indie projects, whereas Unreal developers are more involved in high-end, AAA, and VR projects. The choice depends on the project scope and industry focus.

What are the most commonly searched types of Unity Game Developer jobs in Fresno, CA?

The most popular types of Unity Game Developer jobs in Fresno, CA are:

What are popular job titles related to Contract Unity Game Developer jobs in Fresno, CA?

For Contract Unity Game Developer jobs in Fresno, CA, the most frequently searched job titles are:

What job categories do people searching Contract Unity Game Developer jobs in Fresno, CA look for?

The top searched job categories for Contract Unity Game Developer jobs in Fresno, CA are:

What cities near Fresno, CA are hiring for Contract Unity Game Developer jobs?

Cities near Fresno, CA with the most Contract Unity Game Developer job openings:

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Fresno, CA • On-site

$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.