Forward deployed engineer vs solutions engineer vs consultant: which do you need?
Three titles that sound alike and leave behind very different things: a demo, a plan, or a running system. Here's how to tell them apart before you sign.
The verdict
4 things that decide this
- 01Choose a forward deployed engineer when the product has to run on your systems and your data, and nobody on your side can carry the integration. Choose a solutions engineer when you're still evaluating a product. Choose a consultant when the question is what to do, not how to build it.
- 02The three roles differ on two things: who writes the production code, and how long the person stays. A solutions engineer builds a proof of concept, usually on sample data, then moves to the next prospect. A consultant recommends. A forward deployed engineer writes the code on your infrastructure and stays through go-live.
- 03Labels drift. Some vendors call their post-sales integration staff solutions engineers; some consultancies embed engineers who behave like FDEs. Apply the two tests above rather than the title, and ask which repository the code will live in and who approves the pull requests.
- 04Below enterprise scale, the FDE column is usually filled by a senior engineer embedded from a partner firm, since the labs keep their own FDE teams for their largest accounts. That's the engagement Hashlogics runs under staff augmentation, and it's built to end in a handover rather than a dependency.
The three roles, side by side
| Question | Solutions engineer | Consultant | Forward deployed engineer |
|---|---|---|---|
| When they're involved | Before the sale, during evaluation | Before and around a decision | After the sale, through go-live |
| Who writes production code | Rarely; proofs of concept on sample data | Usually nobody; plans and recommendations | They do, on your infrastructure |
| Whose systems they work in | The vendor's demo environment | Documents, workshops, interviews | Yours: repository, data, tooling |
| How long they stay | Until the deal closes | Until the report is delivered | A defined period, until it runs |
| What they're measured on | Deals won | Quality of the advice | Whether it runs in production |
| What they leave behind | A demo and a proposal | A plan you own | A running system, plus feedback into the product |
| Best when | You're choosing a product | You're choosing a direction | You've chosen, and now it has to work |
Why the labels blur
The overlap is real, and the reference sources say so. Wikipedia's entry (read 2026-09-01) lists the roles an FDE's duties overlap with: solutions architects, sales engineers, customer engineers, professional services engineers, systems integrators and IT consultants. Six titles, for a job most companies staff with two people.
Colin Jarvis set up OpenAI's forward deployed engineering team in 2025 and gave The Pragmatic Engineer the cleanest split. FDEs 'are more hands-on and typically work with more ambiguity than SAs traditionally do.' They 'write code directly on customer infrastructure and use customer tooling.' A solutions architect works on sample data. An FDE works on yours.
Consultants sit on the other side of the line for a different reason: how long they stay and what they hand over. Gergely Orosz's phrasing in the same piece: consultants 'make one-off recommendations, whereas FDEs generally work with customers, long-term.' A consultant's job ends when the document lands. An FDE's ends when your system runs.
Match the role to where you are in the purchase
Work out which stage you're at, then hire for that stage only. Buying the wrong role isn't a disaster; it's a delay, because you'll end up hiring the right one afterwards.
- 01You haven't picked a vendor: ask for a solutions engineer and insist the proof of concept runs on your data, not theirs.
- 02You have a process problem and no clear build yet: a consultant, on a fixed scope, with a written output you own outright.
- 03You've bought or built the product and it has to live in your ERP, your CRM or your records system: that's FDE work. If the vendor won't send one, an embedded senior engineer does the same job.
- 04You're a mid-sized business: expect the vendor's FDE team to be reserved for its largest accounts, and plan for the embedded route from the start.
- DecideConsultant: what should we do?
- EvaluateSolutions engineer: does the product fit?
- BuyContract signed; the demo team leaves.
- DeployForward deployed engineer: make it run here.
- RunYour team, a service level, or both.
Most stalled AI projects bought the first two stages and never staffed the fourth.
Related questions
01Is a forward deployed engineer the same as a professional services engineer?+
Close, and often the same person under a different title. Professional services engineers configure and integrate a vendor's product after the sale. A forward deployed engineer does that, writes new code, and feeds what they learn back into the product. Wikipedia lists professional services among the roles FDE duties overlap with. Ask whether the person can change the product or only configure it.
02Can a solutions engineer do the FDE job after the sale?+
Only if they can write production code and the vendor lets them stay on your account. Most can't, for structural reasons: solutions engineers are measured on deals and move to the next prospect once one closes. If a vendor offers its solutions engineer for the deployment, ask how many hours a week they'll be in your repository and for how long.
03Do consultants ever write production code?+
Yes, some do, and at that point they're doing FDE work under a consulting contract. The test is the deliverable. If the contract ends with a document, it's consulting. If it ends with code running in your environment that your team owns, it's a forward deployment, whatever the letterhead says.
Related
- What is a forward deployed engineer? →The definition, the Palantir origin and the three names for one role.
- What does a forward deployed engineer actually do? →The week as it happens: data, operators, code, feedback.
- Can a small or mid-size business get a forward deployed engineer? →Yes, through an embedded senior engineer. What the engagement looks like.
- Hire forward deployed engineers →A senior engineer embedded in your operations, from a free scoping call.
- Staff augmentation vs outsourcing →The adjacent decision, once you've chosen the embedded route.
- Staff augmentation →How our embedded engineers join and stay.
