Palantir's engineers have a shorthand for the difference between their two biggest engineering roles. A software engineer's focus is "one capability, many customers." A forward deployed engineer's focus is "one customer, many capabilities" (Palantir blog). Internally, Palantir calls them Devs and Deltas. The role spent years as a Palantir oddity. In 2025, AI companies made it one of the most talked-about jobs in tech. An a16z essay called it "the hottest job in startups" (a16z). If you sell complex AI software to enterprises, you're probably about to hire one.
Key Takeaways
- Forward deployed engineers (FDEs) write real code inside a customer's environment to make your product deliver results there.
- Hire for engineering depth, customer judgment, and autonomy. Weakness in any one of them sinks the role.
- The role is different from a solutions engineer or consultant. FDEs ship production code.
- Demand spiked in 2025, so expect competition. Screen carefully and look beyond the usual hubs.
What the Role Is
Palantir's post describes Deltas as engineers who "deploy our software platforms to customers" with a mandate "to achieve technical outcomes for our customers," measuring success "in terms of impact on the customer's goal." It pushes back on the idea that the role is consulting: "A Delta does significantly more engineering and technical work than a consultant." The name, it explains, goes back to early business development teams named after letters in the NATO alphabet.
In an AI company, that looks like this: an FDE sits with a customer's team, connects your product to their data and systems, writes the integrations and custom workflows the product doesn't cover yet, and feeds what they learn back to your product team. The a16z essay framed this as trading some margin for a moat, since deep deployments are hard for competitors to displace.
The demand is real, though the numbers need care. eWeek, citing Financial Times reporting on Indeed data, said FDE job postings rose more than 800% between January and September 2025 (eWeek). Treat the exact figure as secondhand. The direction isn't in doubt.
The Three Things to Screen For
Palantir's post lists the traits it looks for: technical decomposition, "autonomy and strong technical intuition," thoughtfulness, and "high user empathy, an ability and desire to understand business strategy." That maps to three screens.
Engineering depth. FDEs write production code in messy environments: legacy databases, strange auth setups, rate-limited APIs. Give them a realistic integration task with a flawed spec and see what they build and what they question.
Customer judgment. They'll spend their days with customer stakeholders. Run a role-play where a customer asks for a custom feature that would break your product's model. A strong FDE finds the real need and a way to meet it without forking the product.
Autonomy. Nobody is looking over their shoulder at a customer site. Ask for a story where they owned an ambiguous problem end to end.
| Candidate type | Strength | Risk as FDE |
|---|---|---|
| Backend engineer, no customer exposure | Solid code | Struggles with ambiguity and stakeholders |
| Solutions engineer | Customer skills | Code may not survive production |
| Consultant | Business framing | Writes decks when code is needed |
| Ex-founder or early engineer | Autonomy, breadth | May resist following the product roadmap |
The best FDE candidates often come from the last row, or from engineers who have worked at small startups where they talked to customers every week. How to hire a product engineer covers a close cousin of this profile.
A Concrete Version
A Series B company sells an AI document-processing product to insurers. Its third enterprise customer has claims data spread across an old policy system and a document store with inconsistent file names. The pilot is stalling.
The company assigns an FDE for eight weeks. Week one: map the customer's data sources with their IT team and find the three document types that make up most of the volume. Weeks two to four: write a connector to the policy system and a normalization step for the file names. Weeks five to eight: build an evaluation set with the customer's claims adjusters, tune extraction on it, and report accuracy weekly.
The pilot converts. Just as important, the FDE writes up the connector pattern, and the product team turns it into a standard feature, so the next insurer takes three weeks instead of eight. That feedback loop is why the role exists.
The Honest Counterpoint
FDEs are expensive to run. They create custom work that can pile up into a services business that only looks like a software business on paper. If every deployment needs an FDE forever, your product may not be ready for the customers you're selling to. Track how much FDE work turns into product features, and push hard on that number.
Also consider whether you need this role or a strong solutions architect plus a good integration team. For simpler products with standard integrations, the FDE model is overkill. And travel expectations matter: be clear about how much time the role spends on-site, since that affects who will apply.
Frequently Asked Questions
What's the difference between a forward deployed engineer and a solutions engineer?
Solutions engineers mostly support the sale with demos and technical answers. FDEs work after (and often during) the sale, writing production code in the customer's environment.
Can FDEs work remotely?
Many customer deployments can be done largely remotely, with on-site visits at key moments. Time-zone overlap with the customer matters a lot. See why time zone overlap matters.
What background makes a good FDE?
Strong software engineers who have talked to customers regularly: early startup engineers, former founders, and product engineers. Pure consultants and pure backend specialists both tend to struggle.
The Bottom Line
Hire FDEs who can ship production code, handle customer ambiguity, and work alone, and make sure their lessons flow back into your product. With demand this high, a tight screen matters more than a big funnel. For senior engineers with that mix, see available engineers or get a quote for your role.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
