1

Rust Game Developer Jobs in Glassboro, NJ (NOW HIRING)

Rust Game Developer information

See Glassboro, NJ salary details

$31.4K

$104.9K

$174K

How much do rust game developer jobs pay per year?

As of Sep 3, 2026, the average yearly pay for rust game developer in Glassboro, NJ is $104,876.00, according to ZipRecruiter salary data. Most workers in this role earn between $78,800.00 and $119,900.00 per year, depending on experience, location, and employer.

What is a Rust game developer?

A Rust Game Developer is a software engineer who specializes in creating video games using the Rust programming language. Rust is known for its emphasis on safety, performance, and concurrency, making it increasingly popular for game development. These developers work on various aspects of game creation, including game mechanics, graphics, networking, and optimization. They may use game engines that support Rust, such as Bevy or Amethyst, and often collaborate with designers, artists, and other programmers to bring games to life.

What are the key skills and qualifications needed to thrive as a Rust game developer?

To thrive as a Rust Game Developer, you need proficiency in the Rust programming language, a solid understanding of game development principles, and experience with real-time systems and graphics programming. Familiarity with game engines (like Bevy or Godot with Rust bindings), version control systems (such as Git), and knowledge of ECS (Entity Component System) architecture are typically required. Strong problem-solving, collaboration, and adaptability help you innovate and work effectively within a development team. These skills ensure efficient, safe, and high-performance game creation, meeting the demands of modern game development.

What are some common challenges faced by Rust game developers when collaborating with multidisciplinary teams?

Rust Game Developers often work closely with artists, designers, and other programmers, each with different skill sets and workflows. One common challenge is ensuring seamless integration between Rust codebases and assets created in tools that may not natively support Rust. Clear communication, well-defined interfaces, and consistent documentation are crucial for bridging these gaps. Additionally, Rust’s strict safety and concurrency features can require extra onboarding for team members less familiar with the language, but these same features help maintain code quality in the long run.

What job categories do people searching Rust Game Developer jobs in Glassboro, NJ look for?

The top searched job categories for Rust Game Developer jobs in Glassboro, NJ are:

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Philadelphia, PA • On-site

$20 - $30/hr

Full-time

Posted 3 days ago

New


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.