- Step 2 of 10 in the Agent Engineer path
Agent Engineer vs AI Engineer vs ML Engineer
Zarif
Ramp posts an Applied AI Engineer job and a Machine Learning Engineer job. Both ship to production. Both want backend skills. Both mention AI.
They're different jobs. One builds product features on top of big general-purpose models someone else trained. The other builds a model from the company's own data to catch fraud.
Add "Agent Engineer" to the mix and it gets blurrier. Here's the simplest way to keep them apart. An ML engineer is judged on the model. An AI engineer is judged on the product feature built around a model. An agent engineer is judged on what happens when the model is allowed to take actions. Reading a posting for which of those it cares about tells you more than the title does.
The postings compared here were opened on September 26, 2026. Roles close and ranges change, so open the link before relying on any detail.
The three jobs side by side
| Agent engineer | AI engineer | ML engineer | |
|---|---|---|---|
| Owns | The loop that lets a model choose actions: its tools, what it knows, what gets saved, the safety limits, and checks on the results | Product features built on foundation models (large, general-purpose models): hooking them up, finding the right documents, prompts, and shipping to users | Models trained or tuned on the company's own data, and getting them into production |
| Judged on, per postings | How well and how reliably the agent works in production, measured by tests | Shipped features and how much they get used | How well the model does on a business problem, such as fraud caught |
| Typical tools | Tool definitions, test harnesses, step-by-step logs, orchestration, sandboxes | LLM APIs, web frameworks, document search, cloud platforms | Python data tools, PyTorch, statistics, feature pipelines |
| Usually sits in | An agents, agent platform or applied AI team in engineering | Applied AI or product engineering | A data or ML department close to the business team it serves |
| Main thing you produce | An agent that fails safely, and a test that proves it | A working AI feature | A model, and evidence it beats what came before |
These are the usual patterns in the postings below, not rules. The sections that follow show where each column comes from.
Agent engineer: owns what the model is allowed to do
Agent engineering postings talk about actions, tools and testing more than about models. The work comes in two kinds: building agents for a product or a customer, and building the platform other agents run on.
On the product side, Harvey's Senior Software Engineer, Agents asks the engineer to "design environments and actions for agentic professional work, make model selection decisions, manage context windows, create optimal tools, and develop evals." Sierra's Software Engineer, Agent is responsible for "building, tuning, and evolving AI agents in production environments." Scale AI's Frontier Agents Engineer (Applied AI) names "agent guardrails, fallback strategies, tracing, monitoring, and evaluation pipelines."
On the platform side, Sierra's Software Engineer, Agent Runtime sits in platform engineering and works on "the orchestration engine, runtime, and primitives that define how agents reason, take actions, and interact with users and systems." Anthropic's Staff+ Software Engineer, Claude Managed Agents designs "durable session and event storage, sandbox orchestration, streaming, scheduling, and multi-tenant isolation." That's large-scale systems work, and the posting asks for at least eight years of it.
What these postings share is a worry about what goes wrong after the model decides. WRITER's Software engineer, agents puts it plainly: "Ensure reliability, monitoring, and observability for all agent components."
Anthropic's own guide, Building effective agents, draws the line this way. In a workflow, code decides each step. In an agent, the model directs its own steps and picks its own tools. An agent engineer decides where that line sits and makes the result safe to run.
The agent engineer career guide breaks the work into parts, with a portfolio project to practice on.
AI engineer: ships features built on foundation models
AI engineer postings are broader. The engineer plugs models into a product and ships the result. Agents are one possible result among several.
Ramp's Applied AI Engineer asks the engineer to "ship full-stack AI projects end to end" and wants "a track record of working on full-stack AI projects, particularly those involving production use cases of LLMs." The same posting also covers "components for AI infrastructure, supporting production-level inference and fine-tuning" and internal tools for other engineers. The weight is on range and shipping.
WRITER's AI engineer reports to the head of AI engineering and will "drive the development of intelligent agents and AI-powered features." It also asks for PyTorch, TensorFlow or JAX and "MLOps tools for managing the AI lifecycle." That's the overlap in one posting: agents are part of the job, and so is model tooling that an agent engineer posting rarely mentions.
The practical difference from an agent engineer is how deep you go on one question. An AI engineer is judged on whether the feature works for users. An agent engineer is judged on whether the actions the model takes are correct, allowed, and possible to recover from when something breaks.
The AI engineer career guide covers the broader role, with a project on finding documents and testing answers.
ML engineer: owns the model
ML engineer postings start from data. The engineer trains, tests and deploys models for one specific problem, and the model itself is the product.
Ramp's Machine Learning Engineer sits in the data department and works with fraud engineering. The posting asks the engineer to "prototype and productionize machine learning models and rules-based systems to protect Ramp and its users from fraud." It wants "strong python experience (numpy, pandas, sklearn, pytorch etc.)" and "prior experience deploying Machine Learning models to production."
Put that next to Ramp's Applied AI Engineer posting. Both ship to production, and both need backend skills. The ML engineer works with statistics, feature data and a model the company owns. The applied AI engineer works with foundation models someone else trained. Neither posting mentions what an agent is allowed to change or how approvals work.
Where the titles blur
Three patterns come up often enough to watch for.
- The AI engineer who builds agents. WRITER's AI engineer posting includes "intelligent agents" in its scope. If most of the bullets are about tools, actions and testing, prepare for an agent engineering interview.
- The agent engineer who's really a platform engineer. Anthropic's Claude Managed Agents and Sierra's Agent Runtime postings are platform jobs. Knowing agents matters, but the interview will test storage, keeping customers separated, and what breaks at scale.
- The agent engineer who works with customers. Decagon's Senior Software Engineer, Agent Product will "integrate them at scale with large enterprise-grade customers." That leans toward forward deployed engineering, which the FDE vs solutions architect comparison covers.
The exact title "Agent Engineer" is still rare. On the job boards checked for this piece, Scale AI's Frontier Agents Engineer and Elastic's Agentic AI Engineer came closest. Most employers post "Software Engineer" with an agents team name attached.
How to tell which one a posting really is
Read for these signals before you trust the title. Most postings mix a little of each, so count which column wins.
| Signal in the posting | Leans agent engineer | Leans AI engineer | Leans ML engineer |
|---|---|---|---|
| Main verbs | Design tools, orchestrate, guard, evaluate agents | Integrate, ship, build features | Train, tune, model, analyze |
| Named skills | Tool calling, context management, eval harnesses, tracing | LLM APIs, full-stack frameworks, cloud platforms | Statistics, sklearn, PyTorch, feature engineering |
| Data it works with | Traces, tool results, task outcomes | Prompts, documents, user feedback | Labeled datasets, features, model metrics |
| Failure it worries about | A wrong or unauthorized action, a stuck loop | A bad answer or a slow feature | Drift, false positives, a model that stops generalizing |
| Team name | Agents, agent platform, agent runtime | Applied AI, AI product | Data, ML platform, a domain team like fraud |
If the posting still leaves it open, ask on the first call:
- Does the model in this product take actions that change records, or does it only return text?
- Who owns the test set, and how do you measure agent quality today?
- Does the team train or fine-tune models, or only use hosted ones?
- What broke in production last quarter, and who fixed it?
Posted ranges, read carefully
These ranges come from the postings linked above, opened September 26, 2026. They show how specific employers post pay. They aren't market averages, and the levels don't line up one to one.
| Employer and role | Posted range | What the posting says it covers |
|---|---|---|
| Ramp, Applied AI Engineer | $204.4K – $352K | Compensation field, plus equity. Not labeled base salary |
| Ramp, Machine Learning Engineer | Estimated Base Salary $200K – $330K | Base salary, plus equity |
| WRITER, AI engineer | SF & NYC Base Compensation $220K – $259K | Base compensation in SF and NYC, plus equity. Other US locations: $198K – $233K |
| WRITER, Software engineer, agents | SF & NYC Base compensation $146K – $240K | Base compensation in SF and NYC, open to multiple levels, plus equity. Other US locations: $132K – $216K |
| Sierra, Software Engineer, Agent Runtime | $230K – $390K | Compensation field, plus equity. Not labeled base salary |
| Anthropic, Staff+ Software Engineer, Claude Managed Agents | Annual Salary: $405,000 - $485,000 USD | Annual salary for a staff-plus role requiring at least eight years of experience |
The Ramp pair is the fairest comparison, because the same company posts both roles in the same city.
The two WRITER ranges differ in seniority as well as role. The agents posting covers several levels, so its low end isn't a fair match for the AI engineer range. The Anthropic row reflects how senior the role is more than the agent specialty.
More agent engineering ranges are on the Agent Engineer career path.
Which one fits your background
If you come from backend or large-scale systems work, agent engineering is the closest step, especially the platform side. The gap is testing: learning to measure a task whose output changes from run to run.
If you come from product or full-stack engineering, AI engineering is the natural way in, and agent work is a specialty inside it. Start with one feature, then add one tool the model can call.
If you come from data science or statistics, ML engineering uses what you already have. Moving to agent work means learning to run a service: logins and permissions, retries, and writes that are safe to repeat.
The how to become an agent engineer guide maps each background to lessons in the site's agent course.
Next steps
- Follow the Agent Engineer career path: reading order, posted pay and practice prompts.
- Read the agent engineer career guide for what the work involves day to day.
- Prepare with the agent engineer interview guide.
- Compare the broader role in the AI engineer career guide.
