Forward Deployed Engineer: full-stack developer rebranded?

In a year "Forward Deployed Engineer" went from Palantir's in-house job title to a label on postings from companies that have never set foot at a customer site.

You see it on LinkedIn constantly: explainer posts about what an FDE is, companies opening roles with that exact title, people putting it in their bio. Open roles with this exact title have more than quadrupled in a year, according to marketplace data from Paraform (a source with a direct commercial interest in FDE hiring volume: take it as a trend signal, not a neutral census). The problem starts when you actually read the job descriptions one by one: a great many are simply Full Stack Developer roles behind a more attractive job title.

The tell: a lot of "FDE" postings are fully remote

Try it yourself: search "Forward Deployed Engineer" on Indeed or LinkedIn Jobs and filter for remote. Dozens of results come up. LiveKit is hiring a Forward Deployed Engineer for $170K to $250K, tagged "Remote (US)". Second Front Systems does the same with a "Forward Deployed Platform Engineer" marked Remote, only to then write in the body of the posting that regular travel to the customer is required. The title says "remote," the description says "in the field." Either nobody bothered to align the two, or the title is just a sticker slapped on a role that already existed.

Careful not to overgeneralize: a hybrid role with modest travel isn't automatically a fraud, if it's stated honestly. The specific problem with these postings is the internal mismatch, title versus description, not the travel percentage by itself. That said, a Forward Deployed Engineer exists, by definition, to be deployed forward: when the title says "remote" and the job description says "in the field," that mismatch is the most reliable tell that "forward deployed" is all title, no field.

"Sparkling sales engineers": the phrase that nails it

Whoever coined the role already has a name for this imitation. Shyam Sankar, Palantir's CTO, put it bluntly on an earnings call: "Remember, only Palantir has FDEs. Everyone else has sparkling sales engineers" (Q2 FY2026 transcript, accessed August 10, 2026). He was describing a direct comparison: a major tech customer ran a frontier lab and Palantir head-to-head on the same ticketing automation problem. The lab delivered nothing of value; Palantir built agent swarms for its customers' own customers. "Sparkling sales engineer," decorative rather than substantive, is the precise name for whoever wears the FDE title without paying the cost that makes it real.

It's not an isolated jab. A independent essay on "FDE culture" (a practitioner's personal opinion, not an institutional source, but useful because it reaches the same conclusion without being Palantir) lands on the same phrase for the same phenomenon: slapping the FDE label on an ordinary sales team is a case of cargo cult, copying the form without the substance. Real FDE culture, per that essay, is a "radical deference to teams in the field": field teams can invent solutions that look very different from the standard platform, as long as they solve the customer's problem. It has a price: senior engineers, generous budgets, tolerance for a fair amount of organizational chaos. Whoever won't pay it, but still wants the title, ends up producing exactly the "sparkling sales engineering" Sankar was talking about.

What is a Forward Deployed Engineer, really?

The term comes from Palantir, which has used it since 2011 to describe engineers (internally nicknamed "Deltas") who write production code while sitting physically next to the people who'll use it: analysts, operators, the customer's own team. They don't design in a vacuum and hand off a finished product; they watch how that person actually works and build the tool around that reality. Time on site isn't optional flavor text: OpenAI, for instance, requires up to 50% travel to the customer on its own FDE postings (as MarkTechPost also notes). That's not folklore, it's the job spec.

The job covers the full lifecycle, not just writing code: understanding the customer's problem from the inside, designing the solution with the people who'll use it, building it, deploying it to production, then improving it against real usage. Drop any one of these steps, typically the on-site one, and what's left is a good product engineer, not a Forward Deployed Engineer.

It isn't, though, one fixed archetype identical everywhere. Palantir's Delta, the OpenAI/Anthropic version, and, more recently, AWS's (see below) are variations on the same principle, not photocopies. How much travel, how embedded in the product, how long the customer engagement runs: all of that varies. The principle (understand-design-build-deploy-improve, in the field) stays the same; the execution doesn't. It's the same rebrand-or-not-a-rebrand question that shows up in the SEO vs GEO debate: a new name doesn't change the substance underneath.

Why is the FDE title exploding now?

Ten years ago "Data Scientist" was the title every company wanted on the door, even when the person inside was really a SQL analyst with a Python notebook. The same script is playing out with FDE today. OpenAI and Anthropic legitimately created the role to get their models deployed inside large enterprises, and that's a real job. But once a title catches hype, every company wants it on the org chart, regardless of what the person under it actually does. The result: "Forward Deployed Engineer" is becoming the new wrapper for an old job, the full-stack developer who can also talk to a customer. That's not a knock on the original role, Palantir built something specific. It's a knock on whoever photocopies the title without the substance.

a16z offers a useful test for telling authentic titles from inflated ones: does it describe work that would have been unrecognizable five years ago? Run "Forward Deployed Engineer" through it: strip out the physical customer contact, and what's left that a full-stack developer from ten years ago wouldn't recognize? Often, nothing.

The test applies to whoever adopts the title today by copying it, not retroactively to the original coinage, a distinction worth keeping separate. Palantir's 2011 Delta already passed its own version of this test fifteen years ago, and a recognizable trade grew out of it. The problem isn't that the title is old, it's whoever photocopies it now without carrying over the substance that made it unrecognizable the first time.

Does Amazon have an FDE program too?

On July 6, 2026, The Motley Fool reported AWS is investing $1 billion to expand its own use of Forward Deployed Engineers, to accelerate enterprise adoption of its AI cloud platform. This isn't an isolated Palantir/OpenAI/Anthropic experiment anymore: once the world's third-largest cloud provider puts a billion dollars behind it, the title is mainstream by definition.

Not everyone is convinced the model scales, though. Anaplan CEO Charlie Gottdiener, interviewed by Forbes on July 10, 2026, calls it "a good selling model, a good initial deployment model. Not a great model for running the software. Not at all."

Kinaxis's Manik Sharma, a Palantir alum, adds a sharper execution critique: putting "25-year-old engineers" directly with the customer becomes a problem when they don't understand basic domain concepts, like supply-chain constraints or the bullwhip effect, small demand shifts amplified into big swings upstream.

The same Forbes piece notes Palantir's commercial revenue is now 46% of its total (roughly $2.1 billion): the model clearly works for selling. Whether it scales for running things is the open question.

What to actually check in an "FDE" posting

If you're evaluating a role with this title, skip the label and read three things: how much time it actually requires on site with the customer (not "flexible," a real percentage), whether the pay reflects real seniority (Palantir Forward Deployed Engineers on Levels.fyi range from $171K to over $295K in total compensation, with an average base around $155K on Glassdoor), and whether the rest of the posting talks about co-designing with users or only lists a tech stack. If the on-the-ground piece is missing, it's not an FDE, it's the same job as always, just a cooler line for the profile. That principle, more than the title, is also why most pilot projects never make it to production: without someone staying on the ground until the end, the "forward deployed" part of the title never actually happens.

There's also a question of scale, before the question of title. 7% of OpenAI's open roles fall into forward-deployment categories, per an analysis by SaaStr, and 69% of venture-backed startups already have a dedicated AI team, versus a minority of small and mid-sized businesses (HubSpot data, via SaaStr). The same piece estimates real FDE engagement costs between $25K upfront and $60K+ per year, with one to two months of embedded support: figures built for an enterprise, not for an Italian SME. For an SME the right question isn't "do I need a full-time FDE," it's what scaled-down version of the same function it actually needs: someone physically inside the process until it works, not just for a demo.

Put the two numbers together and the math gets interesting: if a senior FDE costs $171K-$295K a year in salary, but SaaStr pegs a full embedded engagement at $25K-$60K, one engineer clearly cannot spend a whole year with a single customer at that price. The economics only work if one FDE serves several accounts at once, or if the "embedded support" a customer pays for is a much smaller slice of that engineer's time than the job title implies. Worth asking, on either side of the table, before signing an FDE engagement.

In short

Forward Deployed Engineer isn't a buzzword by itself: it's a specific role, born at Palantir, now replicated (well) by OpenAI, Anthropic and others. It becomes a buzzword when the title stays but the substance, being physically with the customer, disappears. If you read "fully remote" under "Forward Deployed Engineer," you've found the mismatch. It's also how I scope my own engagements: on-site time stated as a percentage, the same thing I ask job posts to do.