Forward deployed engineer vs solutions engineer vs consultant: who to hire
A solutions engineer shows it can work, a consultant says what to do, and a forward deployed engineer makes it run. One invented project shows where each stops.
Short answer
A solutions engineer works before the deal: demos and proofs of concept that help close it. A forward deployed engineer works after the deal, writing and running software inside the customer’s systems until it works in production. A consultant advises and hands over a plan. Hire by the gap: a stalled sale, a stalled rollout, or an unclear strategy.
On this page
- Roles compared
- Solutions engineer, consultant, forward deployed engineer
- Based on
- Palantir, The Pragmatic Engineer, a16z, Paraform and Varick Agents, read 2026-10-19
- Not found
- Consultant pay, and how consultants are measured
The verdict
- Hire a solutions engineerwhen deals stall at technical evaluationThey run demos and build proofs of concept so the buyer can picture it working. Skip them if the sale is closed and the product needs custom work inside the customer’s systems.
- Hire a forward deployed engineerwhen deals close but rollouts stallThey write and run software inside the customer’s environment and stay until it works. Skip them if the real gap is an unclear strategy, or if documentation could solve the problem.
- Hire a consultantwhen leaders disagree on what to do firstYou get an analysis and a roadmap, plus help getting executives aligned. Skip them if you need software running in production by the end.
- Or cover every teamwhen one team at a time is too slowForward deployed engineers are scarce and each covers a few teams. Software that runs the same playbook for every team is the alternative we build.
Nolli makes software in this area. We compare from each vendor’s public pages and name our sources below. We did not run hands-on tests.
Key takeaways
- The three roles differ by when they work and what they leave behind: a solutions engineer leaves a proven demo, a consultant leaves a plan, and a forward deployed engineer leaves software running in production.
- Titles blur between companies, so read the job itself: does the person write code on the customer’s systems, and do they stay after launch?
- Forward deployed engineers are scarce and cover one team at a time, so decide whether you need their deep builds or the playbook they follow for every team.
Take one invented project. A 300-person distributor wants an AI agent to handle supplier invoices that do not match their purchase orders. Today those invoices land in a shared inbox and wait for someone in accounts payable to sort them out.
Three different people could touch it: a solutions engineer, a forward deployed engineer (FDE) and a consultant. The titles sound alike. The jobs do not, and hiring the wrong one wastes time and money. We follow the one project through all three, then compare them. The project is an illustration, not a customer story and not Nolli data. For the role itself, see our guide What is a forward-deployed engineer?
One thing first. A solutions engineer and an FDE usually work for the company that sells the software. A consultant is usually hired by the company that buys. So this post has two readers: a startup choosing which technical person to hire, and a buyer choosing whom to ask for help.
One project, three roles
Here is the invoice project in order. Watch where each person enters and where they leave.
- Before the dealThe solutions engineer shows it can workThe vendor’s solutions engineer joins the sales calls, answers the distributor’s architecture questions, and builds a proof of concept on sample invoices. The goal is a signature. After it, their involvement typically winds down.
- Any time the buyer choosesThe consultant says what to doThe distributor hires a consultant, who interviews the accounts payable team and the finance leaders, and ranks the ideas. The product is a roadmap: do invoices first, then purchase approvals. The consultant leaves when the report is accepted.
- First weeks after the dealThe FDE maps the real workThe vendor’s FDE sits with the accounts payable team and watches how mismatched invoices are really handled. This is where the unwritten rules show up: which supplier always sends the wrong unit, who is allowed to approve a price difference.
- The following monthsThe FDE builds, runs and measuresThe FDE writes the agent inside the distributor’s accounting system and inbox, runs it on real invoices, and compares the result with the old way. People keep approving the risky cases. The FDE stays until the number holds.
Look at what each one leaves behind. The solutions engineer leaves a demo that convinced someone. The consultant leaves a document. The FDE leaves software that runs on the distributor’s invoices, plus a number that says whether it beat the old way. Paraform, a recruiting marketplace, names a fourth role, the customer engineer, who takes over once the deployment is stable. We leave that role out.
The solutions engineer: a test drive
A test drive lets you feel the car on a road the dealer chose. You do not own the car yet, and nobody has checked it fits your garage. A solutions engineer runs the test drive.
Solutions engineer
A technical person in the pre-sale cycle. Per Paraform, they run technical demos, answer architecture questions and build proof-of-concept environments so that sales can close deals.
Paraform says their main measure is revenue influenced, not code shipped, and that their pay leans on variable pay tied to deals closed. The Pragmatic Engineer describes the closest role at OpenAI, the solutions architect, as advisory: they rarely write code on customers’ infrastructure and usually build proofs of concept on anonymized or offline cuts of data.
That is the right design for the job. It is also the limit. Paraform says AI products are easy to demo and much harder to deploy inside a Fortune 500 company’s infrastructure. A proof of concept on sample invoices says nothing about the supplier who sends the wrong unit every month.
The forward deployed engineer: the builder who moves in
Picture a builder who moves into your house and works there until the lights come on. That is the FDE. Palantir created the role in the early 2010s and called its engineers Deltas. Their mandate, in Palantir’s words, is to achieve technical outcomes for one customer, measured by impact on that customer’s goal.
Forward deployed engineer
An engineer who embeds with a customer’s team, learns how the work really gets done, then builds and deploys software inside that team’s workflows and stays until it runs in production. See our glossary entry.
The Pragmatic Engineer reports how OpenAI draws the line against the solutions architect: FDEs write code directly on the customer’s infrastructure, using the customer’s tools, and handle more ambiguity. Our guide adds the order of work. Varick Agents, an FDE firm, spends at least four weeks watching how the work is really done before it touches a model. The reason is the gap between the written process and the real one, and Varick’s Daniel Kornum says automation built for the documented process breaks on roughly 30% of the volume.
The reason this role became so sought after is the gap a demo cannot close. The investor a16z wrote that enterprises buying AI are like a grandmother getting an iPhone: “they want to use it, but they need you to set it up.” The FDE is the person who sets it up.
Three limits, from our guide. FDEs are scarce and expensive. Each engagement lights up one team at a time. And the map of how the work happens leaves with them when they go. On pay, Paraform reports an average of $238,000 for FDEs against $155,000 to $210,000 for solutions engineers. Paraform does not say what sample those figures come from, so treat them as one recruiter’s view.
The consultant: the surveyor with a report
A surveyor inspects the house and writes up what to fix and in what order. The report can be excellent. It does not repair the roof. An AI consultant works the same way, and our guide says a consultant mostly advises and hands over a plan.
Palantir’s own Deltas draw the line this way: consultants generally produce a one-time analysis, recommendation or solution, while a Delta works with the customer to build something that lasts. The Pragmatic Engineer says the same, one-off recommendations against long-term work. Palantir’s engineers also grant the overlap. Both want the customer to get better at what it does.
Our own comparison page gives the consultant real strengths: executive alignment, strategy and change management across a large organization. Its limit is that an assessment built from interviews and workshops captures what people remember at one moment, and it ages. That describes an interview-based assessment, not every consultancy. Some also build. I found no figure for consultant pay or for how consultants are measured in the sources I read, so the table below says so.
What each one does
| Solutions engineer | Consultant | Forward deployed engineer | |
|---|---|---|---|
| Scopes the problem | partly | fully | fully |
| Builds software | partly | none | fully |
| Ships it to production | none | none | fully |
| Owns the result after launch | none | none | fully |
| Advises on strategy and gets leaders aligned | partly | fully | partly |
none partly fully · Our reading of the sources listed at the end, not a measurement. A full circle means the role does this as its main work, a half circle means a smaller part of the job. It shows the typical role as the sources describe it; titles vary, and some consultancies and some FDEs do more than shown.
| Solutions engineer | Consultant | Forward deployed engineer | |
|---|---|---|---|
| Usually works for | The company that sells the software. | The company that buys. | The company that sells the software, or a firm that sells FDE work. |
| When | Before the deal. | At the buyer’s choice. | After the deal. |
| Leaves behind | A demo and a proof of concept. | An analysis and a roadmap. | Software in production and a measured result. |
| Measured on | Revenue influenced (Paraform). | Not found in the sources I read. | Impact on the customer’s goal (Palantir). |
| Reported pay | $155,000 to $210,000 (Paraform). | Not found. | Average $238,000 (Paraform). |
| Main limit | A demo is not production. | A plan does not run, and it ages. | Scarce, and one team at a time. |
Positions are our reading of the sources, not measurements. Horizontal: whether the role works on the customer’s own systems and data or on samples and in meetings, per The Pragmatic Engineer and Paraform. Vertical: how much working software the role ships, per the same pages and Palantir.
Who to hire
Pick a solutions engineer if
your product is sound but deals stall when a technical buyer asks “will it work here?” Skip them if the buyer is already signed and waiting on custom work.
Pick a forward deployed engineer if
deals close but the rollout stalls inside the customer’s systems, and the fix is custom engineering your core team should not own. Skip them if a clearer strategy or better documentation would solve the problem.
Pick a consultant if
the open question is what to do first and who agrees. Skip them if you expect running software at the end.
Combine them if
the project is large. The consultant ranks the ideas, the vendor’s solutions engineer proves the first one can work, and the FDE builds it.
Or give every employee FDE capabilities
Every limit in the FDE section comes from the same cause. An FDE engagement lights up one team for a few weeks, and a company has dozens of teams. The best FDEs are scarce, and what they learn about how work really runs can walk out with them.
Nolli’s aim is to run the first half of the FDE playbook continuously, for every team. It learns how the work happens from people’s work on company devices, their email and calendar, and the logs of the AI agents they use, then shows where AI belongs, checks it on the company’s own work, and shares what works as skills, SOPs and agents. Its limits are real. Nolli is software, not an engineer. It does not write and ship a custom integration inside your systems, so for a deep build on your hardest problem you will often still want an FDE, who then starts from a current map instead of weeks of interviews. It is not a consultant either, and it will not align your executives for you.
Where Nolli fits
Where Nolli fits, and where it does not
Nolli is AI discovery. It does the mapping and proving that FDEs do by hand, for every team at once, and keeps the map current. It does not replace the FDE who builds, the solutions engineer who sells, or the consultant who aligns leaders. We have no customer results to quote. Your company decides what is captured and who sees the results. See Why Nolli. No public price. Request a demo.
Request a demoQuestions people ask
Is a forward deployed engineer the same as a solutions engineer?
No. A solutions engineer works before the contract, showing with demos and proofs of concept that a product can work. A forward deployed engineer works after the deal, inside the customer’s environment, and owns making it work in production.
Is an FDE just a consultant with a different title?
Palantir’s Deltas say no: consultants generally deliver a one-time analysis or recommendation, while a Delta builds a long-term solution with the customer. The Pragmatic Engineer notes that some companies treat the FDE as a technical consultant, so read the job description.
How much more do FDEs earn than solutions engineers?
Paraform, a recruiting marketplace, reports an average of $238,000 for FDEs and $155,000 to $210,000 for solutions engineers in 2026. It does not say what sample those figures come from.
Which should a startup hire first?
Paraform suggests a solutions engineer first if you sell to enterprises and deals stall at evaluation, and an FDE once customers need complex custom deployments. That is one recruiter’s rule of thumb, not a law.
Do we need to hire an FDE to adopt AI?
You need what FDEs do: see the real work, decide where AI belongs, build inside your existing tools, and prove the result. You can hire for it, train your own people in the playbook, or use software that runs discovery across every team.
Sources
- “Dev versus Delta: Demystifying engineering roles at Palantir.” Palantir Blog, April 8, 2019.
- Gergely Orosz. “What are Forward Deployed Engineers, and why are they so in demand?” The Pragmatic Engineer, August 12, 2025.
- John Kim. “Forward-Deployed Engineer vs. Solutions Engineer vs. Customer Engineer: What Startups Actually Need in April 2026.” Paraform (a recruiting marketplace), April 22, 2026.
- Joe Schmidt. “Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in Startups.” Andreessen Horowitz, June 4, 2025.
- Daniel Kornum. “If AI is so great, why isn’t it working?” Varick Agents.
- “AI Forward Deployed Engineering: The blueprint to breaking into FDE in 30 days.” Varick Agents.
- Greg Isenberg, with Vasuman Moza of Varick Agents. “Become a $1M/yr FDE (Full Course).” The Startup Ideas Podcast, October 1, 2026.
Plain-text copy: /blog/forward-deployed-engineer-vs-solutions-engineer-vs-consultant.md