fde
FDE vs Solutions Engineer vs Solutions Architect vs Sales Engineer
Forward deployed engineer vs solutions engineer: FDEs ship production code at the customer, SEs win the deal. Compared with SA and sales engineer.

Prepare for the Forward Deployed Engineer loop
The difference between a forward deployed engineer and a solutions engineer is what happens after the deal. A solutions engineer (or sales engineer) helps win it with demos and technical answers; a solutions architect designs how the product should fit the customer's systems; a forward deployed engineer stays with the customer and writes the production code that makes the product work in their environment.
The FDE side of this comparison draws on our web research into FDE interview loops at eight companies, built from 23 public sources including candidate write-ups, interview guides, a Blind thread and Sierra's own engineering blog.
Titles are inconsistent across companies, so treat the matrix below as the definitions the titles usually carry, and read the job post itself before deciding which role a listing really is.
The four roles in one matrix
| Forward deployed engineer | Solutions architect | Solutions engineer | Sales engineer | |
|---|---|---|---|---|
| Main output | Working production code at one customer | Reference designs and integration plans | Demos, proofs of concept, technical answers | Demos and technical answers during a sale |
| Writes production code? | Yes, daily | Sometimes, mostly prototypes | Proofs of concept | Rarely |
| Tied to a sales quota? | Not as a rule | Sometimes | May share a team target | Usually |
| Customers at a time | One or a few | Several | Many | Many |
| When engaged | After the deal, through go-live | Before and after the deal | Before the deal | Before the deal |
| Owns the outcome | The customer's people using it | The design being sound | The technical win | The technical win |
None of these rows comes from a single source; they are the common meaning of each title, and you will find exceptions. The one row that is reliable across companies is the first: what the person produces.
Reading a job post
Three phrases decide it quickly. "Embedded with" or "deployed at" a named customer means FDE; that is the strongest tell. (We checked a Salesforce lead FDE posting for Agentforce on Built In; it was removed in June 2025 and describes hands-on development and customer support rather than using the word "embedded", so do not rely on any single posting's wording.) "Quota", "pipeline" or "technical win" means a sales-aligned role regardless of title. "Reference architecture" and "best practices" mean solutions architecture.
Watch for hybrids. Decagon's Deployment Strategist and Palantir's Echo (Deployment Strategist) roles sit between FDE and solutions work: Palantir's Echo is reported as an analyst-generalist role with 25 to 75 percent travel and Python, R or SQL (Ophy), and Decagon's is described by Paraform as a first-hire role open to ex-founders (Paraform). If you want to write code every day, ask the hiring manager what fraction of the week goes to code.
How the interview loops differ
The FDE loop is the one with public evidence. Across the companies we researched, it combines practical coding, a decomposition or case round, applied-AI design at the labs, and behavioral questions about customers (Aced on Palantir, Aced on Databricks, Aced on OpenAI). Coding is the round that separates it from sales-side loops, and FDE coding is reported to be real, if easy to medium.
For solutions and sales engineering loops, our research did not cover company-specific interview reports, so the following is inferred from the roles. Expect a demo or presentation round, a discovery role-play, and a lighter technical screen. The discovery role-play overlaps with FDE prep: Anthropic's applied AI loop reportedly includes a 45-minute discovery call against an interviewer playing a VP of Engineering (getperspective), and the rubric (questions before pitch, reflect back what you heard, handle skepticism) would serve a solutions engineer equally well.
So if you are preparing for both kinds of role, discovery practice transfers in both directions. Coding practice transfers only toward FDE.
FDE vs solutions engineer: the short version
| FDE | Solutions engineer | |
|---|---|---|
| After the deal or before? | After, through go-live | Before, to win it |
| Daily work | Writes and ships production code at the customer | Demos, proofs of concept, technical Q&A |
| Measured on | The customer using what was built | The technical win in the sale |
| Quota | Not as a rule | Often a shared target |
"FDE vs SE" and "forward deployed engineer vs sales engineer" are the same comparison: the SE or sales engineer is a pre-sales role, the FDE is a post-sales engineering role. The solutions architect sits between them, designing how the product fits the customer's systems.
Which one to pick
Pick FDE if you want to write production code and are happy to trade depth in one product for breadth across a customer's systems. Pick solutions architecture if you like design and want to influence many deployments without owning each one. Pick solutions or sales engineering if you enjoy the sale itself: the demo, the objection, the technical win.
If the choice is really FDE against a product engineering role, FDE vs software engineer covers that comparison, and what a forward deployed engineer is explains the role from the start. The FDE interview guide lays out each company's loop.
Frequently Asked Questions
What is the difference between a forward deployed engineer and a solutions engineer?
A solutions engineer helps win the deal with demos, proofs of concept and technical answers. A forward deployed engineer works at or with the customer after the deal and writes the production code that makes the product work there. The main output differs: working code versus a technical win.
Forward deployed engineer vs solutions architect: which writes more code?
The FDE, by a wide margin. A solutions architect designs reference architectures and integration plans and typically writes prototypes; an FDE typically ships production code most days.
Is a sales engineer the same as a solutions engineer?
Often used interchangeably, but sales engineer usually signals a role tied to a quota during the sale, while solutions engineer can include broader pre-sales and onboarding work. Titles vary by company, so read the job post.
Which role pays more, FDE or solutions engineer?
It varies by company and by how much of the pay is variable. FDE pay varies widely by company and level, so check current offers on levels.fyi; we do not give a solutions engineer figure because compensation there depends heavily on quota attainment.
Can a solutions engineer become a forward deployed engineer?
Yes, if you build the coding and decomposition skills FDE loops test. Discovery and customer skills transfer directly; production coding is the gap to close.
How do I prepare for a forward deployed engineer interview?
Practise practical coding, problem decomposition, customer discovery, applied-AI design and behavioural questions. See the FDE interview guide and FDE interview questions.
Start with the free FDE lessons
The FDE track on thita.ai opens with two free patterns: what a forward deployed engineer is and the decomposition framework, plus two worked case studies, improving city traffic with sensor data and a logistics client losing money on deliveries. The full track adds AI mock interviews for five FDE rounds: decomposition, customer discovery, applied-AI design, practical coding and behavioral. Its free lesson on FDE vs SWE, solutions engineer, solutions architect and sales engineer goes deeper on this comparison.
Topics
Your next step
Prepare for the Forward Deployed Engineer loop
The FDE track walks through the rounds FDE loops use, decomposition, coding and customer scenarios, then lets you rehearse them out loud with an AI interviewer that asks follow-up questions.