Emerging roles
Forward deployed engineer vs solutions engineer: what's the difference?
The main difference is production ownership. A solutions engineer designs, prototypes and advises, usually during the sales process and across many accounts, then hands the build to others. A forward deployed engineer builds the solution, ships it into the customer's production environment after the deal and is accountable when it breaks, usually for one to three customers.
Side by side.
| Question | Forward deployed engineer | Solutions engineer / architect |
|---|---|---|
| Main job | Build and ship into production | Design, prototype, prove value |
| When | Mostly after the contract is signed | Mostly during the sales cycle |
| Coding | Most of the week, production code | Proofs of concept and demos |
| Accounts | One to three, in depth | A portfolio of many |
| Owns | The outcome in production | The design and the technical win |
Which fits you?
- Choose FDE if you want to spend most of your time building, enjoy ambiguity and want to own outcomes in production.
- Choose solutions engineering if you prefer design and advisory work, like the sales rhythm and would rather own the architecture than the 2 am incident.
Common questions
Is a forward deployed engineer more technical than a solutions engineer?
Usually, in hands-on coding: FDEs write production code most of the week, while solutions engineers code mainly for prototypes and demos.
Can a solutions engineer become an FDE?
Yes, especially with strong coding skills. Show projects where you built and shipped something to production and owned it afterwards.
Your next step
Make your experience easier to understand.
Review your experience and preferences. Decide which introductions are right for you.