2

Full Time Full Stack Developer React Python Jobs in Eau Claire, WI

Transport truck loading involves moving full pallets of products from the warehouse onto a trailer ... Position is responsible for maintaining the stability of the pallet through proper stacking and ...

Meat Service Counter Manager

Eau Claire, WI · On-site

$20.75 - $27.50/hr

Eau Claire - Mall Drive Full-Time ABOUT FESTIVAL FOODS: We are a Wisconsin grocer that is committed ... We operate +40 full-service supermarkets across the state of Wisconsin. At Festival, people are at ...

Showing results 21-40

Full Time Full Stack Developer React Python information

See Eau Claire, WI salary details

$58.9K

$128.6K

$181.8K

How much do full time full stack developer react python jobs pay per year?

As of Sep 10, 2026, the average yearly pay for full time full stack developer react python in Eau Claire, WI is $128,576.00, according to ZipRecruiter salary data. Most workers in this role earn between $108,000.00 and $149,600.00 per year, depending on experience, location, and employer.

What is the difference between Full Time Full Stack Developer React Python vs Full Time Front End Developer?

AspectFull Time Full Stack Developer React PythonFull Time Front End Developer
Required SkillsReact, Python, JavaScript, HTML, CSS, database knowledgeJavaScript, HTML, CSS, UI/UX design, React or Angular
Work EnvironmentDevelops both client and server-side applications, often in cross-functional teamsFocuses on user interface and client-side features, collaborating with designers
Industry UsageUsed across tech, finance, healthcare, and e-commerce sectorsPrimarily in web development agencies, tech companies, and startups

Full Time Full Stack Developer React Python roles require a broader skill set, covering both front-end and back-end development, while Front End Developers focus mainly on user interface and client-side features. The choice depends on your interest in full system development versus UI design.

What are popular job titles related to Full Time Full Stack Developer React Python jobs in Eau Claire, WI?

For Full Time Full Stack Developer React Python jobs in Eau Claire, WI, the most frequently searched job titles are:

What job categories do people searching Full Time Full Stack Developer React Python jobs in Eau Claire, WI look for?

The top searched job categories for Full Time Full Stack Developer React Python jobs in Eau Claire, WI are:

What cities near Eau Claire, WI are hiring for Full Time Full Stack Developer React Python jobs?

Cities near Eau Claire, WI with the most Full Time Full Stack Developer React Python job openings:

AI Agent Trajectory Annotator and Reviewer

Menomonie, WI

$20 - $30/hr

Full-time

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