1

Freelance Ai Agent Developer Jobs in Silver Spring, MD

Showing results 41-60

Freelance Ai Agent Developer information

What is the difference between Freelance Ai Agent Developer vs Freelance Chatbot Developer?

AspectFreelance Ai Agent DeveloperFreelance Chatbot Developer
CredentialsKnowledge of AI, machine learning, NLPExperience with chatbot platforms, scripting, NLP
Work EnvironmentDevelops intelligent agents for various platformsBuilds conversational interfaces for customer service or marketing
Industry UsageUsed in AI-driven automation, virtual assistantsCommon in customer support, marketing campaigns

Freelance Ai Agent Developers focus on creating intelligent agents that can perform complex tasks using AI and machine learning, while Freelance Chatbot Developers primarily design conversational interfaces for customer interaction. Both roles require NLP skills but differ in scope and application.

What are the most commonly searched types of Ai Agent Developer jobs in Silver Spring, MD?

The most popular types of Ai Agent Developer jobs in Silver Spring, MD are:

What are popular job titles related to Freelance Ai Agent Developer jobs in Silver Spring, MD?

For Freelance Ai Agent Developer jobs in Silver Spring, MD, the most frequently searched job titles are:

What job categories do people searching Freelance Ai Agent Developer jobs in Silver Spring, MD look for?

The top searched job categories for Freelance Ai Agent Developer jobs in Silver Spring, MD are:

What cities near Silver Spring, MD are hiring for Freelance Ai Agent Developer jobs?

Cities near Silver Spring, MD with the most Freelance Ai Agent Developer job openings:

Infographic showing various Freelance Ai Agent Developer job openings in Silver Spring, MD as of June 2026, with employment types broken down into 100% Full Time. Highlights an 100% Remote job distribution.

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Adelphi, MD • On-site

$20 - $30/hr

Full-time

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