A solutions engineer mainly helps sell a product: they show prospects it can solve their problem, using demos and proofs of concept. A forward deployed engineer (FDE) mainly gets the product working for real users: they work out what’s needed and ship production code. The simplest test is what happens after the contract is signed. A solutions engineer usually moves on to the next deal, and that’s when an FDE’s main work begins.
The titles overlap in practice, and that causes hiring mistakes. Here’s how to tell them apart and work out which one you need. For the broader role, start with what a forward deployed engineer is.
The differences at a glance
| Solutions engineer | Forward deployed engineer | |
|---|---|---|
| Main goal | Help win or keep the customer | Make the product work for real users |
| Timing | Mostly before the sale | Mostly after the sale, and ongoing |
| Usually reports to | Sales, or customer success if post-sales | Engineering, or a dedicated FDE team |
| Production code | Rarely. Demos, proofs of concept, scripts and configuration | Yes |
| Sales target | Often | No |
| Starting point | A prospect’s question | An unclear problem |
| Judged by | Deals won, or renewals | Whether it works for users and gets used |
The reporting lines and targets come from KORE1’s role comparison. KORE1 is a recruiting firm, and it notes that these titles get conflated even inside the companies posting them. Treat this table as the typical pattern.
What a solutions engineer does
A solutions engineer is the technical person in a sales process. The title’s close relatives are sales engineer and, in some companies, solutions architect. They learn what a prospect needs, map it to the product, answer the hard questions from the prospect’s technical team, build a demo or proof of concept, and help get the deal over the line. The US Bureau of Labor Statistics describes sales engineers as selling products or services that require technical expertise.
A proof of concept is a small working version that shows something can be done. It can skip what production code can’t: handling unusual cases, automated tests, security and anything needed to keep running for years. That’s why a proof of concept can look finished without being close to finished.
Some solutions engineers work after the sale too. KORE1 describes a post-sales version who sits in customer success or professional services, writes some scripts and configuration, and has a renewal or retention target.
What an FDE does
An FDE starts with a problem that isn’t fully defined, works directly with users or customer stakeholders, and ships a working answer into production. They might connect the product to a customer’s systems, fix what breaks on real data, or build what the product is missing. What they learn should change the product for everyone else.
Insight Partners’ panel draws the line sharply: FDEs don’t build demos, solution engineers do. First Round Review makes the same point from the other side, stressing that the FDE remains an engineer who writes and debugs production code, unlike a solutions consultant or sales engineer. Tiffany Siu, First Round’s head of talent, says Palantir FDEs passed the same interview loops as its software engineers.
The Pragmatic Engineer gives a useful example from OpenAI, where solutions architects are mostly advisory and rarely write code on customer systems, while FDEs do it directly.
Where the titles blur
Don’t rely on the title alone, for three reasons.
Some FDE jobs are sales jobs. PostHog notes that some roles with the FDE title look more like technical consulting or sales engineering. The title is popular, so companies have a reason to apply it to existing roles.
Some solutions engineers build real things. Post-sales solutions engineers can do meaningful technical work, and some may be capable of an FDE role. A title tells you where they sit in the organization, not what they can do.
Early-stage companies mix them. At a small startup, the same person may run a demo on Tuesday and ship an integration on Thursday. That’s fine, but be honest about which half is the actual job, because the two require different skills and different measures of success.
Four questions cut through this, whether you’re reading a job description or a résumé:
- Does the person commit code that runs in production?
- Do they carry a sales target?
- What do they do after the contract is signed?
- Who do they report to?
Pay, briefly
Pay data for both roles is messy, and the sources don’t measure the same thing. The Bureau of Labor Statistics puts the median wage for all US sales engineers at $124,900 as of May 2025, covering many industries beyond software. For FDEs, Bloomberry’s analysis of job postings, as reported by Paraform, gives a median base of $173,816. That doesn’t compare like with like, since one is a broad government figure and the other a base salary from postings in a hot market. Solutions engineers may also earn commission on top. For how FDE costs add up across routes, see forward deployed engineer cost.
Which one do you need?
| Your situation | Likely hire |
|---|---|
| Prospects stall because nobody can run a technical demo or answer security questions | Solutions engineer |
| You lose deals in evaluation, and your founder or CTO is doing every demo | Solutions engineer |
| Deals close, but customers don’t get live | FDE |
| The product works in demos and fails on real customer data | FDE |
| You need someone to work out from users what to build, and then build it | FDE |
| You’re pre-sales and need to prove the product on a prospect’s real data | Either, depending on who will finish the job |
The last row needs a word of explanation. Looker’s co-founder told First Round that it used forward deployment during free trials, working with prospects’ real data. If the trial work has to become the real system, an engineer who can ship is worth more. If it’s only there to win confidence, a solutions engineer is enough.
Siu’s test applies here too: if you define success as closing deals or running demos, the role is closer to sales. Hire accordingly, because a good FDE is unlikely to stay happy running demos, and a good solutions engineer may not want to own production code.
Not sure you need either? When do you need a forward deployed engineer covers the signs, and how to hire a forward deployed engineer covers what to test for.
How the two work together
If you have both, plan the handover. Don’t let everything the solutions engineer learned disappear when the deal closes. Two of the companies on Insight’s panel, nCino and ServiceNow, bring the customer success manager and sales rep in from the first FDE conversation. Whatever your setup, keep the promises made during the sale in writing, because the FDE is the person who has to make them true.
Where epicX fits
epicX places forward deployed engineers, not solutions engineers. Its engineers work with users and ship, and you direct them and own the result. If your bottleneck is after the sale, or nobody is close enough to users, see how to hire a forward deployed engineer through epicX, from $5K a month. If you mainly need someone to run demos, you’re better off hiring a solutions engineer.