1

Hourly Python Jobs in Nevada (NOW HIRING)

Programmer - AI Trainer

Las Vegas, NV · On-site +1

$50 - $100/hr

Projects are paid hourly starting at $50-$100+/hr, with bonus rates available on some projects Responsibilities: * Give AI chatbots coding challenges and evaluate their outputs * Evaluate the quality ...

Optimization Engineer - Commercial

Las Vegas, NV · On-site

$109K - $131K/yr

Proficiency in writing production-quality code in Python, utilizing libraries like Pandas/NumPy and using advanced techniques such as vectorization and parallelization. Strong foundation in ...

Optimization Engineer - Commercial

Las Vegas, NV · On-site

$110K - $132K/yr

Proficiency in writing production-quality code in Python, utilizing libraries like Pandas/NumPy and using advanced techniques such as vectorization and parallelization. * Strong foundation in ...

Data Center Engineer

Reno, NV · On-site

$35 - $45/hr

Between $35 to $45 hourly, depends on experience and relevancy to the role. Duration: 12 months ... Proficiency in DCIM (Nautobot, etc.) and scripting (shell, Python, Ansible). * Working knowledge of ...

New

Minimum two (2) years of experience in a technical environment. • Proficiency in writing production-quality code in Python, utilizing libraries like Pandas/NumPy and using advanced techniques such ...

Showing results 21-40

Hourly Python information

What does an hourly Python developer do?

An Hourly Python developer is a programmer who is hired on an hourly basis to create, modify, or maintain software using the Python programming language. Their tasks can range from developing web applications and automating tasks to analyzing data or building machine learning models. Hourly Python developers are often engaged for specific projects or short-term work, allowing businesses to scale their development resources as needed. They may work independently or as part of a team, and are usually paid based on the number of hours worked rather than a fixed salary.

What types of projects can hourly Python developers expect to work on, and how does the project structure typically look?

Hourly Python developers are often brought in to support a variety of short-term or specialized projects, such as data analysis, web application enhancements, automation scripts, or bug fixes. The work structure is usually project-based, with clear deliverables and timelines set by the client or team lead. Collaboration might happen remotely with regular check-ins via chat or video calls, and developers are expected to manage their own time efficiently. This role offers exposure to diverse projects and technologies, making it ideal for those who enjoy variety and learning new tools.

What are the key skills and qualifications needed to thrive as an hourly Python developer, and why are they important?

To succeed as an Hourly Python Developer, you need strong programming skills in Python, experience with frameworks like Django or Flask, and a solid understanding of software development principles. Familiarity with version control systems such as Git, cloud platforms, and possibly certifications like PCEP or PCAP are often expected. Effective communication, problem-solving abilities, and adaptability help you collaborate with clients and teams while managing project-based workloads. These competencies ensure you can deliver high-quality, efficient solutions in dynamic and time-sensitive environments.

What are the most commonly searched types of Python jobs in Nevada?

The most popular types of Python jobs in Nevada are:

What are popular job titles related to Hourly Python jobs in Nevada?

For Hourly Python jobs in Nevada, the most frequently searched job titles are:

What job categories do people searching Hourly Python jobs in Nevada look for?

The top searched job categories for Hourly Python jobs in Nevada are:

What cities in Nevada are hiring for Hourly Python jobs?

Cities in Nevada with the most Hourly Python job openings:

Infographic showing various Hourly Python job openings in Nevada as of August 2026, with employment types broken down into 1% As Needed, 61% Full Time, 34% Part Time, 1% Temporary, 2% Contract, and 1% Nights. Highlights an 99% Physical, and 1% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Henderson, NV • On-site

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