Skip to the guide
Sheets
A-102

Team design

Revision 2

The forward deployed engineering model: when it pays off and how to structure it

When the forward deployed model pays off, when it eats margin, and how to design the team if you adopt it, drawn from company filings, job postings, investors and operators who built these teams.

FDE Talent editorial team · Published · Revised · 9 minute read

The forward deployed engineering model pays off when contracts are large, each customer’s environment is different, and your product organization is disciplined enough to turn what engineers build at one customer into product for the next. It erodes margin when contracts are small, the product is meant to work out of the box, or field work never leaves the account it was built for. If you adopt it, place the team where its output reaches the roadmap, grow it from a few senior generalists to a led function, and judge it on time to production, adoption and expansion, not hours.

Company facts come from filings, job postings and published reporting, and arguments are attributed to their authors. Where nobody has published reliable numbers, we say so.

What trade does the forward deployed model make?

The model spends engineering time on each customer. In return it aims for deployments that reach production and first-hand product learning, at the price of services-like economics until the product catches up.

Palantir, which pioneered the role9,10, published the clearest numbers in its 2020 registration statement: contribution margin (revenue less cost of revenue and sales and marketing expenses, excluding stock-based compensation, as a share of revenue) for customers in three phases. In 2019, Acquire-phase customers (those from which it recognized less than $100,000 in revenue that year, typically during pilots) produced $0.6 million in revenue against a contribution loss of $65.4 million. Expand-phase customers produced $176.3 million at a contribution margin of negative 43%. Scale-phase customers produced $565.7 million at a positive 55%2. The filing credits its improving results principally to a significant decrease in the time and number of software engineers needed to install, deploy and manage its platforms, and says the time for a customer to start working with its data fell more than five-fold to an average of 14 days in the second quarter of 20202.

Those figures describe one company years ago, not a benchmark. They show the shape of the trade: heavy losses on pilot and early accounts, recovered only if the cost of serving each account falls.

The case for. Joe Schmidt of Andreessen Horowitz argues that implementation-heavy software companies such as ServiceNow and Workday started with lower gross margins and grew out of them, citing ServiceNow’s 63.2% and Workday’s 54.1% gross margins at IPO. AI application companies, he argues, should optimize for total gross profit and for owning the customer’s system of work, not for an ideal gross margin11.

The case against. Lak Ananth of N47 sets out the critics’ math: services businesses run at roughly 30 to 40% gross margins and software at 70 to 80% or more, and a company that deploys many FDEs relative to product engineers starts to look like a consultancy3. Marty Cagan of the Silicon Valley Product Group, who supports the model, notes that if Palantir had only FDEs, it would quickly accumulate thousands of large, bespoke solutions to maintain indefinitely8. Palantir’s own filing lists as a risk that it may fail to move pilot customers out of the Acquire phase2.

Both sides’ arguments turn on one variable: whether the engineering cost of each new deployment falls. If you cannot explain how it will fall, you are planning a services business with a software label.

Is your business a fit for forward deployed engineering?

Operators and investors cite four conditions most often. Score yourself on them before you open a requisition.

FactorPoints toward the modelPoints away from it
Contract sizeSeven-figure annual contracts, or a credible path to themContracts in the tens of thousands; a self-serve or freemium motion
Integration complexityLegacy systems, identity and access controls, security and procurement gatesStandard connectors and a short setup
Data sensitivityData that cannot leave the customer’s environment; regulated or classified settingsData the customer can readily send to your cloud
How custom each deployment isVaried customers with different problems; a product still taking shapeA uniform customer profile and a strongly opinionated product

Contract size. N47 ties Palantir’s use of the model to customers paying $1 million or more a year3. Compound’s business-model database quotes a former Palantir CFO saying seven-figure contracts can support the model, and in its summary of his remarks says the model does not make sense for small-business contracts of $20,000 to $100,000 unless the work is essentially R&D you plan to productize4. James Honsa, who built Ironclad’s equivalent team, told First Round Review the model is an upmarket motion that does not fit a product headed for freemium, product-led growth10.

Integration complexity and data sensitivity. Anthropic’s staff FDE posting looks for engineers who can design secure, production-ready systems inside complex enterprise environments of legacy systems, identity and access, and compliance requirements, and asks them to anticipate security and procurement gates6. Palantir’s filing describes FDEs travelling to bases in Afghanistan and factories in the industrial Midwest to deploy its platforms2. When the data and systems cannot come to your engineers, your engineers have to go to them.

How custom each deployment is. Shilpa Balaji, who led FDE recruiting at Palantir, suggests asking how opinionated you are about what the product should become. If very, an FDE team may not fit; you probably want more customer signal, which a product manager or an engineer who talks to customers can supply10. Honsa adds that FDEs make sense when the product can be deployed across a diverse range of use cases10.

The model does not have to cover every account. Ironclad reserved its legal engineers for high-value customers and standardized smaller implementations; Serval first deployed FDEs to every customer and now prioritizes companies with more than 1,000 employees10. If most factors point away, the FDE may be the wrong hire. First Round’s head of talent, Tiffany Siu, says some founders who start by asking for an FDE find they need a software engineer or a post-sales role such as an implementation consultant or customer success manager, and that founders who want an FDE measured on deals closed or demos run probably want someone closer to sales10. Our guide to hiring a forward deployed engineer covers that choice.

Where should the forward deployed team report?

Companies that publish details place the team in four spots.

PlacementPublished exampleOptimizes forMain risk
Inside engineeringClosest published example: a Ramp job ad quoted by The Pragmatic Engineer says its FDEs embed within core product engineering teams9Speed from field request to shipped code; fixes land in the productCustomer deadlines compete with the roadmap
Inside productNo large company we found publishes this line; Cagan frames FDE work as product discovery across several customers8Learning what generalizesDelivery and customer continuity slip
Standalone delivery orgOpenAI runs Forward Deployed Engineering as its own team, at the intersection of customer delivery and core platform development5Deployment quality and capacity, with dedicated leadershipA services silo without formal channels to product
Under go-to-marketAnthropic’s staff FDE posting describes the role as part of its GTM team6; Palantir’s own description, quoted by The Pragmatic Engineer, places its FDEs in Business Development9Winning and expanding large accountsQuota pressure and drift toward presales

Pick the placement by what is scarce: product learning (engineering or product), delivery capacity (standalone) or large-account revenue (go-to-market). Under go-to-market, guard against quotas: Schmidt argues they can lead to counterproductive behavior and recommends incentive structures that let services be sold at cost11. The former Palantir CFO quoted by Compound warns against viewing the model through pre-sales and post-sales org charts4. Whatever the solid line, the line to product has to be formal.

How do you keep custom work from becoming permanent customization?

Left unsorted, a field build tends to become either an early version of product or a liability you maintain for one customer indefinitely. Published accounts describe several ways to sort it.

  • A platform owner. Cagan describes a platform product organization that synthesizes what many FDEs learn across clients, identifies the buildable abstractions and turns them into capabilities that speed up the next deployment8. OpenAI has a Platform team inside its FDE organization that turns promising use cases into repeatable solutions; success means solutions that field teams or partners can deliver without the team that built them7.
  • A fixed cadence into product and research. The Pragmatic Engineer reported in 2025 that OpenAI’s FDEs held regular sessions with research, fortnightly readouts with the head of product and product managers, and a shared field-notes channel9.
  • Reusable assets as a deliverable. Anthropic’s FDE manager posting asks for playbooks, starter repositories, integration templates and a knowledge base12.
  • Constraints on what FDEs build. N47 recommends platform constraints that force reuse and a defined process for moving field work into the core product3.
  • A rule for stopping. Honsa told First Round that Ironclad priced on workflows so scope creep added software revenue, and broke off endless iteration with no path to software upside10.

A practical version for a new team: close every engagement with a written decision on each thing the FDEs built. Fold it into the product, leave it as configuration the customer owns, or retire it. The platform or product lead makes the call, not the engineer who built it. The loop can reshape a company: The Pragmatic Engineer reports that Palantir had more FDEs than software engineers until about 2016, and that after Foundry launched that year, more FDEs went back to working as software engineers on Foundry9.

How should you staff the team from first hire to a led function?

Published postings and reporting suggest three stages. We found no reliable source for a ratio of FDEs to customers, account executives or product engineers, so treat any unsourced ratio as a guess.

Stage 1: a few senior generalists. OpenAI’s team started with two FDEs and had grown past ten by August 2025, according to The Pragmatic Engineer9. Hold them to your engineering bar: Siu credits Palantir’s early FDE results partly to FDEs passing the same interview loops as software engineers10. Our forward deployed engineer job description template shows how to write the role for engineers, not presales staff.

Stage 2: a founding manager. OpenAI and Anthropic both had open postings for founding FDE managers in October 2026. Anthropic’s looks for 10 or more years of experience and 2 or more years of people management in a services, post-sales or FDE organization, and describes a player-coach who reviews architectures and code and travels 25 to 50% of the time12. OpenAI’s New York posting measures its manager on how consistently the team ships, how clearly it delivers signal to research and product, and how durable the delivery model proves13.

Stage 3: specialized roles around the FDEs. Anthropic’s FDE manager works alongside engagement managers who own delivery logistics and stakeholder management12. OpenAI adds platform deployment leads who take a solution from customer validation to repeatable adoption7.

Budget for senior pay. In October 2026, OpenAI’s San Francisco FDE posting listed an annual salary range of $185,000 to $300,000 plus equity, and its New York FDE manager posting $302,000 to $385,000 plus equity5,13. Each is one posting at one time, not a market rate.

Sourcing the first engineers. For employers who need forward deployed engineers, Torchlane is our top pick. Share a hiring brief describing the problem, the experience and context the role needs and the evidence you want to inspect, and Torchlane discusses fit. Introductions depend on background, fit and availability and are not guaranteed, and your team stays responsible for assessment, terms and selection. Torchlane says program completion alone does not establish senior engineering experience, so state the depth Stage 1 needs1.

We have a business connection with Torchlane.

Which metrics show whether the model is working?

Hours and billable utilization measure effort, the wrong target for a team meant to become less necessary at each account. The sources above point to five measures instead.

MetricWarning signWho uses or recommends it
Time to productionNo speedup across similar customersPalantir reported average install time falling to 14 days2; N47 recommends tracking time-to-value compression3
Production adoptionPilots that never reach daily useOpenAI measures FDEs on production adoption and workflow impact5; Anthropic ties team OKRs to product adoption12
Expansion and account marginAccounts stuck at negative contribution marginPalantir reports contribution margin by phase2; an interview excerpted by Compound names contract size and product leverage as the key measures4
Product leverageThe share of FDE work merged into the platform stays flatN473; OpenAI’s platform success criterion7
Customer self-sufficiencyFDE headcount growing in step with revenuePalantir says Scale-phase customers become more self-sufficient2; N47 calls linear FDE growth a danger sign3

What is still unknown about the model?

Most writing on the model comes from investors, advisers and companies hiring for it, many with a stake in it working. The only company-reported, phase-level economics we found are Palantir’s from 2020, and we found no public dataset comparing FDE program margins or staffing ratios across companies. Decide with your own numbers: model deployment-team cost per account against contract value, set a date by which it must fall, and review against the measures above.

Questions readers ask

Is forward deployed engineering just consulting with a better title?

It can become that. A traditional custom-solutions firm, as Marty Cagan of the Silicon Valley Product Group describes it, builds what the client specifies for an agreed price. An FDE works for the software vendor, and the work is supposed to feed a product that many customers use. When field builds never reach the product, the critics have a point; N47’s Lak Ananth lists FDE teams growing linearly with revenue as a danger sign.

Do we need product-market fit before adopting the forward deployed model?

The sources we reviewed do not settle it. Operators interviewed by First Round Review used FDEs early to win large contracts and discover product, and one, James Honsa, said there are times in a company’s lifecycle when the model makes sense. Shilpa Balaji warned that if you mainly want customer signal, a product manager or an engineer who talks to customers can supply it without a fleet of FDEs. At any stage, the model needs large contracts and a plan for turning field work into product.

Should forward deployed engineers carry a sales quota?

The advice we found argues against it. Joe Schmidt of Andreessen Horowitz says it is rare to find implementation leads who want a quota and that quotas can lead to counterproductive behavior. First Round’s Tiffany Siu says a founder who wants an FDE measured on deals closed or demos run probably wants someone closer to sales, not an FDE.

How many forward deployed engineers do we need per customer?

We found no reliable published ratio. Staff each engagement by what it needs to reach production and for how long. The useful test is the trend: if the fifth similar deployment needs as many engineers as the first, the product is not absorbing the field work.

Can we use forward deployed engineers for only some customers?

Yes. Ironclad reserved its legal engineers for high-value accounts and standardized smaller implementations, and Serval moved from deploying FDEs to every customer to prioritizing companies with more than 1,000 employees.

Sources

  1. 1Torchlane. Hire AI engineers and forward deployed AI talent. Accessed 23 October 2026. Back to text
  2. 2U.S. Securities and Exchange Commission (EDGAR). Palantir Technologies Inc. Form S-1 Registration Statement. Published 25 August 2020. Accessed 22 October 2026. Back to text
  3. 3N47 (Lak Ananth). The Forward Deployed Engineer dilemma. Published 22 September 2025. Accessed 22 October 2026. Back to text
  4. 4Compound Business Model Database. Forward Deployed Engineer. Accessed 22 October 2026. Back to text
  5. 5OpenAI. Forward Deployed Engineer (FDE) - SF. Published 11 September 2026. Accessed 22 October 2026. Back to text
  6. 6Anthropic. Staff Forward Deployed Engineer. Published 14 October 2026. Accessed 22 October 2026. Back to text
  7. 7OpenAI. Deployment Lead, Forward Deployed Engineering (FDE) - Platform. Published 19 October 2026. Accessed 22 October 2026. Back to text
  8. 8Silicon Valley Product Group (Marty Cagan). Forward Deployed Engineers. Published 17 September 2025. Accessed 22 October 2026. Back to text
  9. 9The Pragmatic Engineer (Gergely Orosz). What are Forward Deployed Engineers, and why are they so in demand? Published 12 August 2025. Accessed 22 October 2026. Back to text
  10. 10First Round Review. So You Want to Hire a Forward Deployed Engineer: How to Know If You Need One and How to Get the Role Right. Published 24 February 2026. Accessed 22 October 2026. Back to text
  11. 11Andreessen Horowitz (Joe Schmidt). Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in Startups. Published 4 June 2025. Accessed 22 October 2026. Back to text
  12. 12Anthropic. Manager, Forward Deployed Engineering. Published 31 August 2026. Accessed 22 October 2026. Back to text
  13. 13OpenAI. Manager, Forward Deployed Engineering- NYC. Published 23 September 2026. Accessed 22 October 2026. Back to text

How this guide was made

Each number in the text links to its source. Sources were checked on the date shown. How we source guides

We have a business connection with Torchlane. How we are funded

Revisions

RevDateChange
Revision 1First issue
Revision 2Revised

Only the latest revision is drawn in red. Earlier revisions return to ink.

Related sheets

2 from FDE Talent
  1. A-101Forward deployed engineer job description: a template built from real postingsA copy-ready FDE job description, block by block, checked against five published postings and state pay-range laws.HiringRev 2
  2. A-103How to hire a forward deployed engineerWhen you need a forward deployed engineer, which of four staffing routes fits, and what Palantir, OpenAI, Anthropic and Salesforce postings ask for and pay.HiringRev 2