Who are Palantir FDEs?
Palantir Learn does not seem to have a dedicated track for becoming an FDE. Does this mean that FDE is not really something you can learn externally, and that you almost have to “be born” into the role inside Palantir? 
Or is “FDE” more of a Palantir-specific brand name for solution engineers, implementation engineers, or forward-deployed technical consultants who work directly for Palantir with clients?
This post just hit the 200-view milestone with no answers yet.
Does that mean “FDE” is a real Palantir role, but hard to explain from the outside? Or should I start treating it as an effective marketing myth? 
Still genuinely curious: is FDE a learnable discipline, a Palantir-specific internal role, or simply a branded version of solution engineering / implementation consulting?
Hey @Denis!
An FDE is a Forward Deployed Engineer, it’s a hybrid of software engineer and consultant who works directly with clients. The role has been popularized by Palantir but also exists in other companies. I don’t work at Palantir, but for me, an FDE is more a way of working.
So, to answer your questions:
So for me, it’s all three at once: a real role at Palantir, a learnable skill, and a branded version of solution engineering.
I hope you find this helpful. Feel free to ask if you have any question.
Nathan 
As a Palantirian and FDE of 14 years, I actually have a very different view than what’s framed out there in the market. Being an FDE not a last-mile “sales engineering” role, or some other convenient and thin relabeling of existing enterprise software roles. In fact it’s not even primarily about the noun (“Forward Deployed Engineer”).
It’s about the verb: Forward Deployed Engineering. This is the way we’ve built our platforms at Palantir since the earliest days of Gotham. Working deeply with our customers in the field; signing up for the outcome, and not simply delivering preexisting technical components or services; and metabolizing the learnings continuously into core platforms. It is an iterative, often “kaizen” process that encompasses the whole organization. The core product engineers are part of forward deployed engineering; the field teams are part of forward deployed engineering; and our internal operations teams are all oriented around supporting this function.
It’s building software (or any product) through the human (and increasingly human+agent) equivalent of back-propagation. You keep indexing reality; chewing the pain of what works and doesn’t; and wrestling the lessons into product primitives. Often what’s produced isn’t optimal the first time, and there are often competing visions at the edge that need to be reconciled continuously. Hence, it’s a whole-of-organization approach to product development. Forward deployed engineers are simply those at the tip of the spear, in the grander orchestration.
To me, the most exciting FDE teams I see are those at our customers, being stood up internally by our customers themselves (often to augment and amplify Palantir’s presence). This is because they are blending the outcome orientation, engineering skill, and access to operational and business stakeholders needed to make the FDE process actuate. i.e., they’re choosing to pursue FDE as a product development approach.
It’s puzzling to see many simply rebranding sales engineers or consultants as FDEs. I agree those roles have a place…but again, FDEing was never about last-mile delivery or simply servicing revenue. It’s always been an approach to building deep and rapidly-changing platforms, which must be accountable to operational requirements (rather than analytical ones or others that are more “fixed” in schema).
We’d love to see more FDEing out there in the world, in the true sense! Resist the thin cargo culting…
I did an interview last year which opines on this a bit more: https://youtu.be/3c0iaLanhyk
Interesting. I had always assumed that the term “forward-deployed engineer” came directly from the military idea of forward-deployed personnel.
Since Palantir worked closely with the military, I imagined that some engineers were literally placed closer to the operational environment, or even closer to the theater, and were therefore called forward-deployed engineers. In that context, the term sounded both distinctive and very close to reality.
Later, as Palantir expanded into civilian and commercial markets, the same title was applied much more broadly. At that point, it started to feel less like a precise description of the role and more like part of Palantir’s commercial mythology: a way to make consulting, implementation, and customer-facing engineering sound more unusual, mission-driven, and exciting.
What is especially interesting I see today, large and serious companies have also picked up this FDE idea or
In practice, it often seems to be simply a rebranding of the client-facing consultant or/and on-client solution-engineer role.
That is at least how I see the term today.
