Same job,
eight costumes in sixty years
The FDE isn't a new role. From the IBM systems engineer to the forward deployed engineer, the "last-mile" labor of bending general-purpose technology to one company's specific business has never disappeared. It just keeps changing workstations and changing names.
Integration labor never disappears. It only migrates between four workstations, resurfacing under a new job title every decade. The FDE is just the 2024 costume.
Four workstations
Last-mile integration labor either gets bundled free into the vendor's price, outsourced to channels and systems integrators, baked into the product, or pushed onto the buyer's own IT. What decides where it lives is product maturity and gross margin.
Renamed, revived
Roughly every decade a new model declares it will kill this labor (boxed software, SaaS's "No Software", low-code, AI agents). A few years later it returns under a fresh job title. The job title is the fossil record.
The SaaS mirror
Salesforce promised "no software, no consultants," then bled 63% of customers a year and was forced to invent Customer Success. The FDE is the Customer Success of the AI era: it won't vanish, it'll be renamed and routed to partners.
Whenever a new technology first goes to market, the product is half-finished. It runs in a demo, but drop it into a real company's dirty data, legacy systems, and undocumented workflows and it falls over. Getting it from "runs" to "actually usable" takes a person who understands both the business and the technology, sitting next to the customer. That is integration labor.
That labor's cost is always there. The only question is whose ledger it lands on. There are four ways to book it, and these four workstations are the entire key to the next sixty years.
Bundled free into the vendor's price
The vendor pays for it and throws the engineer in as a freebie. The customer never sees the labor bill; it's hidden inside the price of the hardware or software.
Outsourced to channels and SIs
Handed to a ring of partners: value-added resellers, systems integrators, implementation consultants. The vendor just builds the product; the integration grunt-work goes to the channel.
Baked into the product itself
The labor gets understood and written into product features: config options, wizards, templates, today called Agents. The workstation everyone wants to reach, and the hardest to stay parked in.
Pushed onto the buyer's own IT
The customer staffs it themselves: the corporate MIS department, today's "citizen developers." The labor doesn't vanish; it becomes a fuzzy line item on the buyer's books.
The pattern: the earlier the technology, the more the labor crowds into ①; the more mature, the more it sinks toward ③; and when it can't sink, it bounces back and forth between ② and ④. The chart below is the path that labor walked over sixty years. Watch the line lunge twice toward "③ baked into the product," and twice get bounced right back.
Put this machine on a timeline and it runs eight full laps. At every stop the integration labor switches workstations and changes its name, but the work itself stays the same.
IBM threw the engineer in for free
In the mainframe era IBM didn't sell machines, it sold the whole capability of getting one running inside your business. IBM, Univac, Burroughs and RCA all bundled software, systems engineering and training into the hardware price with nothing priced separately. The person doing the work was the Systems Engineer (SE), paired one-to-one with a salesperson. IBM even pulled people fresh off the Apollo 11 programming team to deploy on-site. Before 1969, these services were "provided free of charge at the discretion of the IBM Branch office"[IBM history]. Free, hidden in the hardware price. That is the prehistoric form of the FDE.
Minicomputers kicked the labor out to the channel
In 1969 an antitrust threat forced IBM to "unbundle" and price systems engineering separately (regulation was a key trigger, not the only one), and the SE's low-level programming work flowed to cheaper third parties. Then DEC and Data General minicomputers dropped the price floor; vendors couldn't afford on-site engineers per customer, so they handed integration to OEMs and VARs. When Novell shipped its LAN in 1983, installing one was beyond ordinary users, and dealers became "network integrators" overnight.
Boxed software: first lunge at "③," and the labor fled
Lotus 1-2-3, WordPerfect and dBASE compressed software into a retail box, "shrinkware." This was workstation ③ in the extreme: work that used to need a programmer, pressed into a mass-replicable commodity with near-zero marginal cost. But the cheaper the box, the more orphaned the integration work around it, so it fled two ways: one to the channel (reseller Pomeroy's services were 12% of revenue but over half its profit), one pushed onto the buyer's own internal IT, a brand-new destination.
Client/server grew workstation ② into a giant
Client/server was heterogeneous, multi-vendor, networked. An IEEE paper called it "a sisyphean task", with total cost of ownership 3 to 6 times a mainframe's. Complexity exploded, and integration labor swelled into a giant industry: systems integration was about $14.9B in 1990 across 1,600 dedicated firms, reaching roughly $87.8B by 2000. Andersen Consulting renamed itself Accenture in 2001; EDS signed a ten-year, $3.2B Xerox outsourcing deal.
SaaS's "No Software": the first formal vow to kill implementation
Salesforce launched in 1999 with the No Software campaign, the word "software" in a red circle with a line through it. Benioff's own framing of the problem: "without software or hardware to install, and pricy consultants to hire"[official]. "No consultants" was written into the promise. That is the exact script of today's AI agent: "you don't manage it, it just runs." And the company that promised turnkey nearly died of churn, then was forced to staff up a small army it deliberately named Customer Success, not customer support.
The AWS Solutions Architect: the FDE's direct ancestor
Once AWS commoditized infrastructure, all three workstations came online at once. AWS states in plain text that the Solutions Architect is "a free resource" (workstation ①), owning the customer's overall technical relationship, acting as trusted advisor, working "as an extension of our customers"[AWS official]. Alongside sit paid Professional Services (② in-house) and the APN partner ecosystem (② outsourced). This is exactly Palantir's FDE "embedding with the customer," just without the "forward deployed" branding. A caveat: SA and FDE are not the same role, the SA leans pre-sales and design, the FDE comes later and writes production code, they're variants of the same labor at different points in the sale.
Low-code: second lunge at "③," and the same irony
Low-code platforms (OutSystems, Mendix, Microsoft Power Platform) pitched it bluntly: "eliminate ad-hoc development," "watch your backlog disappear," "no additional headcount." Another run at workstation ③, productizing the integration labor into a tool. And the same irony followed: low-code spawned an entire implementation-partner ecosystem, complete with certified "low-code functional consultants," and "low-code implementation services" became a category with its own analyst rankings. The labor didn't vanish; it relocated to "certified low-code consultant."
The FDE: sixty years on, back to workstation ①
The modern FDE traces to Palantir's Forward Deployed Software Engineer (codename Delta), embedding to configure the existing Foundry/Gotham platforms, structurally identical to the 1960s IBM SE. Palantir even demonstrates the ③ feedback loop: a field configuration that turns out useful for others gets generalized back into the base platform. The 2024–2026 receipts: OpenAI's FDE team was founded only in January 2025 and grew from 2 people to 52 by year-end; Anthropic is hiring FDEs right now, with one French-region posting listing a base of €205,000–220,000 (the only employer-published FDE band, the seven-figure numbers floating around are content-marketing blogs, ignore them). The spark was a16z's essay "Trading Margin for Moat," which lands squarely on the "fat margin" variable.
Lay the sixty years of job titles in a row and you see the strata of one job. The sales engineer is the clearest seam: the role has drifted under new names since IBM coined it in the 1960s. As one veteran put it, "the name kept changing, but the nature of the position itself remained essentially the same."
The FDE is, for all intents and purposes, the old solutions engineer / technical consultant in a fresh uniform. The tasks haven't changed: embed with clients, fix their broken systems, keep contracts alive through hand-holding. Same fundamental work, different wrapper. What changed was the story.
Tom White · "Sexy Titles, Unsexy Work" · commentator
Every time someone declares this labor dead, it returns a few years later under a new job title. The job title is the fingerprint of the decade.
SaaS deserves its own look, because the resemblance to today is uncanny. A model that vowed to kill implementation labor ended up merely renaming it Customer Success, then growing an implementation ecosystem six times its own size.
You can't only collect evidence that flatters the thesis. The strongest counterargument has weight, so here it is, with each camp's best advocate.
My read: the recession camp is more convincing, Mollick's line is nearly decisive, and the SaaS mirror has already played out the ending once. But one timing point matters: for the next 12 months both camps see the same picture, labs expanding FDEs, services revenue compounding. The real split is whether the labs start disbanding these teams in 2027. The FDE will recede, but don't pull the date too close, this is a 2027 question, not a 2026 one.
Connect the sixty years and the FDE's position is clear: it's what happens when an immature technology (large models) early in its life, pushed by fat margins and a long last mile, sucks integration labor back inside the vendor (workstation ①), the same move as IBM bundling the SE into its price. History also lets you predict: as models mature and patterns get baked into the product (③), and as GSIs take over standardized deployment (②), the FDE role will shrink back.
So the next time someone waxes lyrical about the FDE's "unique delivery philosophy," measure it with one question.
Your last mile, three years from now: does it settle into the product, or does it forever need a pile of people?
A ruler · The last-mile question
Those who can answer are genuinely building the slide into workstation ③. Those who can't, or who argue the opposite (that integration in the AI era can never be productized), either truly believe this time is different (then bring a Black Matter–grade argument), or they've dressed up "the product isn't mature yet" as "we have a unique delivery philosophy." This shadow has followed computing for sixty years. Every time it says it's leaving, it has only changed clothes.