1

Weekend Python Game Developer Jobs in Indiana (NOW HIRING)

Showing results 21-40

Weekend Python Game Developer information

What is the difference between Weekend Python Game Developer vs Part-Time Python Developer?

AspectWeekend Python Game DeveloperPart-Time Python Developer
CredentialsBasic Python knowledge, possibly some game development experienceProficiency in Python, relevant certifications optional
Work EnvironmentTypically freelance or project-based, flexible hours, often remotePart-time employment, may be remote or on-site, flexible schedule
Industry UsageGame development studios, indie developers, hobbyistsTech companies, startups, software firms
Search & Comparison IntentUnderstanding freelance or hobbyist roles in game developmentExploring flexible coding roles in Python

The Weekend Python Game Developer focuses on creating games during weekends, often as a hobby or freelance project, with an emphasis on game-specific skills. In contrast, a Part-Time Python Developer may work on various software projects with flexible hours but not necessarily in game development. Both roles require Python proficiency and offer flexible schedules, but their industry focus and typical work environments differ.

What cities in Indiana are hiring for Weekend Python Game Developer jobs?

Cities in Indiana with the most Weekend Python Game Developer job openings:

AI Agent Trajectory Annotator and Reviewer

Gary, IN

$20 - $30/hr

Full-time

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