What a forward-deployed engineer does, what they earn ($140K–1.2M), and how three structurally different FDE types operate in 2026. Tier-by-tier compensation and a vetting checklist.
A forward-deployed engineer (FDE) is a software engineer who embeds directly inside a customer organization to scope, build, and ship production code tailored to that customer's specific environment. Unlike a solutions architect who designs and hands off a document, the FDE owns running software.
FDE job postings on Indeed jumped 729% year-over-year (from 643 to 5,330, April 2025 to April 2026), driven by one problem: LLM products need custom integration that neither documentation nor traditional consulting can deliver.
This guide covers what the role means, how three structurally different FDE types (AI lab, enterprise SaaS, and defense) operate, and what the 2026 skill stack requires. It also maps tier-by-tier compensation and shows how to spot a real FDE role from a sales-engineer rebrand before you accept the offer.
A forward-deployed engineer is a software engineer who sits at the customer site and fills the gap between what a product does and what the customer needs. Bob McGrew, former Chief Research Officer at OpenAI and early engineering executive at Palantir, describes the function directly. In his words:
A forward deployed engineer is someone (typically technical, an engineer) who sits at the customer site and fills the gap between what the product does and what the customer needs.
The critical differentiator is ownership of running code. An FDE writes and ships production software in the customer's environment; a solutions architect designs and hands off a document. Paraform's breakdown puts it plainly:
FDEs build; SEs guide. This isn't a values judgment, it's a skills and incentive question. SEs are optimized for breadth and presentation. FDEs are optimized for depth and execution.
Palantir invented the role in the mid-2000s for CIA and NSA clients, describing its scope as startup-CTO-level. Per Palantir: "FDE responsibilities look similar to those of a startup CTO: you'll work in small teams and own end-to-end execution of high-stakes projects." The internal name at Palantir was "Delta"; core SWEs were "Dev."
By 2014, Palantir was running more than 100 FDEs across government and commercial accounts. Until 2016, Palantir had more FDEs than traditional software engineers.
The driver is structural, not cyclical. LLM and agent products can theoretically do anything imaginable. The product is no longer the bottleneck.
Getting that product to work inside a specific customer's data environment, security policies, and existing workflows is. Jake Stauch, CEO of Serval, describes the dynamic:
Software platforms have become so powerful that their capabilities are no longer the rate-limiting step for the customer. AI unlocked all of these long-tail capabilities. But somebody has to steer the product to do it in that way.
The numbers reflect it. The institutional confirmation: OpenAI formalized a $10B Deployment Company joint venture in May 2026, with 19 institutional investors and a 17.5% guaranteed annual return target.
Anthropic followed with a $1.5B joint venture backed by Blackstone, Goldman Sachs, and others. EY launched FDE roles in April 2026, signaling the model has crossed from AI startups into professional services.
A four-stage loop maps consistently across practitioner accounts, McGrew's Y Combinator talk, and Jarvis's Altimeter interview.
You arrive at a vague problem statement: "we need to cut fraud," "we want AI in our factory." Your first deliverable is not code: it's a problem statement with measurable acceptance criteria.
Jason Liu (@jxnlco), who did FDE work at Action IQ before ML engineering at Stitchfix and Meta, describes the diagnostic pattern in a thread with 901 likes:
Engineers aren't really being quantitative with how they're describing problems. They're using words like…
The reframe from adjective to metric is the FDE's first output. Liu's example: changing a single response schema field name from final_choice to final_answer improved model accuracy from 4.5% to 95%. Precision in problem specification produces outsized results.
Move fast and build a proof-of-concept. The goal is showing what's possible and collecting fast feedback, not shipping hardened code.
Speed matters more than elegance. Customer trust is the real output of this stage.
Harden the PoC to production-grade: scalable, secure, compliant with the customer's infrastructure constraints. You navigate internal security reviews, legacy system integration, and data pipeline quirks that no external engineer would encounter. Colin Jarvis, Head of FDE at OpenAI, describes the Morgan Stanley embedding:
We first of all did a bunch of retrieval tuning to get to the point where we could trust the outputs of the research reports, and then we ran a bunch of pilots getting the wealth advisers to label data, and eventually got them to the point where they trusted the insights and started actually using them.
The last stage is what separates FDE from consulting. You take customer insights back to the core product and research teams and help build better generalizable products. McGrew's gravel-road metaphor captures the loop:
The FD goes and builds like a gravel road to where the product needs to go. And then the role of my team was to look at that and basically figure out how that should generalize to the next five customers or the next ten customers, and then turn that gravel road into like a paved superhighway.
Time allocation in practice: the State of FDE 2026 survey (1,500 respondents) reports 47% customer-facing work, 31% coding, and 22% internal coordination.
The single largest source of practitioner confusion is that "FDE" means structurally different things at different company types. No SERP top-10 guide currently maps this for candidates evaluating offers.
What you're signing up for at OpenAI bears almost no resemblance to what you're signing up for at Anduril. Understanding the tier determines which skills to develop, which compensation expectations apply, and what day-to-day work looks like.
At OpenAI, Anthropic, Scale AI, and Cohere, the FDE writes and ships production code in enterprise environments, specializes in LLM integration, RAG pipeline setup and tuning, and custom agent orchestration. Per SVPG's framing, the primary output is product intelligence. Your discoveries shape what the core product becomes.
Compensation from the Perspective AI 2026 report (n=1,200 FDEs): mid-level ~$385K total comp; senior/staff $485K–$785K; principal $1.2M+. Equity now represents 55–70% of total comp, up from 35–45% in 2024. Engagement cadence runs 2–6 week sprint cycles, remote or hybrid.
Evals and agent observability are non-negotiable here. Jarvis cites a MIT-attributed statistic that 95% of enterprise AI deployments fail.
The FDE's job is to make the 5% succeed. You prove to the customer's security team that the agent is safe.
Salesforce, Ramp, Databricks, Snowflake, and most Series A+ AI startups define the enterprise SaaS tier. The FDE builds customer-specific integrations, configuration layers, dashboards, and migration scripts on top of a platform product, focused on making it work in the customer's specific environment: legacy data formats, security requirements, existing workflows.
Compensation from FDE Pulse 2026 (265 active postings with disclosed salary): FDE Pulse reports a mid-level base midpoint of $187K; senior/staff $231K; manager/lead $250K+. Overall base midpoint: $199K (FDE Pulse). 76% of postings include equity; 78% disclose pay.
The Ramp model (roughly 15 FDEs in pods with four core operating principles) illustrates the enterprise SaaS structure. The product is well-defined; the FDE accelerates customer-specific deployment rather than pioneering new capability.
Defense and government FDE roles are structurally different from the two tiers above. Palantir and Anduril FDEs physically deploy to customer facilities, sometimes classified and sometimes in conflict-adjacent regions. The role requires US security clearance (Top Secret for Anduril's roles) and involves engineering in constrained, sometimes air-gapped environments.
Anduril's FDE role data: $113K–$155K base plus equity, up to 75% travel including "remote regions of the world" for up to two months, with health requirements per DFARS/DoDI military standards. Deployment durations run 6–18 months at customer facilities.
Palantir built this model from its earliest CIA and NSA contracts. Internal FDE names: "Deltas" (customer-embedded) handled classified deployments at Fort Bragg, Langley, and other facilities for six to twelve months at a time, writing production code with full security clearances.
The confusion between FDE and adjacent roles is real and expensive. Candidates accept what they think is an FDE role and find themselves doing pre-sales or implementation support. The distinction is production code ownership.
Role | Core Activity | Writes Production Code? | Customer Interaction | Builds For |
|---|---|---|---|---|
Build custom production software at customer site | Yes (owns outcome) | Deep, long-term embedded | One specific customer | |
Software Engineer (core) | Build scalable product features for all users | Yes | Rare or none | All users |
Design systems, run demos, pre-sales PoCs | Rarely; hands off spec | Pre-sales, high-level | Sales motion | |
Sales Engineer | Pre-sale demos and technical validation | No | Pre-sale discovery | Closing the deal |
Relationship management, support, renewal | No | Ongoing advisory | Retention | |
Consultant | Advisory, documentation, SOW delivery | Rarely, and not production code | Project-scoped | Document/recommendation |
FDE vs. adjacent engineering and customer-facing roles
The distinction between FDE and TAM is where the most title inflation lives. TAMs rarely write production code; FDEs do. Barry, a former Palantir internal deployment role holder who spent five years in the organization, puts the requirement plainly:
The FDE model only works with a radical deference to teams in the field. They are empowered to do whatever they need to solve a problem, even if it bears only a thin, even begrudging, relationship to the base platform.
Without that autonomy, the model collapses to implementation support regardless of what the title says.
On r/cscareerquestions, practitioners split sharply. u/momo_0 (176 upvotes, August 2025) describes the genuine version:
FDE roles have always been a subset of the Sales + Solutions engineering umbrella. This isn't a new thing. If you have the right hybrid skill set, can be a very fun and lucrative career.
u/wayne099 (68 upvotes, ten years in the role) calls it:
Best of both worlds Sales and SWE. You get to go to sales conferences, travel, talk to customers, no quota plus you get paid like SWE.
In a November 2025 thread on r/cscareerquestions, u/that_young_man (top-voted) posted the skeptic view:
Forward deployed engineer is a sales role with a worse commission structure.
That assessment holds for the ~40% of postings that are pre-sales or solutions engineering rebranded. The assessment is inaccurate for AI-lab FDE roles where the engineer owns production code, sits on-call, and commits directly to the customer's repository.
FDE work demands a T-shaped profile: deep in engineering, wide in enough domains to navigate any customer environment. The gap between a 2024 FDE profile and a 2026 one is this agentic layer. Most SERP incumbents haven't updated to reflect it.
Python is mandatory across every source; no other language appears as consistently in job postings, practitioner accounts, and interview guides. Secondary: TypeScript/JavaScript for full-stack work; Java or Go for enterprise backend environments.
Advanced SQL is non-negotiable: joins, window functions, CTEs, query optimization. You will be writing against customer databases with schemas you've never seen, without a DBA to ask.
Cloud fluency across at least one major provider (AWS most common, then GCP and Azure): compute, storage, networking, IAM. Containers and orchestration: Docker (build, run, push) and Kubernetes (pods, deployments, services). Infrastructure as code at a minimum with Terraform basics.
Data pipelines: ETL/ELT, Spark, Airflow, distributed processing. Enterprise FDE engagements routinely begin with the customer's data in the wrong shape for the AI product. This is where you spend the first two weeks.
RAG pipelines end-to-end: vector database choice (Pinecone, Weaviate, PGVector), retrieval tuning, hybrid search, context management. Jarvis's Morgan Stanley engagement (retrieval tuning on proprietary research reports until outputs could be trusted) is the canonical example of what this means in production.
Agent orchestration: LangChain/LangGraph, CrewAI, LlamaIndex. You need to build, debug, and maintain multi-agent workflows in customer environments where failure modes are novel and observability is your responsibility.
Evals and AI observability (LangSmith, Braintrust, HoneyHive) are the 2026 differentiator. Tracing, monitoring, guardrails, and constraint enforcement are now the deliverable the customer's security and compliance teams require before a production rollout.
The FDE's job is no longer just "get the agent to work in the demo." It is to prove to the customer's security team that the agent is safe, auditable, and compliant with their requirements. FDEs who can't speak this language are being filtered out of AI-lab hiring in 2026.
MLOps basics: model deployment, versioning, and monitoring in production. LLM fine-tuning fundamentals and transformer-architecture intuition are valuable for debugging: you don't need to run training, but you need to understand why a model behaves a certain way at the inference edge.
Albert Lam, a former Palantir deployment lead, names the two uncoachable traits: customer empathy and the ability to execute solutions autonomously. You are the highest-ranking technical person in the room, accountable to a customer who may not know what's technically possible. Simultaneously, you're accountable to a product team without full context on the customer's environment.
McGrew's take on ideal FDE candidates:
They need to be rebels. They need to be someone who understands how things are done right now and recognizes that it's insufficient, that it doesn't work. Because if their perspective is "I come from this world, it's great," then they're never going to be able to figure out the step function change that the new software has to be able to make.
Best backgrounds for breaking in: early-stage startup engineers (already customer-facing, shipping under pressure), hands-on solutions architects who built PoCs rather than diagrams, and data or ML engineers with production deployment experience. Full-stack engineers who ask why before taking tickets also fit well.
Compensation varies more in the FDE market than in almost any other engineering role. A single "average FDE salary" number is misleading.
A defense-tier FDE and a frontier-lab principal FDE occupy entirely different compensation brackets. Below is a unified map from three primary sources.
Tier | Level | Total Comp | Data Source |
|---|---|---|---|
AI Lab (OpenAI, Anthropic, Scale AI) | Mid-level | ~$385K | Perspective AI 2026, n=1,200 |
AI Lab (OpenAI, Anthropic, Scale AI) | Senior / Staff | $485K–$785K | Perspective AI 2026 |
AI Lab (OpenAI, Anthropic, Scale AI) | Principal | $1.2M+ | Perspective AI 2026 |
Palantir FDSE | L3 | ~$155K | Perspective AI 2026, n=423 |
Palantir FDSE | L4 (Mid) | $215K median | Levels.fyi + Glassdoor 2026 |
Palantir FDSE | L5 (Senior) | ~$295K | Levels.fyi + Glassdoor 2026 |
Palantir FDSE | L6 (Staff) | $415K+ | Levels.fyi + Glassdoor 2026 |
Palantir FDSE | L7 (Principal) | $555K+ | Levels.fyi + Glassdoor 2026 |
Enterprise SaaS | Mid-level | $187K base midpoint | FDE Pulse 2026, 265 postings |
Enterprise SaaS | Senior / Staff | $231K base midpoint | FDE Pulse 2026 |
Enterprise SaaS | Manager / Lead | $250K+ base midpoint | FDE Pulse 2026 |
Defense / Government | Mid-level | $113K–$155K base + equity |
FDE compensation by tier, 2026
Three figures that circulate as "average FDE salary" each measure different things: $238K total comp (Hashnode 2026 guide, all levels), $174K (Revealera median of 1,000+ postings, via Bloomberry), and $113K (Glassdoor base-only average, all companies). Don't compare them directly.
The Glassdoor number reflects base salary across every tier including junior implementation roles; the Revealera figure is a posting-median across all seniority levels; the Hashnode figure is total comp. All three are accurate for what they measure.
FDE versus adjacent roles on the same seniority level: Paraform's 2026 data puts FDE average at $238K versus solutions engineer $155K–$210K and customer engineer $130K–$180K.
On r/cscareerquestions, practitioners estimate that roughly 40% of current FDE postings are pre-sales or implementation support roles carrying the FDE title. The estimate is community-sourced, not from a primary study, but it aligns with Barry's insider critique and the SERP data showing "FDE vs solutions engineer" as one of the top related searches. A five-minute JD audit separates the real roles from the noise.
Green flags (genuine FDE role):
Red flags (likely solutions engineering or TAM rebranded):
u/freakingdingus (June 2025, active FDE) describes the genuine version:
Essentially I am a software engineer and solutions engineer in one. I work with clients to figure out their needs and then instead of sending off info to someone else I do the work myself.
That last clause, "I do the work myself," is the key sentence. If the JD doesn't make that claim, ask directly in the interview: "Who owns production deployments: the FDE, the core engineering team, or both?"
The most common mistake is accepting a title without confirming what the role actually requires. Before accepting any offer, ask for a specific example of a production system an FDE recently built or deployed for a customer. Ask who wrote it, who owns the on-call, and who has commit rights to the customer's codebase.
If the interviewer can't answer concretely, the role does not match the FDE model.
FDE practitioners consistently identify skipping quantitative problem framing as the highest-impact mistake. Arriving at a customer site and writing code against the first vague problem statement ("make our data pipeline faster") without defining measurable acceptance criteria produces work that solves the wrong problem. The framework from @jxnlco: before writing a line of code, translate every qualitative descriptor ("slow," "inaccurate") into a metric with a target value.
Ramp's Builders Blog identifies "scoping and generalization" as the art of the role: knowing when to MVP a quick fix versus build a generalizable solution. FDEs who build fully custom systems for every customer produce neither efficient delivery nor useful product feedback. The best deployments produce both a working customer system and a generalized capability the product team can ship to everyone.
The FDE who only tracks whether the deployment succeeded misses the role's most valuable output. The SVPG framing of the role emphasizes discovery: what the FDE learns at the customer site is an asset the core product team cannot generate any other way. Practitioners who treat Stage 4 (feedback) as optional produce good deployments; practitioners who treat it as the primary output produce good products.
Barry's inside critique of the FDE model:
Slapping a title on your field team because it sounds cool is one thing: building a truly "Forward Deployed" culture is another. It doesn't work without complete commitment to the benefits and costs.
Companies that impose rigid product constraints on their FDEs, or that route FDE discoveries through slow product approval cycles, extract the costs of the model without capturing the benefits. The candidate who asks "how quickly do field discoveries reach the product roadmap?" in the interview gets real signal about whether the company has built the model or just borrowed the title.
Practitioners increasingly describe FDE as an accelerated path to company-building rather than a lateral move from core engineering. Three trajectories emerge:
Into product management: Field intelligence from customer deployments is the most direct pipeline to PM roles. FDEs see customer problems before the PM does. The SVPG product-discovery lens explicitly frames FDE experience as upstream discovery work, and companies that recognize this treat FDE alumni as pre-qualified PM candidates.
Into engineering leadership: FDE alumni who return to core engineering carry customer context that is rare in promoted ICs. Palantir describes the FDSE role as training for "startup CTOs." The breadth of scope, autonomy, and customer ownership is unlike any pure product role.
Into founding: @jxnlco's trajectory (FDE at Action IQ, ML engineering at Stitchfix and Meta, then building instructor (open-source LLM output library used by thousands), then AI consulting at $500/hr) illustrates the pattern-library compounding effect. FDE experience produces reusable frameworks across customers; eventually those frameworks become products or intellectual property. On r/cscareerquestions, practitioners describe this as the role's highest-upside trajectory.
The career risk is real and should be named. Community voices surface three structural downsides:
MCP (Model Context Protocol) explained: five primitives, STDIO vs Streamable HTTP, OAuth 2.1, and the access-control design most AI guides miss.
Andrej Karpathy co-founded OpenAI, led Tesla's Autopilot team, coined vibe coding, and founded Eureka Labs. A profile of the AI researcher who made deep learning accessible to millions.
The most current artificial intelligence statistics for 2026, covering market size, investment, adoption, workforce impact, productivity, healthcare, and public trust. 65 sourced data points from McKinsey, OECD, Goldman Sachs, Pew Research, and more.
