ZipRecruiter

Log In

1

Task Agent Jobs in Kansas (NOW HIRING)

HCW Defunct

Front Desk Agent

Wichita, KS · On-site

$14 - $17.75/hr

As a Front Desk Agent, you'll be the face of our hotel, welcoming guests with warmth ... The ability to multi-task and remain composed under pressure. * Proficiency in basic computer ...

Farmers Insurance District 72

Be Seen First

Insurance Agent Apprentice

Wichita, KS · On-site

$65K - $120K/yr

Manage key administrative and operational tasks, including client communication, policy updates, documentation, and claims coordination. * Collaborate with your mentor agent and Farmers leadership to ...

previous pagenext page

Showing results 21-40

All JobsTask Agent JobsTask Agent Jobs in Kansas

Task Agent information

What cities in Kansas are hiring for Task Agent jobs?

Cities in Kansas with the most Task Agent job openings:

Infographic showing various Task Agent job openings in Kansas as of August 2026, with employment types broken down into 91% Full Time, 6% Part Time, 1% Temporary, and 2% Contract. Highlights an 83% Physical, 1% Hybrid, and 16% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Kansas City, KS

Bespoke Labs
See more jobs at Bespoke Labsexternal

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

Apply