Forward-deployed engineer (FDE) is a role pattern that originated at Palantir and has spread across enterprise AI and infrastructure companies - Anthropic, OpenAI, Databricks, Scale AI, and most large-deal AI startups now hire under this title. The role sits between engineering and the customer: an FDE works embedded with a single enterprise account, builds custom integrations and workflows on top of the company's product, and is measured by how much value that customer extracts from the platform.
What an FDE actually does
The defining feature of the role is that an FDE is embedded with a customer for weeks or months, not a meeting at a time. That embedding looks different at different companies but usually involves three layers of work.
The first is technical implementation: writing code that connects the company's product to the customer's systems, building custom UI on top of the platform, designing data pipelines that ingest the customer's data into the company's tooling. This is engineering work, not configuration work - most FDE roles include real Python, TypeScript, and SQL development.
The second is product feedback. FDEs are typically the first people inside a company who see how customers actually use the product. They translate customer pain into specifications, file detailed bug reports, and often ship the first version of features that later become product before the core engineering team productionises them.
The third is account growth. An FDE who builds something the customer values increases the contract value of the account at renewal. That is one reason the role has spread so quickly - it produces measurable revenue impact in a way that pure engineering roles do not.
How FDE differs from solutions engineering
Solutions engineers are typically pre-sales: they help close deals by demonstrating the product against a customer's requirements. Forward-deployed engineers are post-sales: they make sure the deal that closed actually delivers value. The two roles overlap in skill set - both involve writing code in front of customers - but the operating cadence and incentive structure are different.
Solutions engineers measure their work in deals closed and POCs converted. Forward-deployed engineers measure their work in customer outcomes, usage, and contract growth. Companies often have both roles, with FDEs picking up where SEs leave off after the sale.
The employer landscape
Enterprise AI companies are the largest single hiring vertical for FDE roles in 2025–26. Anthropic, OpenAI, Cohere, and Mistral all hire forward-deployed engineers to support their largest enterprise contracts - typically deals in the seven-to-eight-figure range where the customer needs custom integration and workflow tooling. Compensation tends to be at or above standard senior-engineer levels, with travel expectations that vary widely by employer.
Data and analytics platforms - Databricks, Snowflake, Confluent - hire FDEs to support strategic accounts. The work skews toward data-pipeline implementation and custom analytics rather than ML application.
Defence and government-adjacent companies - Palantir, Anduril, Scale - pioneered the role and continue to define its most demanding form, with both clearance and travel requirements that limit who can apply.
Series B+ infrastructure startups increasingly hire FDEs as their first non-engineering customer-facing technical hires, replacing the model of dedicating engineering time to single customers.
Skills that distinguish strong FDEs
Strong FDEs combine three things that are independently uncommon and rarely combined. They write production-quality code in at least one language the customer's stack uses (Python and TypeScript cover most cases). They communicate technical decisions clearly to both engineers and non-engineers, including in writing. And they have the temperament for ambiguity - most FDE engagements begin with a customer goal that the FDE has to translate into a concrete technical plan.
The skill that is often missing in candidates pivoting into FDE roles is the temperament. The role is part engineer, part consultant, part diplomat. Engineers who need a tightly-scoped backlog rarely thrive; engineers who enjoy walking into ambiguity and producing structure usually do.
Remote work and the FDE role
The FDE role is often described as remote - and it largely is - but with a substantial caveat. Most FDE positions involve travel to customer sites, sometimes 30–50% of the time, particularly in the first months of an engagement. The remote component is everything-other-than-customer-on-site: planning, code review, internal collaboration, async product feedback. If you are evaluating a remote FDE role, the travel expectation is the single most important question to ask.
Some FDE roles are fully remote with no travel - typically because the customer prefers async collaboration or because the company explicitly designed the role around it. These are increasingly common at AI-native companies whose customers are themselves remote-first.
Compensation
FDE compensation usually tracks senior-engineer compensation at the same company, sometimes with a customer-success-style bonus or commission tied to account expansion. Cash compensation in 2025–26 typically falls in the $180k–$280k range for US-based roles at well-funded AI and infrastructure companies, with equity grants comparable to senior-engineer offers.
Compensation can be higher at companies where FDEs are explicitly tied to revenue - Palantir-style commission structures can push total compensation into the $400k+ range for top performers. Compensation tends to be lower at companies where the role is treated as a customer-success function with engineering work attached.
Red flags and green flags
A red flag in an FDE job description: "minimal travel required" paired with a list of enterprise accounts that are headquartered in different cities. The travel expectation is almost always higher than disclosed, and under-disclosure at the description stage predicts under-disclosure on offer day.
A green flag: the job description names the specific product area the FDE will support, lists the programming languages the customer's stack uses, and mentions a named customer success counterpart the FDE will work alongside. That level of specificity signals the company has done this before and understands what the role actually involves.
Other green flags: the role reports into engineering rather than customer success (signals technical seniority is taken seriously); the company publishes engineering blog posts from FDEs (signals the work is valued internally); the offer package includes an explicit travel budget and a clear policy on home-office days.
Frequently asked questions
What is the difference between a forward-deployed engineer and a solutions engineer?
Solutions engineers operate pre-sale; their job is to help close deals. Forward-deployed engineers operate post-sale, embedded with a customer for weeks or months, and their job is to make the customer succeed with the product. Compensation, incentive structure, and time horizon are all different.
Do FDE roles require travel?
Most do, in the 20–50% range. Some are fully remote. The travel expectation is the most important question to ask when evaluating a role and is often under-disclosed in job descriptions.
Is FDE a path into product management or engineering management?
It can be either. FDEs see how products are used in the wild, which is excellent preparation for product management. They also work at the boundary between engineering and customer needs, which sets up well for engineering management roles where customer judgement matters. The path is less common than the engineering→PM or engineering→EM paths but is well-trodden at companies like Palantir.
What programming languages should an FDE know?
The right answer depends on the customer's stack, but Python and TypeScript cover the majority of cases. SQL is essential. Most FDE roles also benefit from comfort with at least one cloud platform's primitives - typically AWS, GCP, or Azure depending on the employer's customer base.
How do FDE compensation packages compare to standard senior-engineer roles?
At most companies they track senior-engineer compensation closely, sometimes with a small commission or bonus component tied to account expansion. At companies where FDEs are explicitly revenue-attached, total compensation can exceed standard engineering roles substantially.
Related resources
- Remote solutions engineer jobs - the pre-sales counterpart
- Remote sales engineer jobs - adjacent role with stronger commercial focus
- Remote applied ML engineer jobs - common FDE specialisation in AI companies
- Remote technical account manager jobs - non-coding peer role
- Remote founding engineer jobs - adjacent high-ambiguity engineering role