Learn · Role clarity
Real FDE vs renamed solutions engineer
Forward Deployed Engineer is spreading fast. Some openings are the real job. Many are Sales Engineer or Solutions Architect with a cooler name. Here is how practitioners tell them apart.
“The job is not to deploy software and not to sell software. It is to solve the problem.”
Named sources: Nabeel on title inflation, Gergely Orosz on platform write-back, Lenny: FDE vs Solutions Engineer, and Voices from X reading list.
Why title inflation is accelerating
AI labs and startups need people who can ship models into messy customer environments. That demand is real. The shortcut is also real: slap “Forward Deployed” on a GTM engineering title and hope prestige does recruiting work. Former Palantir FDE Nabeel Qureshi has said he gets weekly emails from people standing up an “FDE function” — and that many of those roles are ordinary sales-engineer or solutions-architect jobs being rebranded.
FDE vs solutions engineer (the useful cut)
Lenny Rachitsky’s framing is still the cleanest public 80/20: Palantir-style FDE work is mostly custom software for one large customer, with intent to abstract later. Solutions engineers mostly integrate existing software with small changes. The economics only work on very large contracts — which is why copying the title without copying the deal size and product loop fails.
For a structured comparison on this site, see FDE vs Solutions Engineer.
Four boundary tests
- Outcome ownership. Consulting sells judgment and leaves. Solutions sells a design or POC. Delivery sells a statement of work. FDE sells a result inside the customer’s production system — if it fails there, it is on you (Hobson’s boundary).
- Product write-back. Gergely Orosz argues you cannot really be “forward deployed” from outside the platform. If the role never feeds patterns back into the product — only token spend or account-specific glue — call it something else.
- Team home. Mati Staniszewski (ElevenLabs, former Palantir Deployment Strategist) puts FDEs on the product team, not GTM. Domain expertise can stay with the customer; reusable product experience must come home.
- Fit for the company stage. First Round’s panel notes a tell that the model is a bad fit: you already know exactly how customers should use the product. FDE thrives when field discovery still shapes the roadmap.
Quick contrast table
| Signal | Real FDE | Renamed SE / services |
|---|---|---|
| Org home | Product / engineering | Sales / GTM / PS only |
| Artifact left behind | Production system + reusable pattern | Demo, POV, config, SOW |
| Success metric | Adoption, reliability, product leverage | Pipeline, token usage, billable hours |
| After customer #5 | Primitives / platform improve | Same custom work by hand |
What to do with this as a candidate
In screens, ask who owns production after go-live, whether you will write code that ships, and how field work changes the product roadmap. Compare titles against our jobs board and company salary hubs — then read the JD for ownership language, not just the word “Forward.”
Frequently asked questions
- What is a real Forward Deployed Engineer role?
- A real FDE embeds with customers to solve production problems, owns outcomes in the customer environment, and writes reusable learning back into the product platform — not just demos or configs.
- How do companies fake the FDE title?
- Common pattern: rename Sales Engineer or Solutions Architect to Forward Deployed Engineer without changing ownership, coding bar, or product write-back. The title markets prestige; the job stays pre-sale adaptation.
- What is a quick test for fake FDE roles?
- Ask whether the person sits on the product/engineering team, ships production systems, and improves the product for the next customer. If the work ends at token usage or a POV deck, it is a different job.
- When should a startup not hire FDEs?
- If leadership already has a crisp vision of exactly how every customer should use the product, classic product + SE motions may fit better. FDE shines when niche uses are discovered in the field and pulled back into the platform.