Forward Deployed Engineer vs. Solutions Engineer: Which Do You Need?

A solutions engineer works before the contract and is measured on deals influenced. A forward deployed engineer works after it, ships production code into the deployment, and is measured on whether it succeeds. Which one you need is determined by where deals are stalling: before signature points to solutions engineering, after signature points to forward deployment.

These four titles are used loosely enough that two companies advertising the same role often want different people. The separation that holds up is not seniority or skill, but which side of the contract the work sits on and whether the person ships code.

The four roles, separated properly

The third column is the fastest test. If the person cannot open a pull request against either your product or the customer's integration, you are hiring account management or consulting, whichever the fourth column says. Both are legitimate roles. Neither is a forward deployed engineer, and advertising one while meaning another wastes a search.

Diagnose from where deals stall

Rather than choosing from job descriptions, look at where your pipeline actually loses time.

• Stalling before signature on technical objections, security review, or "can it do X": that is pre-sales. A solutions engineer.
• Closing, then taking months to go live: that is post-sale technical work. A forward deployed engineer.
• Live but unhappy, with recurring escalations and unclear ownership: that is a technical account manager, or a product problem wearing a staffing costume.
• Live, happy, but every customer needed bespoke work: forward deployed engineering, plus a product conversation about what should be generalised.

The incentive problem in combining them

Small companies frequently make one person cover pre-sales and post-sale technical work. It works briefly and fails in a predictable direction.

Pre-sales work is urgent and visible: a deal is waiting, a date exists, someone in revenue is asking. Post-sale work is important and invisible: the customer already signed, and the cost of it going slowly lands next quarter. Given one calendar, the urgent half wins every week, and the deployment backlog grows quietly until a renewal is at risk.

If you have to combine them, do not rely on the person to balance it. Protect post-sale time explicitly, and measure the deployment outcomes as well as the deals.

Where the role should report

Engineering, with a strong dotted line to revenue. This matters more than most org decisions at this scale, because the reporting line determines what the person actually spends their week doing regardless of the job description.

Reporting into customer success tends to convert the role into escalation handling, because escalations are what that function is measured on and they always arrive with urgency attached. The engineering line preserves the thing you hired for: someone building reusable solutions rather than absorbing tickets.

The dotted line matters too. Without exposure to revenue priorities, forward deployed engineers optimise for technical elegance over the deal that is actually at risk.

Common questions

Is a forward deployed engineer the same as a sales engineer?

No. A sales engineer works before the contract and is measured on deals influenced. A forward deployed engineer works after it and is measured on whether the deployment succeeds. The skills overlap and the incentives do not, which is why combining them into one role tends to starve whichever half is not being measured.

What is the difference between a forward deployed engineer and a technical account manager?

A technical account manager owns the relationship and coordinates resolution. A forward deployed engineer owns the technical outcome and resolves it themselves. If the person cannot merge a pull request, the role is account management with a technical vocabulary.

Should a forward deployed engineer report to engineering or to customer success?

Engineering, with a dotted line to the revenue side. Reporting into customer success tends to convert the role into escalation handling, because that is what the surrounding function is measured on. The reporting line determines what the person actually spends their week doing more reliably than the job description does.

Do we need a forward deployed engineer or a solutions engineer first?

Solutions engineer first if deals are stalling before signature on technical objections. Forward deployed engineer first if deals are closing and then taking months to go live. The symptom tells you which side of the contract your constraint sits on.

Can one person cover both roles?

At very small scale, briefly. It breaks predictably: pre-sales work is urgent and visible, post-sale work is important and invisible, so the pre-sales half consumes the calendar. If you must combine them, protect the post-sale time explicitly rather than hoping it survives.