Pilot · limited independent review. This is practice, not a certificate or a job guarantee. Before you start

Drillhall

Guide · Reviewed 2026-10-14

Forward deployed engineer vs solutions architect vs software engineer

A forward deployed engineer (FDE) is a software engineer who works inside a customer's organisation to make the product solve that customer's problem, writing production code in their systems, and who takes what they learn back to the core product [2][3]. A solutions architect mostly advises and rarely writes code on the customer's infrastructure [2]. A product software engineer builds one part of the product for every customer [1].

Side by side

AspectForward deployed engineerSolutions architectSoftware engineer (product)
Main jobMake the product work for one customer's real problem, using many parts of it [1][2]Advise the customer on how a solution should be designed [2]Build one part of the product for every customer [1][2]
Where the work happensInside the customer's organisation, often for months, alternating with the core product team [2][3]In advisory engagements with the customer [2]On the company's own product team [1]
Writes production code in the customer's systemsYes: connects the customer's systems and ships custom workflows [2][3]Rarely [2]No: writes the shared product [1]
Feeds back into the productYes, and this is the point of the role: a team split off into professional services loses that loop [2][3]Not a core part of the role [2]Owns the product itself [1]

Titles vary between companies. Read what a job posting asks you to do, not just its title.

Often confused with

  • Consultant. A consultant typically makes a one-off recommendation; an FDE usually stays with the customer and builds over the long term [2].
  • Pre-sales engineer with a new title. Some companies have renamed pre-sales solution engineers as FDEs without changing the work [3].

Practising the FDE side

Drillhall's missions practise the parts that differ from a product engineering job: interviewing stakeholders, scoping a pilot, recording a design decision, fixing code and proving it with tests, handling an incident, and writing for an executive. How we assess lists the nine areas, and the templates show the documents. To see a mission, try the free preview.

Sources

  1. Dev versus Delta: Demystifying engineering roles at Palantir · Palantir blog
  2. What are Forward Deployed Engineers, and why are they so in demand? · The Pragmatic Engineer (Gergely Orosz) · 2025-08-12
  3. The Palantirization of everything · a16z (Marc Andrusko) · 2026-01-16