What are Forward Deployed Engineers, and why are they so in demand? (2025)

g8oz

This term is so eye rolling. Unless the FDE has legitimized pull within the core product team they are nothing more than a glorified field engineer/technical consultant.

protocolture

We have sales engineers at home.

adamgordonbell

My understanding is Palantir used the term, and calling teams of them "Delta Force" to make a consultative-and-service-heavy software adoption cycle make sense to US Military clients.

LowLevelKernel

Is it similar to Facebook’s Production Engineer role or Google’s SRE role?

fde_my_butt

>FDEs are sometimes mistakenly thought of as consultants, but the difference between consultants and FDEs is that the former make one-off recommendations, whereas FDEs generally work with customers, long-term. ...sounds like a consultant to me! Also, even if "long-term" was an important distinction, the term FDE itself became popular a very short time ago !!! https://trends.google.com/trends/explore?date=all&geo=US&q=f... so how can you assert FDEs work with customers for the long-term

padolsey

TL;DR: Glorified contract role for integrating your employer's APIs with enterprise customers. Like working with mckinsey vibe PMs and being sold on fat margins you'll see none of? Perfect!

paxys

I remember interviewing at Palantir back when they were making this role popular (probably a decade ago). I wanted to be an SDE and the recruiter kept pushing me towards this “forward deployed engineer” role. After hearing the pitch I went…oh so you want me to be a sales consultant? They did not take this well, I guess because Palantir was trying very hard to convince the world they were a tech unicorn and not a glorified consulting firm.

poemxo

I'm swimming against the current with this, but I think the role is really cool. Blessed by your own company to wear the vestments of an expert, and expected by the customer to deliver the sort of advice that will get a team "unstuck", a forward deployed engineer is in the perfect spot to prove just how much of a hotshot he or she is. Especially in fields like defense where the customer is staffed with teams that are highly risk averse. It's one of the few careers I get a bit jealous of, even though the burnout rate is probably pretty high.

andy99

I’ve done some of what I think this is, working on prem with customers, and I find it funny when I see jobs for FDEs that are somehow all in-office in San Francisco. The whole idea of being forward deployed I take to mean actually deployed.

lahfir

to put it in simple terms, these are people who are so good at both usage/integration of the entire product and can help the company's clients to integrate the product seamlessly into their stack. We've seen this in rise, especially OpenAI engineers having office hours inside Nvidia's campus, etc.

naturalmovement

Interesting choice of name for a website which contains no actual engineering.

_pdp_

Every company I have seen implements more or less the exact same stack, with a few small variations. The problem is that it is often not very good and is usually months, if not years, behind. I have already seen this in several places, including a few F250 companies. Frankly, it is a waste of time. It is expensive to build, expensive to maintain going forward, and often already dated by the time it is finished because things have moved on. Also, as much as I like code, and would personally prefer to build things in code, a lot of internal innovation happens because end users have access to agentic tools. Yet, from the outset, both OpenAI and Anthropic FDE approaches seem heavily code-driven. I might be mistaken. In my opinion, it is much better to deploy a more customisable harness that sits across the different technology stacks that is also user-friendly. But then I am biased, because that is what we do, so take this comment as you will.

slowin

These used to be called "Sales Engineers" but Palantir wanted something more militant sounding. It's a shame others picked this gross term up and started using it.

oooyay

Palantir is also the kind of business where every engagement is somewhat to totally bespoke. That's a big departure from a more typical SaaS model where you focus on providing a platform that your customers build on top of with a more generic set of tools. I am curious whether this FDE direction will result in more product and platform complexity that is more difficult to unwind.

edoceo

Back in the lat 90s we called ourselves a "Strike Team".

kyuuurius

As building becomes more and more easier, the value of pure swe goes down. I feel the only way to thrive in this environment is either a specialized engineer or a fde.

vanuatu

the main distinction i like to make is: your FDEs shape your product strategy, and should be considered R&D. after making sure a customer deployment is successful (by any means necessary btw, even if it means building new systems outside of the product), the crucial next step is to drive the product improvement with PMs and core software engineers after contact with reality. this was a pretty radical idea from palantir in the era of saas if you only do step 1 you're basically just solutions engineers / mckinsey, and if you only do step 2 with no customer learning to your product you don't improve your platform for all the other customers. the pain becomes the moat There's a reason why this echelon of companies comp FDEs much, much more than services businesses is because you're trying to find engineering + product + customer facing in one (knew people making 200k+ 5 years ago as new grad FDEs, and the same flavour at the labs is 500k+ easy) that being said the role has evolved a lot over the years, and depending on the company it could be indistinguishable from solutions eng, or sales eng, or even dev rel.

ajb

In the semiconductor industry this role is called Field Application Engineer. They do serious work, not just slideware, as your chip probably ships with drivers that were designed months or years before you could get significant time from the customers engineers (which generally only happens after you manufacture, but you need software to prove it works well before that). So these guys are the ones who adapt it, and their feedback is valuable as they are the ones who build understanding of the customer. However, at my old employer they didn't get commit rights to the main software repos. They had to carry around a bunch of patches which were gradually cleaned up and integrated. As I didn't directly work with them, I don't know if this says more about them or the guys managing the internal development. It's a role that fits a different personality to that typical among software engineers. If you're bored as a dev it may suit. Pointless to try to shoehorn people into the role that don't suit it though.

RajT88

Used to be called Sales Engineers. Also Customer Engineers. Also Field Engineers. Also: Solutions Architect. Same shit. Different day. The wheel begins a new turning.