What is a Forward-Deployed Engineer?

Definition

A Forward-Deployed Engineer (FDE) is a software engineer who works directly inside a customer's environment to deploy, integrate, and customize a company's product. Unlike traditional software engineers who build for an internal roadmap, FDEs operate embedded with customers — writing code, owning integrations, and solving production problems in real customer infrastructure.

The role was popularized by Palantir, which built much of its early growth model around sending engineers to live inside government and enterprise clients. As AI products moved from demos to mission-critical production systems, demand for FDEs has spread rapidly across the industry.

What does a Forward-Deployed Engineer do?

Day-to-day FDE work spans three areas:

• Integration engineering — building connectors, APIs, and pipelines that plug the product into the customer's existing systems (data warehouses, identity providers, internal tools).
• Custom development — writing bespoke workflows, dashboards, or automation on top of the core platform to match the customer's specific use case.
• Production ownership — debugging live incidents in the customer's environment, triaging support escalations, and owning reliability for that deployment.

A typical week includes: a scoping call to understand a new integration requirement, writing a data pipeline for one customer, debugging a production issue for another, and filing product feedback with engineering based on field observations.

FDE vs. Solutions Engineer vs. Sales Engineer

The roles are often confused. The clearest distinction is before vs. after the signature:

• Sales Engineer / Solutions Engineer — pre-sale. Runs demos, answers RFPs, helps close the deal. Mostly configures and presents; rarely ships production code.
• Forward-Deployed Engineer — post-sale. Writes and maintains real software deployed inside the customer's environment. Owns the deployment from first integration through stable production use.

There is overlap in communication skills (both talk to customers daily), but the core output is different: a running production integration vs. a signed contract.

Skills and background

Most FDE job descriptions require:

• Strong software engineering fundamentals (Python, Java, Go, or TypeScript are most common)
• Practical experience with APIs, data pipelines, and cloud infrastructure
• Customer-facing communication — translating technical trade-offs for non-technical stakeholders
• Comfort with ambiguity and context-switching across multiple customers

AI-era FDE roles increasingly add: LLM API integration, embedding pipelines, RAG architectures, and model deployment patterns.

Which companies hire FDEs?

Palantir built the playbook; AI companies adopted it fast. As of mid-2026, 373 companies have open FDE postings tracked by latchhire. The highest current headcount belongs to:

1. Databricks (76 open roles)
2. Palantir (63 open roles)
3. OpenAI (33 open roles)
4. Truelogic (29 open roles)
5. HappyRobot (19 open roles)

See the full FDE job board for all 912 open roles.

Compensation

In the US, mid-to-senior FDE roles typically fall in the range of $165,000–$215,000 in base salary, with a median of $200,000 based on 365 roles with published salary data (43% coverage). Equity adds significantly at earlier-stage companies. See the FDE salary page for full data.

Why FDE demand is growing

Three structural forces drive the surge in FDE hiring:

1. AI products need deployment, not just access. A SaaS login worked out of the box. An LLM-powered product needs to connect to internal data, respect compliance boundaries, and be tuned to the customer's workflows — that's engineering work done on-site.
2. Enterprise deals are getting larger. As deal sizes grow, the cost of a failed deployment grows too. Companies invest in FDEs to protect NRR (net revenue retention).
3. The feedback loop is a moat. FDEs surface what customers actually need, which feeds the product roadmap. Companies that deploy FDEs early build more relevant products faster.