1

Assistant Ai Agent Developer Jobs in Michigan (NOW HIRING)

AI Agent & Chatbot Projects * AI Workflow Projects * Predictive Modeling Projects * Educate Finance ... Bachelors' degree in Engineering, Technology field, and/or Finance or equivalent * Project ...

... AI agent. Many startups are attempting to attack this problem because the market is so big - $350B ... And our Head of Engineering was one of the earliest engineers at Figma. AI Engineer ...

AI Engineer

Birmingham, MI · On-site

$150K - $250K/yr

... AI agent. Many startups are attempting to attack this problem because the market is so big - $350B ... And our Head of Engineering was one of the earliest engineers at Figma. AI Engineer ...

AI Engineer

Ann Arbor, MI

$150K - $250K/yr

... AI agent. Many startups are attempting to attack this problem because the market is so big - $350B ... And our Head of Engineering was one of the earliest engineers at Figma. AI Engineer ...

Showing results 21-40

Assistant Ai Agent Developer information

What is an assistant AI agent developer?

An Assistant AI Agent Developer is a professional who designs, develops, and maintains AI-powered virtual assistants or chatbot systems. Their work involves programming conversational agents, integrating natural language processing (NLP) technologies, and ensuring the agent can understand and respond to user queries effectively. They may also be responsible for training the AI using data, testing the assistant's performance, and deploying updates for improved accuracy and functionality. This role often requires knowledge of programming languages such as Python, familiarity with AI frameworks, and understanding of user experience design.

What are the key skills and qualifications needed to thrive as an assistant AI agent developer?

To thrive as an Assistant AI Agent Developer, you need a solid background in programming (especially Python), machine learning concepts, and a relevant degree in computer science or a related field. Familiarity with AI frameworks like TensorFlow or PyTorch, version control systems like Git, and APIs is typically required. Strong problem-solving abilities, attention to detail, and effective teamwork are essential soft skills for success in this role. These skills ensure the development of robust, efficient AI agents and smooth collaboration within multidisciplinary teams.

What are the typical collaboration practices for an assistant AI agent developer within a software development team?

As an Assistant AI Agent Developer, you'll frequently collaborate with data scientists, senior developers, and product managers to design, test, and refine AI agents. You'll often participate in code reviews, daily standups, and brainstorming sessions to ensure that the AI solutions align with project goals and user needs. Effective communication and teamwork are essential, as you may need to integrate your code with other systems or adapt to evolving project requirements. Working with cross-functional teams not only helps in troubleshooting but also provides valuable learning opportunities to advance your skills.

What are the most commonly searched types of Ai Agent Developer jobs in Michigan?

The most popular types of Ai Agent Developer jobs in Michigan are:

What are popular job titles related to Assistant Ai Agent Developer jobs in Michigan?

For Assistant Ai Agent Developer jobs in Michigan, the most frequently searched job titles are:

What job categories do people searching Assistant Ai Agent Developer jobs in Michigan look for?

The top searched job categories for Assistant Ai Agent Developer jobs in Michigan are:

What cities in Michigan are hiring for Assistant Ai Agent Developer jobs?

Cities in Michigan with the most Assistant Ai Agent Developer job openings:

AI Agent Trajectory Annotator and Reviewer

Bespoke Labs

Allendale, MI • On-site

$20 - $30/hr

Full-time

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