Three job titles get used interchangeably, and they should not be: sales engineer, solutions engineer, and forward deployed engineer. All three sit between engineering and the customer, but they own different stages of the relationship and a different amount of production code. Getting the distinction right matters for two reasons. If you are hiring, the wrong title attracts the wrong person. If you are sourcing, the strongest forward deployed engineers are usually sitting under one of the other two titles today. Here is the clean version.
The one-line difference
The simplest way to separate the three is by where they sit in the deal and whether they ship production code into the customer's environment.
| Role | Stage | Primary goal | Ships production code? |
|---|---|---|---|
| Sales engineer | Pre-sale | Help win the deal | Rarely; demos and POCs |
| Solutions engineer | Pre-sale into onboarding | Prove technical fit, design the solution | Sometimes; POCs and configuration |
| Forward deployed engineer | Post-sale | Make the deployment work and renew | Yes, in the customer's stack |
The sales engineer
A sales engineer, sometimes called a pre-sales engineer, sits inside the sales motion. Their job is to remove technical objections and help the account executive close: running demos, answering architecture questions, scoping a proof of concept, and being the credible technical voice in the room. They are measured on pipeline and bookings, usually with a significant variable or OTE component to their compensation. A sales engineer can read code and reason about systems, but they rarely ship production code into a customer's environment, and once the contract signs their involvement typically winds down.
The solutions engineer
Solutions engineer is the fuzziest of the three, because the title is used differently across companies. At most, a solutions engineer spans late pre-sale into early onboarding: scoping technical fit, designing the integration, building proofs of concept, and sometimes configuring the product for the customer's first use. Some solutions engineers write meaningful code; many do not own delivery end to end. The overlap with sales engineering on one side and forward deployed engineering on the other is exactly why the title causes confusion. If a solutions engineer is shipping production code inside customer environments and owning the outcome, they are effectively doing forward deployed work under an older label.
The forward deployed engineer
A forward deployed engineer, or FDE, owns the post-sale technical outcome. They embed with the customer after the contract signs, write and ship production code inside the customer's stack, build the integrations that make the product deliver value, and stay close enough to catch problems before they become churn. The model traces back to Palantir and is now standard at AI-native companies, where a product rarely works out of the box for an enterprise. The forward deployed engineer is the reason the deal turns into a working deployment and renews. Compensation is mostly base plus equity rather than variable, because they are an engineer, not a quota carrier. We cover the discipline in full on the forward deployed engineering specialism page, and the hiring playbook in how to hire a forward deployed engineer.
Why the titles get confused when you are sourcing
The practical consequence: if you advertise for a forward deployed engineer and wait for inbound, you get a thin and mismatched pile, because the people who can do the job mostly carry a different title today. The strongest FDE candidates are often sitting in solutions engineering, integration engineering, or sales engineering roles, wanting to write more production code and own delivery rather than only support the sale. Sourcing forward deployed engineers is a translation exercise, not a keyword match. The reverse mistake is just as costly: hiring a sales engineer and expecting them to embed and ship inside a customer's stack for six months is a miscalibration that ends badly for both sides.
How the three are paid
The three price differently, which matters when you write the offer. Sales and solutions engineers often carry a variable or OTE component tied to revenue. Forward deployed engineers are compensated as senior engineers, base plus equity, at a premium to comparable backend roles because of the scarcity and the customer exposure. In Australia in 2026, senior forward deployed engineers run roughly AUD 180-240k base in Sydney. For the full picture by city and discipline, see the Australian Tech Engineering Salary Guide 2026, or the city role pages for Sydney, Melbourne and Brisbane.
Which should you hire?
Decide by the stage you actually need owned:
- You need to win more technical deals. Hire a sales engineer.
- You need to scope fit and design integrations around the sale. Hire a solutions engineer.
- You need someone to embed after the sale and make the deployment work. Hire a forward deployed engineer.
Many companies need more than one of these as they scale, and at smaller companies one person often does all three. The mistake is assuming the titles are interchangeable when you write the brief, then being surprised when the hire optimises for a different stage than the one you needed.
The cleanest test: a sales engineer helps you sign the contract, a solutions engineer helps you design what you signed, and a forward deployed engineer makes it work in production. Hire for the stage you actually need owned.
FAQ
What is the difference between a forward deployed engineer and a solutions engineer?
A solutions engineer mostly works pre-sale and during onboarding, scoping technical fit and building proofs of concept. A forward deployed engineer owns delivery after the sale, shipping production code inside the customer's environment and owning the deployment through to renewal. Many forward deployed engineers were solutions engineers who wanted to own delivery and write more production code.
Is a forward deployed engineer the same as a sales engineer?
No. A sales engineer supports the sales motion before the contract, running demos and proofs of concept, usually with a variable or OTE compensation component. A forward deployed engineer is a post-sale software engineer who ships production code in the customer's stack, compensated as an engineer on base plus equity.
Do forward deployed engineers write production code?
Yes. Writing and shipping production code inside the customer's environment is the defining part of the role, which is what separates it from sales engineering and most solutions engineering work.
Which earns more, a solutions engineer or a forward deployed engineer?
It depends on company and structure, but forward deployed engineers typically command a premium to solutions engineers on base salary, reflecting the production engineering bar and the scarcity of the profile. Solutions and sales engineers may offset some of that with variable or OTE compensation.