Forward-deployed engineer / comparisons
Forward-deployed engineer vs solutions engineer: what's the difference?
A solutions engineer supports the sale — demos, proofs of concept, pre-sales architecture — and their accountability ends when the customer signs. A forward-deployed engineer's accountability begins there: they write production code inside the customer's environment after the deal closes, and they own whether it delivers the promised result. The shorthand is that a solutions engineer proves it can work and a forward-deployed engineer makes it work.
Side by side
| Forward-deployed engineer | Solutions engineer | |
|---|---|---|
| Point in the deal cycle | After signature, through production and adoption | Before signature, through the technical win |
| Primary output | Production code in the customer's systems | Demos, POCs, reference architectures, RFP responses |
| Accountable for | Whether the deployed system produces the promised outcome | Whether the deal clears its technical bar |
| Codebase | The customer's production repo, and the vendor's product | Demo environments and sandboxes |
| Shape of attention | Few customers, months to years deep | Many prospects, weeks shallow |
| Usually reports into | Engineering, or a dedicated delivery org | Sales |
| Compensation shape | Base plus equity, rarely a quota | Base plus variable tied to quota |
What a solutions engineer actually does
A solutions engineer (sometimes sales engineer or pre-sales engineer) is the technical half of a sales team. They scope the customer's problem, run demos and proofs of concept, design reference architectures, answer security and compliance questionnaires, and carry the technical argument through to signature.
Where they overlap
In practice the boundary is soft and getting softer. Plenty of forward-deployed engineers are pulled into late-stage deals as the technical closer, because the person who will own the build is the most credible voice on whether it can be built. And at smaller companies the same person often does both jobs under one title. The distinction that survives is accountability, not activity: if the role's success is measured at signature, it is a solutions engineer; if it is measured in production, it is an FDE.
What the hiring data shows
The overlap is measurable. Across the 674 machine-readable job descriptions in Plank's census, 35% mention pre-sales or solutions work as part of the FDE job — so a third of forward-deployed roles explicitly expect their engineers in the sales cycle. 16 postings (1.6% of the census) fuse the two titles outright, at companies including NODA, Aircall, ServiceNow, Accelerant. The titles are converging, and the postings show it.
From Plank’s first-party census of 982 verified open FDE roles across 462 companies, observed 2026-09-04. The census covers FDE-titled postings, so it describes the forward-deployed side of this comparison; it is not a survey of solutions engineer roles.
Which one do you need?
Forward-deployed engineer
- The product genuinely does not work in a customer's environment without engineering effort.
- Deals are closing but deployments are stalling, churning, or quietly never going live.
- You need someone accountable for an outcome after the contract is signed.
Solutions engineer
- Deals are stalling before signature on technical objections.
- The product deploys cleanly and the gap is trust and proof, not integration.
- You need to cover many prospects at once rather than go deep in a few.
Questions people ask
- Is a forward-deployed engineer the same as a solutions engineer?
- No. A solutions engineer is accountable for winning the technical argument before a contract is signed; a forward-deployed engineer is accountable for the system working in production after it is. They overlap in the late deal cycle, and some companies fuse the titles, but the point of measurement is different.
- Do forward-deployed engineers do pre-sales work?
- Often, yes. 35% of the FDE job descriptions in Plank's census mention pre-sales or solutions responsibilities. The difference from a solutions engineer is that pre-sales is a secondary duty rather than the job.
- Which pays more, an FDE or a solutions engineer?
- They are structured differently rather than simply ranked. Solutions engineers typically earn a base plus variable pay tied to quota attainment. Forward-deployed engineers are usually paid as engineers — base plus equity, no quota — which at frontier AI labs pushes total compensation well past what a comparable solutions engineer earns, mostly through equity.
- Can a solutions engineer become a forward-deployed engineer?
- It is one of the most common paths in, provided the engineering is real. The customer-facing instincts transfer directly. What usually needs building is depth in production code — owning a system on-call, integrating with a real system of record, and shipping against someone else's data model.
Still working out the definition itself? Start with what a forward-deployed engineer is, or see who is hiring them and for how much.