ZipRecruiter

Log In

1

Rust Game Jobs in Brandon, FL (NOW HIRING)

All JobsRust Game JobsRust Game Jobs in Brandon, FL

Rust Game information

See Brandon, FL salary details

$6

$18

$32

How much do rust game jobs pay per hour?

As of Sep 4, 2026, the average hourly pay for rust game in Brandon, FL is $18.20, according to ZipRecruiter salary data. Most workers in this role earn between $12.31 and $20.67 per hour, depending on experience, location, and employer.

What is rust game?

Rust is a popular multiplayer survival video game developed by Facepunch Studios. In Rust, players must gather resources, build shelters, craft items, and survive against environmental hazards, wildlife, and other players. The game emphasizes player interaction, including cooperation and competition, and features a large open world with evolving gameplay dynamics. Rust is available on PC and consoles, and it is known for its challenging survival mechanics and active online community.

What skills and qualifications are needed to thrive as a game developer specializing in Rust?

To thrive as a Game Developer specializing in Rust, you need strong programming skills in Rust, game development experience, and a relevant degree in computer science or a related field. Familiarity with game engines (such as Bevy or Godot), version control systems like Git, and experience with graphics or networking APIs are typically required. Creativity, problem-solving, and the ability to collaborate effectively with multidisciplinary teams are essential soft skills. These competencies ensure efficient development of high-performance, reliable games and foster innovation in competitive gaming markets.

What are common challenges faced by developers working on a large-scale Rust game, and how can they be addressed?

Developers working on large-scale Rust games often encounter challenges such as optimizing performance for multiplayer environments, managing complex systems (like networking and physics), and maintaining code quality as the project grows. Addressing these issues typically involves implementing efficient data structures, leveraging Rust's strong type system to prevent bugs, and using profiling tools to identify bottlenecks. Team collaboration is crucial, so regular code reviews and clear documentation help maintain consistency and facilitate onboarding of new team members.

What are popular job titles related to Rust Game jobs in Brandon, FL?

For Rust Game jobs in Brandon, FL, the most frequently searched job titles are:

What cities near Brandon, FL are hiring for Rust Game jobs?

Cities near Brandon, FL with the most Rust Game job openings:

Rust Game jobs near you

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Tampa, FL • 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.

Apply