1

Hourly Developer Operations Jobs in Calwa, CA (NOW HIRING)

... hourly and agency workforce, in a logistics, fulfillment, last-mile manufacturing, engineering ... operational problems - - Excellent communication skills (including local language and English ...

Design Engineer, Substation

Fresno, CA · Hybrid

$44.70 - $74.42/hr

... for our Electric Operations partners. Our organization is accountable for program planning ... PG&E is providing the hourly rate range that the company in good faith believes it might pay for ...

In this role, you will lead a team of hourly workforce and will be responsible for engaging your ... degree in Engineering, Operations, Supply Chain/Logistics, or a related field. - Industry ...

Hourly Highgate is a leading real estate investment and hospitality management company with over ... with the operation maintenance and repair of equipment. * Change out light bulbs; perform ...

Engineer Maintenance

Visalia, CA · On-site

$22 - $23/hr

Compensation Type Hourly Highgate Hotels Highgate is a leading real estate investment and ... with the operation maintenance and repair of equipment. * Change out light bulbs; perform ...

... operations, and provide engineering support. * Completes required field service reports, which ... Compensation Range: $48.41 - $65.49 per hour The hourly rate is determined by the CBA/rate sheet ...

Underfiler

Fresno, CA · On-site

$20 - $23/hr

Non-Exempt / Hourly California Compensation Range: $20.00 - $23.00 (Compensation is determined by a ... Read and interpret blueprints, engineering drawings, Job Operation Listings, process sheets, charts ...

Mesa Energy Systems, Inc.

Fresno, CA · On-site

$29.31 - $56.18/hr

... engineering applications and automated control systems. * Maintain daily operations of boilers ... Compensation Range: $29.31 - $56.18 per hour The hourly rate is determined by the CBA/rate sheet ...

Controls Technician

Fresno, CA · On-site

$42 - $60/hr

Employment Type: Full-Time * Hourly Rate: $42.00 - $60.00/hr (Depending on Experience) * Overtime ... You will work closely with mechanicalcontractors, electricians, engineers, and project managers to ...

next page

Showing results 1-20

Hourly Developer Operations information

See Calwa, CA salary details

$27

$57

$73

How much do hourly developer operations jobs pay per hour?

As of Sep 14, 2026, the average hourly pay for hourly developer operations in Calwa, CA is $57.06, according to ZipRecruiter salary data. Most workers in this role earn between $60.24 and $69.52 per hour, depending on experience, location, and employer.

What is the difference between Hourly Developer Operations vs Hourly Software Developer?

AspectHourly Developer OperationsHourly Software Developer
Primary FocusManaging deployment, infrastructure, and system reliabilityWriting, testing, and maintaining software applications
Skills & CertificationsDevOps tools, scripting, cloud platformsProgramming languages, software development frameworks
Work EnvironmentOperations teams, cloud environments, continuous integration systemsDevelopment teams, coding environments, project-based
Common UsageEnsuring system uptime, automation, deploymentBuilding new features, bug fixes, software design

Hourly Developer Operations professionals focus on system deployment, automation, and infrastructure management, while Hourly Software Developers concentrate on creating and maintaining software applications. Both roles require technical skills but serve different aspects of the software lifecycle.

What cities near Calwa, CA are hiring for Hourly Developer Operations jobs?

Cities near Calwa, CA with the most Hourly Developer Operations job openings:

Infographic showing various Hourly Developer Operations job openings in Calwa, CA as of August 2026, with employment types broken down into 88% Full Time, 11% Part Time, and 1% Contract. Highlights an 93% Physical, 3% Hybrid, and 4% Remote job distribution, with an average salary of $118,677 per year, or $57.1 per hour.

AI Agent Trajectory Annotator and Reviewer

Fresno, CA • On-site

$20 - $30/hr

Full-time

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