AI Engineer vs ML Engineer vs Software Engineer

On September 26, 2026, Ramp was hiring an Applied AI Engineer, a Machine Learning Engineer and a Software Engineer, all at once. All three jobs touch AI. All three pay well. They are not the same job, and the interviews won't be either.

Here's the short version. An AI engineer builds a product feature on top of a model someone else trained. An ML engineer builds and trains the model. A software engineer builds the systems both of them plug into.

Short versions break on real job titles, so the rest of this guide checks that one against thirteen postings. Using three roles from one company means the differences come from the job, not the employer. All postings 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

	AI engineer	ML engineer	Software engineer
Owns	A product feature or workflow whose core step is a model call	A model: its data, training, evaluation and deployment	A product surface or system: its data model, APIs and reliability
Main question	Does the product behave correctly when the model is unsure or wrong?	Does the model predict well enough, and keep doing so?	Does the system do what it should, at scale, without breaking?
Typical work	Finding the right documents for the model, letting it call tools, prompts, checking its output, test sets ("evals")	Features, training runs, offline metrics, serving the model, watching accuracy slip over time	Backend services, data modeling, integrations, performance
Uses models by	Calling a hosted or open model and shaping what it sees	Training or fine-tuning one	Integrating a model service another team owns
Main artifact	A feature that works, plus the test set that proves it	A model in production, plus the metrics that justify it	A service in production, plus the tests and runbooks around it

These are defaults drawn from the postings below, not laws.

The split has a history too. swyx's 2023 essay The Rise of the AI Engineer described a software engineer building with foundation models rather than training them. Chip Huyen's AI Engineering (O'Reilly, 2025) separates building applications on foundation models from traditional ML engineering's feature engineering and model training.

AI engineer: builds the product around the model

Ramp's Applied AI Engineer sits on its Applied AI team and is asked to "ship full-stack AI projects end to end." It wants "a track record of working on full-stack AI projects, particularly those involving production use cases of LLMs." The posting also mentions infrastructure "supporting production-level inference and fine-tuning," so the line to ML work isn't absolute.

Brex's AI Engineer, Product builds its Audit Agent, and the posting says plainly what the job is not. "The agent itself reasons; the surrounding product harness is what makes that reasoning useful, trustworthy, and operable for real customers." It adds that "the majority of your work will be backend: system design, data modeling, API shape."

In plain terms, the model does the thinking. The engineer builds everything around it that makes the thinking safe to hand to a customer.

Clay's Software Engineer, Applied AI puts testing at the center: "Build and run evals that measure whether an agent actually completed the task correctly - not just whether the output looked plausible." Samsara's AI Engineer, Customer Success asks the person to "define success criteria and evaluation frameworks before you write the first line of code" and to "own the deployment, versioning, and rollback plan for every agent."

So an AI engineer is judged on whether a model-powered feature works for users, measured by tests the engineer designed. The model usually belongs to someone else. The product, the code around the model and the measuring are theirs.

ML engineer: builds the model

Ramp's Machine Learning Engineer sits in the Data department and works on fraud. The posting asks the person to "employ statistical and machine learning techniques on large datasets to discover patterns of fraud, platform abuse, and identity theft" and to "prototype and productionize machine learning models and rules-based systems." It requires "prior experience deploying Machine Learning models to production."

Glean's Machine Learning Engineer, Search Quality works on language models too, but at the model layer. Its list includes "train a model to capture interactions between signals in our ranking system" and "design smarter ways to domain-adapt language models to each customer's corpus." It asks for "proven ability to design, build, and ship production-ready models."

The word that separates the two roles is train. An ML engineer changes the model itself, or builds a new one, and is judged on how it performs in production.

Glean's posting also shows the overlap. Its team works on "natural language question-answering, evaluation, and experimentation," which an AI engineer would recognize. When a posting says train, rank or domain-adapt, expect an ML interview.

Software engineer: builds the system everyone depends on

Ramp's Software Engineer, Core Product works on cards, approvals and spend controls. The posting says the team's systems "handle billions of dollars in transactions and integrate deeply with Ramp's AI platform." One responsibility is to "integrate with Ramp's internal AI platform to automate spend policy enforcement and anomaly detection."

That last line is the point. Software engineers call models more and more, but the job is still judged on the system: does the transaction go through correctly, quickly, every time? The AI platform belongs to another team.

Moving from this role to AI engineering means taking ownership of the model-powered part, including the fact that it's sometimes wrong.

Where the titles blur

Four patterns came up often enough to watch for.

Applied AI Engineer as a customer-facing job. Anthropic's Applied AI Engineer, Enterprise Tech is "a trusted technical advisor to Enterprise Technology companies adopting the Claude API." OpenAI's Applied AI Engineer, Startups sits within Go To Market and partners "with the Sales team across startup accounts." Cognition's Applied AI Engineer puts it plainly: "You don't demo Devin - you deploy it." These are closer to a forward deployed engineer than to a product engineer.
AI engineer inside another department. Stripe's AI Engineer sits within Solutions Architecture and builds tools for that team: "You'll discover where SAs lose time and build high-impact solutions." Gusto's Enterprise Application AI Engineer sits in IT and connects systems such as NetSuite, Zuora and Jira to agents. The users are coworkers, not customers.
GenAI engineer who also builds models. Datadog's Staff GenAI Engineer in APM is asked to "build and benchmark GenAI/ML models using state-of-the-art techniques." That's ML engineering language under a GenAI title.
Software engineer as the AI title. Clay's agent role is titled Software Engineer, Applied AI. Plenty of product teams use a plain software engineer title for work another company would call AI engineering.

None of these is a bad job. They're different jobs. If you prepare for the title, you prepare for the wrong interview.

How to tell which one a posting really is

Read the posting and count which column wins. Most postings mix a little of each.

Signal in the posting	Leans AI engineer	Leans ML engineer	Leans software engineer
Main verbs	Ship, integrate, evaluate, orchestrate	Train, fine-tune, rank, benchmark	Design, scale, build, migrate
Named skills	LLM APIs, retrieval, evals, agent frameworks, MCP	PyTorch, statistics, feature pipelines, experimentation	Languages, databases, distributed systems
What is measured	Did it finish the task, was it right, did it decline when it should, cost per request	Precision, recall, ranking quality, accuracy slipping over time	Latency, uptime, correctness of the transaction
Who uses the output	Product users, or coworkers through an internal tool	A product surface that consumes predictions	Every other service and product team
Department	Engineering, Applied AI, sometimes a business function	Data, ML, research-adjacent teams	Engineering product or platform teams

If the department is Go To Market or the posting mentions sales accounts, read it as a customer-facing job, whatever the title says.

Here's a made-up example of the count. A posting is titled "Machine Learning Engineer, Support Assistant." It asks you to connect the company's help docs to a hosted model, write test cases for wrong answers, and ship the assistant to customers. It never says train.

The verbs are ship, connect and test. The measure is whether customers get right answers. That's an AI engineer job wearing an ML title, and the interview will look like an AI engineer interview.

Posted ranges at one employer

Ramp posted all three roles on September 26, 2026. The ranges aren't labeled the same way, which is worth noticing on its own.

Ramp role	Posted range	What the posting says it covers
Applied AI Engineer	$204.4K – $352K	Compensation with equity offered; final pay depends on location and level. Not labeled as base salary
Machine Learning Engineer	$200K – $330K	"Estimated Base Salary," with equity offered
Software Engineer, Core Product	$168K – $275K	"SF/NY Target Base Salary," with equity offered

Each range spans several levels, and one of the three doesn't say it's base salary. So the table shows how one employer posted pay on one day. It doesn't show that any of these roles pays more than another at the same level.

The AI engineer career path lists more AI engineer ranges from other employers, each with what it covers.

Which one fits your background

Backend or product engineer. AI engineering is the nearest step. The gap is designing for output that's sometimes wrong, and building the test set that shows how often. The how to become an AI engineer guide puts that work in order.

Data scientist. Look at both AI and ML engineering. You already think in datasets and error rates. ML engineering adds training and serving models. AI engineering adds running a product service.

ML engineer. You can move to AI engineering quickly. Expect more questions about product scope, speed and cost than about model architecture.

Next steps

Follow the AI engineer career path: reading order, employer-posted pay and practice prompts.
Read the AI engineer career guide for a portfolio project with test cases.
Use the AI engineer interview guide once you know which job you're applying for.
If the agent side of the work appeals most, read the agent engineer vs AI engineer vs ML engineer comparison.