1

Hourly Software Developer Jobs in Park, VA (NOW HIRING)

... Engineering, Computer Science, Software Engineering, Supply Chain Management/Logistics, Finance ... Posted Date: 09/01/2026 This role will be posted for a minimum of 3 days. $20 min hourly wage - $35 ...

... Engineering, Computer Science, Software Engineering, Supply Chain Management/Logistics, Finance ... Posted Date: 09/01/2026 This role will be posted for a minimum of 3 days. $20 min hourly wage - $35 ...

... Engineering, Computer Science, Software Engineering, Supply Chain Management/Logistics, Finance ... Posted Date: 09/01/2026 This role will be posted for a minimum of 3 days. $20 min hourly wage - $35 ...

Showing results 41-60

Hourly Software Developer information

See Park, VA salary details

$47.6K

$110.9K

$164.6K

How much do hourly software developer jobs pay per year?

As of Sep 8, 2026, the average yearly pay for hourly software developer in Park, VA is $110,886.00, according to ZipRecruiter salary data. Most workers in this role earn between $89,200.00 and $128,900.00 per year, depending on experience, location, and employer.

What is an hourly software developer?

An Hourly Software Developer is a software professional who works and gets paid based on the number of hours they contribute to a project instead of a fixed salary. These developers are often hired for freelance, contract, or temporary positions to assist with specific development tasks. They may work on designing, coding, testing, or maintaining software solutions for businesses. Hourly developers offer flexibility for both employers and workers, making it easier to scale development efforts as needed. This type of role is common in remote and gig-based work environments.

What does an hourly software developer's typical work schedule look like?

Hourly Software Developers often have flexible schedules, with hours that can range from set shifts to project-based timelines, depending on employer or client needs. In many cases, developers may work remotely, collaborating with team members through online platforms and attending scheduled meetings or check-ins. The work structure encourages regular progress updates and communication to ensure milestones are met efficiently. This hourly model can provide work-life balance and adaptability, while still requiring accountability and consistent productivity to meet project deadlines.

What are the key skills and qualifications needed to thrive as an hourly software developer?

To excel as an Hourly Software Developer, you should have strong programming skills, a solid understanding of software development methodologies, and relevant education or proven experience in the field. Familiarity with common frameworks, code repositories (such as Git), and knowledge of industry-standard languages like Python, Java, or JavaScript are routinely expected. Effective time management, adaptability, and clear communication help developers succeed in dynamic work environments and coordinate with project stakeholders. These skills ensure developers can deliver quality work efficiently and reliably, which is critical for roles with hourly accountability.

What are the most commonly searched types of Software Developer jobs in Park, VA?

The most popular types of Software Developer jobs in Park, VA are:

What are popular job titles related to Hourly Software Developer jobs in Park, VA?

For Hourly Software Developer jobs in Park, VA, the most frequently searched job titles are:

What cities near Park, VA are hiring for Hourly Software Developer jobs?

Cities near Park, VA with the most Hourly Software Developer job openings:

Infographic showing various Hourly Software Developer job openings in Park, VA as of August 2026, with employment types broken down into 1% As Needed, 51% Full Time, 44% Part Time, 1% Temporary, and 3% Contract. Highlights an 99% Physical, and 1% Remote job distribution, with an average salary of $110,886 per year, or $53.3 per hour.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Harrisonburg, VA • On-site

$20 - $30/hr

Full-time

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