The short answer
If the code you ship lives in the customer's repository and the win is the customer's outcome, that is forward deployed work. If the code you ship is a demo or integration that helps close and onboard a customer onto your employer's platform, that is solutions engineering.
The two roles look similar from the outside because both put a technical person in front of a customer. The forward deployed engineer vs solutions engineer question comes down to whose product gets built and who you answer to.
Side by side
| Dimension | Forward Deployed AI Engineer | Solutions engineer |
|---|---|---|
| Works for | The customer's outcome, via a deployment company or a direct engagement | The software vendor selling the product |
| Primary deliverable | A production AI workflow in the customer's codebase | Demos, proofs of concept, and integrations |
| Where the code lives | The customer's product and repository | The vendor's platform and demo environments |
| Measured on | A shipped workflow the customer's team can run and maintain | Pipeline, deals closed, and successful onboarding |
| AI focus | Prompt and context design, data integration, evaluation rubrics | Showing how the vendor's AI features fit the customer's stack |
| Compensation | Median base $174,000; median package $238,000; senior frontier packages above $500,000 (public data, 2026) | Varies by vendor; typically base plus commission (OTE), tied to sales and onboarding outcomes. |
Where they overlap
Both roles need to read a customer's real environment quickly, translate a business problem into a technical plan, and stay credible in a room with engineers and executives at the same time. Both live with ambiguity and incomplete data. The instincts transfer cleanly, which is why solutions engineers are one of the most common backgrounds for people moving into forward deployed AI work.
How to choose between them
Choose by what you want to own. If you want to close deals and help many customers adopt one product, solutions engineering fits. If you want to build the actual feature and own whether it works in production, the Forward Deployed AI Engineer role fits.
One more practical signal: seen as solutions engineer vs forward deployed engineer, the trade is breadth against depth. Solutions engineering rewards breadth across a pipeline; forward deployed work rewards depth on one customer at a time. Neither is more senior than the other. They optimize for different outcomes.
Applied AI Engineer vs Solutions Engineer
Applied AI Engineer is Anthropic's title for the FDE-shaped role, the same job this page describes under a different name. So the same contrast applies: the applied AI engineer builds a production AI workflow inside the customer's systems and is measured on whether it ships, while the solutions engineer sells and integrates the vendor's product and is measured on the deal. If a posting says Applied AI, read it as forward deployed.
Related
Frequently asked questions
Can a solutions engineer become a Forward Deployed AI Engineer?
Often, yes. Solutions engineers already have the customer-facing instinct and the integration skills. The shift is from selling and configuring a vendor's product to building and owning a production AI workflow inside the customer's codebase, plus the evaluation discipline to prove it works.
Who does each role work for?
A solutions engineer almost always works for the software vendor and is measured on sales and onboarding. A Forward Deployed AI Engineer works on the customer's outcome, whether employed by a deployment company or engaged directly, and is measured on shipping a workflow the customer's team can run.
Does a solutions engineer write production code?
Sometimes, but usually demos, proofs of concept, and integrations rather than features that live permanently in the customer's product. A Forward Deployed AI Engineer's main deliverable is production code in the customer's repository, with edge cases, logging, and a handoff.