Once an AI startup starts closing enterprise deals, two roles tend to come up in the same conversation: forward deployed engineer and solutions engineer. They both sit between your product and your customers, and they both need to be technical, so it's easy to treat them as the same hire. They aren't, and hiring the wrong one first usually shows up a few months later as stalled deployments or a stretched sales team.
Here's how the two roles differ, where solutions architects and sales engineers fit in, and how to work out which one your team needs next.
The short answer
A solutions engineer helps you win the deal. A forward deployed engineer helps the customer succeed once they've signed. Solutions engineers spend most of their time on demos, technical scoping and answering a buyer's questions. Forward deployed engineers spend most of theirs writing production code inside a customer's environment, getting your product live and shaping it around how that customer actually works.
Forward deployed engineer vs solutions engineer
| Forward deployed engineer | Solutions engineer | |
|---|---|---|
| Main stage | After the contract is signed | Before the contract is signed |
| Day to day work | Integrations, data pipelines, custom workflows, production fixes | Demos, proofs of concept, technical scoping, security questionnaires |
| Writes production code | Yes, most days | Sometimes, usually for demos and prototypes |
| Usually reports into | Engineering, or a dedicated forward deployed team | Sales or revenue |
| Success looks like | Customers live and using the product | Deals won and closed faster |
The overlap is real. Plenty of strong FDEs started out as solutions engineers, and the best solutions engineers can build a convincing prototype in an afternoon. The difference is where their week goes and who they answer to.
Where solutions architects and sales engineers fit
Solutions architects design how your product should fit into a customer's wider systems. In larger companies they often own the technical design for big accounts, while someone else does the build. In a startup, that design work usually lands with whoever is doing the deployment, which is often your FDE.
Sales engineers are close to solutions engineers, and many companies use the two titles for the same job. Where there is a difference, sales engineers tend to focus more on the demo and the technical side of the sales process, with less time spent on detailed scoping.
For an early stage AI company, the choice usually comes down to two hires: someone technical to help sell, or someone technical to help deliver.
Which one should you hire first?
Look at where deals are getting stuck. If prospects are interested but the sales process slows down every time a technical question comes up, a solutions engineer will probably make the bigger difference. If deals are closing but customers take months to go live, or your core engineers keep getting pulled into individual customer setups, you need a forward deployed engineer.
A few signs it's time for an FDE:
- Founders or senior engineers are personally handling most deployments.
- Customers are asking for integrations with systems your product doesn't support yet.
- The gap between signing and go live keeps getting longer.
- Product feedback from customers arrives secondhand, through account managers.
Many AI startups end up hiring both, and the two roles work well together when the handover is clear. The solutions engineer scopes what the customer needs, and the FDE builds it.
How the salaries compare
The two roles are usually paid differently. FDE packages tend to be base salary plus equity, in line with other senior engineering roles. Solutions engineers often have a larger variable element tied to sales targets, so it's worth comparing total pay rather than base salary alone.
For FDE base salary bands across the US, UK and Europe, see our agentic AI software engineering salary guide.
Hiring the right technical role with Trust in SODA
Our US and UK teams work with AI startups on forward deployed engineering and go to market hiring, so we see both sides of this decision regularly. If you're not sure which role you need first, or you're planning to hire several, we'd be happy to talk it through. Our guide on how to hire a forward deployed engineer covers the FDE side in more detail.
FAQs
Is a forward deployed engineer the same as a solutions engineer?
No. A solutions engineer mainly supports the sale through demos and technical scoping. A forward deployed engineer usually takes over after the deal and writes production code to get the customer live.
Can a solutions engineer become a forward deployed engineer?
Yes, and it's a common move. Solutions engineers with strong backend or integration experience often make good FDEs, since they already understand customers and know how to scope technical work.
What's the difference between a forward deployed engineer and a solutions architect?
A solutions architect designs how a product fits into a customer's systems. A forward deployed engineer designs it and builds it. In startups the two roles are often combined.
Who does a forward deployed engineer report to?
Usually engineering, or a dedicated forward deployed engineering lead. Keeping FDEs close to the product team makes it easier for what they learn from customers to shape the core product.