Home โ€บ Blog โ€บ Who Ships the Last Mile? The Forward Deployed Engineer and the Great Role Merge
Topic Explainer

Who Ships the Last Mile? The Forward Deployed Engineer and the Great Role Merge

In 2026 OpenAI, Microsoft and Anthropic each committed money, and in some cases thousands of engineers, to putting their own people inside customers' companies. This article explains the role they are copying, whether it is just consulting with a better title, and what the data says about software roles actually merging.

FL
FrontierAGI Team
โš ๏ธ How this was researched Everything here comes from web searches, because most primary documents were not directly reachable while writing. Where a figure traces to a company announcement, Gartner, Indeed or Stanford, the article says so, but several numbers reach us only through secondary coverage and are labelled that way. Many of the sources on the role itself are recruiting, vendor and career blogs, so treat their specifics as opinion. The "what you may have read" table near the end lists claims that circulate widely but did not hold up.

Why every AI vendor suddenly wants engineers inside your company

The starting point is an uncomfortable finding. MIT's NANDA initiative reported in 2025 that about 95% of the enterprise generative-AI pilots it studied showed no measurable profit-and-loss impact. Its authors pointed at integration and learning gaps, not at the quality of the models. That report was labelled preliminary, and the 95% figure is often quoted more broadly than the study supports, but it captured a mood: the models were good, and deployment was where value leaked.

The vendors' answer was to stop handing customers a product and walking away. Instead they would send engineers to sit inside the customer, write code against the customer's real systems, and stay until something worked. That job has a name, the Forward Deployed Engineer (FDE), and it is older than the AI boom.

~95%of studied enterprise gen-AI pilots showed no measurable P&L impact (MIT NANDA, 2025, preliminary)
6,000engineers and industry experts Microsoft said its Frontier Company would embed at customers (Jul 2026)
10,000"Frontier Deployed Engineers" Anthropic aims to train by end of 2027 (announced 2 Oct 2026)
~729%year-over-year rise in FDE postings on Indeed by April 2026, as reported; one job board only

What an FDE actually is

An FDE is an engineer employed by a product company who works embedded with a customer, writes production code to solve that customer's real problems, and passes what they learn back to the people building the core product. The role is usually traced to Palantir in the mid-2000s. You will see "2005" repeated in blogs, but no primary source confirms the year, so "mid-2000s" is the safe wording.

Palantir's own engineering blog gives the cleanest description. It splits engineers into Deltas, who work inside a customer's environment, and Devs, who build capabilities meant for many customers. The key idea in most accounts is that the loop closes: customer-specific work is meant to be pulled upstream into the product, so one customer's workaround becomes everyone's feature.

๐Ÿ’ก The test that matters Several independent sources converge on one question for telling a real FDE function from a rebranded one: does what the engineer learns at the customer actually reach the product roadmap? If not, it is consulting or staff augmentation under a new title. Try it yourself below. It is a heuristic assembled from practitioner sources, not an industry standard.

Is it a real FDE function, or consulting with a new title?

Tick every statement that is true of the setup you are looking at. The questions come from practitioner guides, and the verdict is only a rule of thumb.

Heuristics drawn from KDnuggets, Vibe Engines and Perspective AI's playbook. Not a standard.

How the role went from Palantir to the AI labs

Click an event for what happened, how sure we are, and where the information comes from.

Timeline of the forward deployed model

Dates come from the cited sources. Confidence badges say how firmly the date or claim is documented.

How an FDE differs from the people it gets confused with

The dividing line across the vendor and career sources is who writes and owns the production code, and when in the customer lifecycle the person is involved. Titles overlap heavily in practice, so use this as a guide to the typical case, not a rule.

FDE and its neighbours

Pick a role. Time-in-IDE figures come from a single source each and are illustrative.

Compiled from Kanerika, FullStack and HashLogics. Vendor and career blogs, not authoritative standards; the consultant description is the thinnest.

How an engagement runs

No single authoritative playbook exists, so the loop below is a synthesis of how practitioner guides describe the arc. The important details are the ranges the sources actually give. Engagement length varies from roughly 6 weeks to a year across guides, with 90 to 120 days a commonly recommended embed. Discovery usually takes one to four weeks.

The engagement loop, and the step that feeds the product

Click a step, or watch the marker travel round. The amber step is the one that separates an FDE function from a services shop.

Synthesis of InterviewBit, Perspective AI and The Forward Deployed. The "three clients" threshold appears in guides only as an example heuristic ("the same need in three unrelated accounts"), not as an established rule.

The 2026 scale-up

What changed in 2026 is scale. Three of the biggest AI vendors each announced a programme that treats embedded engineering as a core business, not a side team. They are not the same bet.

Three vendors, three versions of the model

VendorWhat was announcedShapeHow firmly sourced
OpenAI"The OpenAI Deployment Company", around 11 May 2026. Reported initial investment above $4 billion and a planned acquisition of the applied-AI firm Tomoro (about 150 engineers).A separate venture, majority-owned and controlled by OpenAI, led by COO Brad Lightcap.Announcement on openai.com; funding and acquisition details are from secondary coverage.
Microsoft"Frontier Company", 2 July 2026. $2.5 billion and about 6,000 engineers and industry experts embedded with customers.A unit Microsoft says "goes beyond" the forward-deployed label, leaning on partners such as Accenture, Capgemini, EY, KPMG and PwC.Microsoft's own blog post; it has not said whether the money is new or reallocated.
Anthropic"Claude Frontier Academy", 2 October 2026. $100 million to train 10,000 "Frontier Deployed Engineers" by end of 2027.A credentialing programme: a multi-day in-person phase, then a 12-week residency leading a real project at the engineer's own organisation. First cohorts include Accenture, Bain, Capgemini, Deloitte, McKinsey and others.Anthropic's announcement; first certified engineers expected in early 2027.
Anthropic's programme trains engineers who work at other organisations, so it differs from OpenAI's and Microsoft's model of employing the engineers directly. A CIO.com column argues the labs are answering the production-deployment problem, not the wider question of getting AI into the broader economy.

The economics: margin for a moat, or services in disguise?

The strongest case for the model is Andreessen Horowitz's "Trading Margin for Moat" essay (Joe Schmidt, around June 2025). Its argument is that an AI company should accept lower gross margins early, because the implementation work builds workflows and switching costs that later support pricing power. As precedent it points to cloud-era software: summaries of the essay report ServiceNow's gross margin at 63.2% and Workday's at 54.1% around their IPOs, rising to about 79% and 75% by 2024. We could not open the essay itself, so those figures are as reported by secondary summaries.

The critics make the mirror-image argument. If every customer needs bespoke work, you have a services business with software attached, with the margins and operating burden that implies. One worked example circulating among critics puts an 80% software margin and implementation labour worth 30% of contract value at roughly 50%. Play with that arithmetic yourself.

What implementation labour does to blended gross margin

Illustrative arithmetic only: blended margin โ‰ˆ software margin โˆ’ implementation cost as a share of contract value. It is not company data and ignores how costs fall as deployments repeat, which is exactly the moat argument.

Cloud-era comparison and the 80% / 30% example: a16z (via summaries) and a critical analysis.

The strengths and the costs, side by side

What it gives youWhat it costs
Firsthand knowledge of how customers really workEffort that scales with headcount, not like software
Faster integration in messy or locked-down environmentsCustomers may treat engineers as free services, eroding margin
Features validated by real use before core R&D builds themCustomisation sprawl and forked code if work never flows back
Trust that a salesperson rarely getsDistance from the core team, and "client myopia" favouring one account over the market
Fast career growth for the engineerBurnout from travel, firefighting and context switching; heavy travel is typical in postings (Anthropic's cite 25โ€“50%)

How fast is demand growing? Depends who is counting

Almost every article about FDEs opens with a growth number, and the numbers disagree. They come from different data sources and different windows, and nearly all come from job boards or vendors with something to sell, so the safe summary is "several hundred to over a thousand percent".

Reported year-over-year growth in FDE postings

Bars are as reported and are not directly comparable. Source type is shown under each label.

ParaformRecruiting platform's own postings, Q1 2025 to Q1 2026
+350%
Indeed643 to 5,330 postings, Apr 2025 to Apr 2026, via Business Insider; one job board
+729%
Unattributed estimateJan to Sep 2025; origin unclear
+800%
Live Data TechnologiesReported by secondary articles
+1,165%
From Paraform and Perspective AI, which repeat the original figures. We did not open the Indeed or Live Data reports. Growth from a small base also looks large: Indeed's own count rose from hundreds to thousands of postings.

The bigger story: what AI is doing to software roles

The FDE sits inside a larger argument, that AI is reshaping who does what in software. Three sources carry most of the weight, and they say different things.

1. Gartner: smaller teams, not fewer engineers

Gartner forecasts that by 2029, 60% of organisations will run smaller software engineering teams at scale, up from 15% in 2026 (reported 7 July 2026 by several outlets; we could not open Gartner's own release, and a Deloitte outlook cites a different Gartner figure, 80% by 2030). Its "tiny team" is usually four or five people, sometimes two or three, typically a product manager, a user or agent-experience designer and at least one AI-native engineer. Gartner frames it as restructuring, not cost-cutting, expects the number of teams to hold or grow, and cautions against cutting junior roles.

๐Ÿ’ก Worth noticing Gartner's tiny team still has three distinct roles. The popular claim that product manager, designer and engineer collapse into one person is not what this forecast says.

2. Indeed: developer postings are rebounding, but only in some layers

US software development postings, Indeed Hiring Lab (July 2026)

Different measures, different baselines. The 71% and 37% shares overlap and do not add up.

Since Feb 2025Software developer postings
+15%
Since Feb 2025All postings, for comparison
โˆ’7%
Versus Feb 2020Still below pre-pandemic
โˆ’27.5%
Share of the May 2025 to May 2026 rise from senior roles
71%
Share of that rise from AI-titled jobs
37%
Entry-level share of Q1 2026 software postings
4.5%
Indeed Hiring Lab and CNBC (11 Oct 2026). Coverage notes part of the rise is a recovery from the post-2022 downturn and that a causal link to AI is unproven.

3. The entry-level squeeze: one phrase, several different measures

"Entry-level hiring is down 65%" is repeated everywhere. That number comes from SignalFire and measures new-graduate hiring at the largest tech companies against 2019. The same data shows engineering hiring at those companies down only about 11%. Stanford's "Canaries in the Coal Mine" study measures something else again. Put side by side, they are not three versions of one number.

Four "entry-level decline" figures and what each really measures

โˆ’76%SignalFire: new-grad hiring at early-stage startups vs 2019
โˆ’76%
โˆ’65%SignalFire: new-grad hiring at the largest tech firms vs 2019
โˆ’65%
about โˆ’20%Stanford and coverage: employment of 22โ€“25-year-old software developers
~โˆ’20%
โˆ’13% to โˆ’16%Stanford: relative employment, ages 22โ€“25, most AI-exposed jobs (Nov 2025 paper; a later revision reportedly ~19%)
โˆ’13%
โˆ’11%SignalFire: all engineering hiring at the largest tech firms vs 2019
โˆ’11%
Sources: SignalFire's State of Tech Talent report via Startup Fortune (we could not open the report); Stanford SIEPR and its Canaries dashboard. The Stanford revision figure is from secondary coverage only. One analysis also finds entry-level postings rising while actual hiring fell sharply, so postings and hiring tell different stories.

Are roles merging, or are tasks shifting?

This is where the confident headlines run ahead of the evidence. The claim that product manager, designer and engineer are collapsing into a single "AI builder" is well documented as discussion and as a few company stories, but we found no systematic dataset, such as job-posting counts or organisation charts, showing job titles actually merging. Credible voices argue the opposite: that AI moved tasks between roles while accountability stayed where it was, and that the product manager role persists with its low-leverage tasks shrinking.

How strong is the evidence for each claim?

Higher rungs are stronger evidence. Each claim sits on the highest rung we could find for it.

Rung 4 ยท Labour-market dataEntry-level hiring has fallen at large tech firms (SignalFire, Stanford). Postings are rebounding mostly in senior and AI-titled roles (Indeed).
Rung 3 ยท Analyst forecastSmaller "tiny teams" with a PM, a designer and an AI-native engineer will become common by 2029 (Gartner). A forecast, not an observation.
Rung 2 ยท Practitioner discussion"Product engineer" and "design engineer" hybrids are replacing separate specialists. Many blogs, little measurement. Counter-voices say tasks shift without roles merging.
Rung 1 ยท Company anecdoteA product company running with two PMs; a large platform reportedly combining PM, design and engineering into one "builder" role. Single stories, partly secondhand.

Where the FDE fits in the merge story

The FDE merge is the one supported by definition: its duties literally overlap neighbouring jobs. The others are discussion.

Sales engineer + solutions architect + client-side developer
โ†’
Forward deployed engineer
Evidence: sources describe overlapping duties; a vendor-driven trend, backed by the 2026 programmes above.
Product manager + designer + engineer
โ†’
One "product engineer" or "AI builder"
Evidence: practitioner discussion and a few company stories only. Gartner's own model keeps all three roles.
Large engineering team
โ†’
"Tiny team" of 2โ€“5 including AI-native engineers
Evidence: analyst forecast (Gartner, 2029). Not yet observed at scale.

One more fact complicates the story. GitHub reportedly saw AI agents involved in about one in three pull requests, up from under one in ten a year earlier (via CNBC's coverage; we did not check it at source). More automated code does not obviously reduce demand for the person who owns the outcome, which is why the roles that grow in the data are senior engineers and anyone close to a customer's real problem.

What to do with this

If you are, or want to become, an FDE

If you are building or buying an FDE function

If you are an engineer choosing a path

Reading the numbers: what you may have seen versus what the sources say

Claim in circulationWhat the sources support
FDE postings are up more than 1,000%About 729% on Indeed, up to 1,165% elsewhere. All job-board or vendor data; "roughly 7x to 12x" is safer.
Engagements last 30 to 90 daysGuides range from about 6 weeks to a year; 90 to 120 days is a common recommendation.
FDEs spend 30โ€“40% of time on user research, 5โ€“15 interviews a weekNo source found.
There is a "three-client rule" for productisingOnly a heuristic in some guides, used in different ways. Not a standard.
Software job listings are up 30% in 2026Indeed Hiring Lab reports about +15% since Feb 2025, and still 27.5% below Feb 2020.
Entry-level developer hiring is down 65%SignalFire: new-grad hiring at the largest tech firms vs 2019. Other measures are smaller; see the chart above.
Gartner: 60% of organisations run smaller teams by 2029, up from 15% in 2026Reported consistently by news outlets (7 July 2026). We did not open Gartner's release; a Deloitte outlook cites 80% by 2030.
Palantir created the role in 2005Palantir as the origin is well supported; the exact year is not confirmed by a primary source.
Roles are merging into a single "AI builder"Well documented as discussion and anecdote; not shown in labour data. Gartner's model keeps separate roles.

๐Ÿ”— Reference links

๐Ÿงญ Closing

๐ŸŽฏ The bottom line The forward deployed engineer is a real and growing way of closing the gap between what AI products can do and what customers manage to deploy, and in 2026 the largest vendors made it a strategy, not a team. Whether it is a durable moat or consulting under a new name depends on one thing that is easy to state and hard to do: whether what engineers learn in the field flows back into the product. The wider claim that software roles are merging into one is not yet shown by the data; what the data does show is a squeeze on entry-level routes, a rebound concentrated in senior and AI-titled roles, and forecasts of smaller teams that still keep distinct jobs. The numbers behind all of this are noisier than the headlines suggest, so read them as direction, not precision.