ZipRecruiter

Log In

2

Freelance No Experience Python Jobs in Utah (NOW HIRING)

Corpay

Quantitative Risk Analyst

Salt Lake City, UT · On-site

$125 - $150/hr

Hands-on Python experience -- ability to read, debug, and modify scripts in a production ... Any unsolicited candidate submissions will become the property of Corpay, and no fees will be paid ...

Corpay

Quantitative Risk Analyst

Salt Lake City, UT · On-site

Hands-on Python experience - ability to read, debug, and modify scripts in a production environment ... Any unsolicited candidate submissions will become the property of Corpay, and no fees will be paid ...

previous pagenext page

Showing results 21-40

All JobsPython JobsFreelance No Experience Python JobsFreelance No Experience Python Jobs in Utah

Freelance No Experience Python information

What is the difference between Freelance No Experience Python vs Data Analyst?

AspectFreelance No Experience PythonData Analyst
Required CredentialsBasic Python knowledge, online coursesBachelor's in related field, some certifications
Work EnvironmentRemote, project-basedOffice or remote, ongoing role
Industry UsageFreelance projects, startupsCorporate, consulting firms
Search & Comparison IntentEntry-level, beginner projectsCareer development, full-time roles

Freelance No Experience Python typically involves short-term, project-based work requiring basic Python skills, suitable for beginners. Data Analysts often have formal education and work in more structured environments. Both roles are in demand, but they differ in credentials, work setting, and career paths.

What freelance jobs can I do with Python?

Freelance Python developers can work on tasks such as web development, automation scripting, data analysis, and building small applications. These jobs often require knowledge of frameworks like Django or Flask, and familiarity with version control tools like Git. Many opportunities are available on freelance platforms for projects that do not require prior experience, making it accessible for beginners to start building their portfolio.

What are popular job titles related to Freelance No Experience Python jobs in Utah?

For Freelance No Experience Python jobs in Utah, the most frequently searched job titles are:

What job categories do people searching Freelance No Experience Python jobs in Utah look for?

The top searched job categories for Freelance No Experience Python jobs in Utah are:

What cities in Utah are hiring for Freelance No Experience Python jobs?

Cities in Utah with the most Freelance No Experience Python job openings:

Freelance No Experience Python jobs near you

AI Agent Trajectory Annotator and Reviewer

Orem, UT

Bespoke Labs
See more jobs at Bespoke Labsexternal

$20 - $30/hr

Full-time

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