ZipRecruiter

Log In

1

Contract Gameplay Engineer Jobs in Michigan (NOW HIRING)

previous pagenext page

Showing results 21-40

All JobsContract Gameplay Engineer JobsContract Gameplay Engineer Jobs in Michigan

Contract Gameplay Engineer information

What is a contract gameplay engineer?

Contract Gameplay Engineers are software developers hired on a temporary or project basis to design, implement, and refine interactive features in video games. They work closely with game designers, artists, and other developers to build gameplay systems such as player controls, game mechanics, and in-game events. Contract roles are often project-specific, allowing companies to bring in specialized talent for the duration of a particular game’s development cycle. These engineers typically write code, debug gameplay issues, and help ensure a smooth and engaging player experience.

What skills and qualifications are needed to thrive as a contract gameplay engineer?

To thrive as a Contract Gameplay Engineer, you need strong proficiency in programming languages like C++ or C#, experience with game engines such as Unity or Unreal, and a solid understanding of game design principles. Familiarity with version control systems (e.g., Git), debugging tools, and sometimes certifications in software development are typically required. Creative problem-solving, effective communication, and the ability to collaborate remotely with diverse teams are crucial soft skills. These competencies ensure efficient development, integration of engaging gameplay features, and seamless teamwork within dynamic, project-based environments.

What are common challenges faced by contract gameplay engineers, and how can they be managed?

Contract Gameplay Engineers often face challenges such as quickly adapting to new codebases, integrating with established development pipelines, and aligning with the creative vision of ongoing projects. To manage these effectively, clear communication with team leads, thorough documentation review, and proactive collaboration with designers and other engineers are essential. Building strong relationships early on helps streamline feedback loops and ensures your contributions align well with project goals, leading to successful contract outcomes.

What is the difference between Contract Gameplay Engineer vs Contract Software Engineer?

AspectContract Gameplay EngineerContract Software Engineer
Required CredentialsBachelor's in Computer Science, experience in game developmentBachelor's in Computer Science or related field, general programming skills
Work EnvironmentGame studios, entertainment companies, remote optionsTech companies, software firms, various industries
Employer & Industry UsagePrimarily in gaming and entertainmentAcross multiple industries including tech, finance, healthcare
Search & Comparison IntentFocus on game development rolesBroader software development roles

Contract Gameplay Engineers specialize in developing interactive gaming features, working closely with game designers and artists. In contrast, Contract Software Engineers have a broader scope, working on various software applications across industries. While both roles require strong programming skills and similar credentials, their work environments and industry focus differ significantly.

What are the most commonly searched types of Gameplay Engineer jobs in Michigan?

The most popular types of Gameplay Engineer jobs in Michigan are:

What are popular job titles related to Contract Gameplay Engineer jobs in Michigan?

For Contract Gameplay Engineer jobs in Michigan, the most frequently searched job titles are:

What job categories do people searching Contract Gameplay Engineer jobs in Michigan look for?

The top searched job categories for Contract Gameplay Engineer jobs in Michigan are:

What cities in Michigan are hiring for Contract Gameplay Engineer jobs?

Cities in Michigan with the most Contract Gameplay Engineer job openings:

Contract Gameplay Engineer jobs near you

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Sterling Heights, MI

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

Apply