The Pulse: Forward deployed engineering heats up again

The Pragmatic Engineer · email · 2026-05 source ↗ Reader 🖥️

Career Development Enterprise AI Adoption & Readiness Forward-Deployed Engineer Founder Mode

The 'Forward Deployed Engineer' role is surging again at Google, OpenAI, and Anthropic — but its latest incarnation is collapsing into a customer-facing solutions-architect/consultant job, often outsourced into externally funded entities, which makes it a strong opportunity for new grads and a poor fit for experienced product engineers.

practical · mixed — Mixed expository/argumentative trend report with strong practical recommendations: Orosz tells different reader segments (new grads, experienced engineers, career counselors) what to do about the Forward Deployed Engineer (FDE) trend. The article reports market signals, then translates corporate language into career-advice claims, and ends with a forecast plus a who-should-take-this-job filter.

Structure

Part	Role
Framing: FDE demand is rising again after the Aug 2025 spike	context — establishes the trend the rest of the article will characterize
Three vendor case studies: Google (in-house spike, shortened interviews), OpenAI (Deployment Company + Tomoro acquisition), Anthropic (separate FDE consulting entity)	evidence — three independent data points that the trend is real and structurally similar
Analytical pivot: 'FDE or a consultant?' — comparing the 2025 hybrid FDE picture (platform + software + solutions engineering) to the 2026 version	argument — reinterprets the evidence as a category shift
Close reading of a Google Cloud FDE job advert with a 'plain English' translation and term-by-term decoding	evidence + rhetorical demonstration — shows the gap between corporate language and lived reality
Who-the-role-fits and who-it-doesn't lists	practical recommendation — translates the analytical claim into career advice
Equity/structural critique: at OpenAI/Anthropic, FDEs are in externally funded vehicles, so they don't share in upside	argument — interprets the corporate-structure choice as a signal about how 'core' FDEs are deemed
Aaron Levie quote on new-grad opportunity, plus historical analogy to tech consultancies hiring new grads	external authority + analogy — borrows credibility and frames the new-grad pitch
Four-segment market forecast (AI labs, AI vendors, non-AI companies, non-AI vendors)	conclusion — generalizes from the three case studies to an industry-wide trajectory

Key terms

Forward Deployed Engineer (FDE) Forward-Deployed Engineer
In Orosz's 2026 framing: a customer-facing engineer who codes, integrates, and hand-holds inside a customer's environment to make AI products deliver value — increasingly indistinguishable from a solutions architect or consultant, especially when housed in an externally funded entity. In his 2025 framing: a hybrid of platform engineering (contributing back to the platform), software engineering (building new solutions), and solutions engineering (integrating into customers' services).
Deployment Company (OpenAI Deployment Company) Forward-Deployed Engineer
A standalone, externally funded entity ($4B PE from TPG, Advent at $14B valuation) whose FDEs handle enterprise integration of OpenAI's models, with OpenAI as a partner rather than investor.
Founder's mindset / high-agency / white glove Founder Mode
Orosz explicitly translates these as: 'no spec, scope creep is your problem'; 'there are no resources besides your own'; 'never say no to the customer.' He treats them as corporate euphemisms that disguise the true working conditions of the role.
Solutions architect / consultant / systems integrator
The reference category Orosz argues the FDE role is collapsing into — customer-facing, integration-heavy, meeting-heavy work where the engineer is not 'core' to product development.
Core (vs. non-core)
Whether a role sits inside the product-building org with the associated equity and influence. Orosz infers from corporate structure (separate entity, external funding, non-parent stock) that FDEs are being deliberately positioned as non-core.
AI transformation Forward-Deployed Engineer
The enterprise-side demand driver: non-AI companies hiring FDEs to integrate AI into workflows and products.

Propositions

explicitDemand for FDEs is increasing again in 2026 after the August 2025 spike.conf: high
explicitGoogle is so eager to hire FDEs that it has compressed its interview process from 4-6 interviews over weeks to as few as two interviews in two days.conf: medium
explicitOpenAI and Anthropic are both externalising FDE work into separately funded entities rather than expanding their in-house FDE headcount.conf: high
explicitOpenAI's acquisition of Tomoro (150 FDEs across UK/Asia/Australia) signals the externalised vehicle, not the parent lab, will be the FDE consolidator.conf: high
explicitdevelopedThe 2026 FDE role is becoming indistinguishable from a solutions architect or consultant.conf: high
refines ←This Week in AI: Production Viability · p13 — Sharpens the FDE-as-consultant observation by identifying what the role is missing: the business-analyst stakeholder layer, leading to technically correct output that solves the wrong problem.
explicitTime allocation for a Google Cloud FDE is roughly 25% coding, 50% integration/plumbing, 25% meetings/customer hand-holding.conf: low
explicitRecruiting phrases like 'founder's mindset,' 'high-agency,' and 'white glove' systematically disguise difficult working conditions (no spec, no resources, no permission to say no).conf: medium
explicitBecause OpenAI/Anthropic FDEs work in externally funded vehicles, they will not receive parent-company stock and therefore won't share in the upside if their work creates parent-company value.conf: medium
explicitFDEs hired into external companies are not seen as 'core' by the AI labs.conf: medium
explicitThe FDE role is a good entry point for early-career engineers and a poor fit for experienced product-focused engineers.conf: medium
explicitFour buyer segments (AI labs, AI vendors, non-AI companies, non-AI vendors) all have reasons to hire FDEs, so demand will rise industry-wide.conf: medium
implicitCustomer-facing engineering work is structurally less valuable to AI labs than model development, which is why the labs are willing to externalise it.conf: high
implicitJob advert language can be reliably decoded by an experienced industry observer to reveal the 'real' job.conf: high
implicitEquity participation is the right yardstick for whether a technical role is 'core' or 'valuable.'conf: high
implicitThere is a stable identity called 'experienced engineer' for whom consulting-like work would feel like a step down.conf: high
implicitThe Palantir-style FDE — embedded engineer with strong feedback authority over product — is the historical baseline against which the 2026 version is a degradation.conf: medium
explicitNon-AI SaaS vendors benefit from FDEs because faster rollout enables larger contracts.conf: medium

Arguments

The FDE role is heating up again industry-wide. strength: medium

Explicit premises:

Google has launched an FDE recruitment spike with a compressed interview loop.
OpenAI created the OpenAI Deployment Company ($4B PE, $14B valuation) and acquired Tomoro (150 FDEs).
Anthropic announced a parallel FDE consulting entity backed by Blackstone, Hellman & Friedman, Goldman Sachs.

Implicit premises:

Three large frontier labs moving simultaneously constitutes a trend, not coincidence.
Hiring announcements and corporate structures are reliable indicators of underlying demand.
What frontier labs do will be imitated by other AI vendors and enterprises.

Inferences:

If demand is rising and supply of experienced engineers is reluctant, FDE wages and titles will need to be reshaped to attract talent — or the role will permanently shift toward new grads.
The 'externalised FDE' structure is a template other labs and large vendors will copy.

The 2026 FDE role is effectively a solutions architect / consultant role. strength: medium

Explicit premises:

The job is housed in quasi-external entities, separate from product orgs.
A specific Google Cloud job advert decodes to ~25/50/25 coding/integration/meetings.
Recruiting language ('founder's mindset', 'white glove') translates to consultant-like working conditions.

Implicit premises:

The Google Cloud advert is representative of FDE jobs at OpenAI and Anthropic's external entities.
The author's translation of recruiter language is broadly correct.
Solutions-architect/consultant is a stable, well-understood reference category.

Inferences:

If the role is really consulting, traditional FDE-as-product-feedback-loop value (the Palantir model) is being abandoned.
The 'critical feedback loop into product roadmap' line is mostly marketing.

FDEs in externalised entities are not 'core' to the AI labs. strength: medium

Explicit premises:

They sit in standalone companies with external funding.
Any stock they receive will not be parent-company stock.
If they were core, the labs would have continued in-house hiring instead.

Implicit premises:

Equity participation in the parent is the operative definition of 'core'.
Corporate-structure choices reveal the labs' true valuation of the work.

Inferences:

FDE work is being commoditised at the same time demand is rising.
The economic surplus from AI deployment will accrue to the labs and PE backers, not to the FDEs.

FDE roles are a good opportunity for new grads. strength: low

Explicit premises:

Product companies are hiring fewer new grads.
Tech consultancies have historically used consultant roles as new-grad on-ramps.
Aaron Levie (Box CEO) explicitly recommends college counsellors steer students toward FDE jobs.

Implicit premises:

The new-grad consultant career path historically led somewhere good.
Levie's industry vantage point gives his recommendation weight.
AI-agent fluency (Claude Code, MCP, CLIs, skills) is acquirable by motivated new grads.

Inferences:

Universities and bootcamps will reshape curricula around agentic coding tools to feed this pipeline.
The career ceiling for new-grad FDEs depends on whether the role becomes a stepping-stone or a trap.

Demand for FDE roles will keep rising. strength: medium

Explicit premises:

AI labs benefit from faster rollouts → more revenue.
AI vendors need FDEs to close enterprise deals.
Non-AI companies want FDEs for 'AI transformation' inside their workflows.
Non-AI SaaS vendors will use FDEs to expand contract size.

Implicit premises:

Enterprise AI adoption is genuinely bottlenecked by integration work that requires engineers, not just consultants or low-code tools.
The supply of capable FDEs will not catch up quickly enough to suppress demand.

Inferences:

FDE compensation will continue to lag product-engineering compensation, since the role is being commoditised.
There is room for an FDE-staffing-agency category beyond Tomoro.

Narratives

Google Cloud CEO Thomas Kurian's announcement of a new AI-focused Go-To-Market org with a hiring spike and 4-6 interviews compressed to 2 in two days.
→ Anchors the 'urgency / desperation' framing for vendor demand and supplies the most concrete piece of trend evidence.
The OpenAI Deployment Company being stood up with $4B from TPG and Advent at a $14B valuation, with OpenAI as partner-not-investor, and immediately acquiring Tomoro's 150-FDE workforce.
→ Illustrates the externalised-FDE structural pattern and implies that FDE delivery is being treated as a separable, financialisable business line.
Anthropic's 'unusually hand-wavy' parallel announcement backed by Blackstone, Hellman & Friedman, Goldman Sachs.
→ Shows the same pattern at a second lab, with the hand-waviness implying the labs are not yet sure how to talk publicly about this category.
Side-by-side reading of a Google Cloud FDE job advert and its 'plain English' translation, followed by term-by-term decoding ('founder's mindset' = no spec; 'white glove' = never say no).
→ Carries the article's central argument — that recruiter language conceals a consultant role — without needing to argue it abstractly; it is the rhetorical climax.
Historical analogy to tech consultancies hiring new grads who treated consulting as a real-world paid learning opportunity.
→ Supports the new-grad recommendation by importing a familiar precedent: 'consultant role = new-grad onramp.'
Box CEO Aaron Levie's recommendation that college career counsellors push FDE jobs, listing AI-agent fluency (coding agents, MCP, CLIs, Skills) as the kicker.
→ Borrows external industry authority to bolster the new-grad opportunity claim and signals the specific tooling stack the article assumes is the FDE skillset.

Questions addressed

✅ Is the FDE role really a rising trend, or hype?
Yes, rising — based on Google's hiring spike plus OpenAI and Anthropic each spinning up separately funded FDE entities.
✅ What does an FDE actually do day-to-day in 2026?
Roughly 25% coding, 50% integration, 25% customer hand-holding — i.e. a customer-facing solutions architect / consultant role.
✅ Why are AI labs externalising FDE work?
To keep core engineering focused on model development and treat customer deployment as a separately financed, partner-run activity.
✅ Who is FDE a good career bet for?
New grads and end-to-end shippers with ambiguity tolerance; not experienced product engineers.
⭕ Where does an FDE career lead next?
Not addressed — the article assumes the new-grad consultant pipeline historically led somewhere good without examining the trajectory.
⭕ How does the 2026 FDE relate to Palantir's original FDE role?
Palantir lineage is not named. The 'feedback loop into product' clause — the most Palantir-like aspect — is dismissed, but the original Palantir model (high-agency engineers with real product authority and substantial equity) is the unspoken contrast class.
⭕ What evidence beyond a single job advert supports the 'FDE = consultant' claim?
None offered — the OpenAI/Anthropic adverts are referenced but not read; comp data, retention data, or interviews are absent.
⭕ Could improved AI tooling collapse FDE demand by making integration self-serve?
Not considered. The four-segment forecast assumes integration friction stays high enough to require human engineers.
⭕ What does FDE mean for enterprise customers and their incumbent engineering teams?
Treated only from the FDE-career angle. Customer-side dynamics — capability transfer, lock-in, displacement of internal engineers — are absent.

Gaps

incompleteThe Palantir lineage of the FDE role is never named, even though the article's whole framing ('the role is becoming indistinguishable from a solutions architect') is implicitly a degradation claim against the Palantir baseline (embedded engineer with real product authority and equity).
Read next: Read the Palantir FDE accounts directly — Shyam Sankar's writing, Karp's 'The Technological Republic,' and ex-Palantir engineers' essays on the FDE model — to make the historical contrast explicit. Then re-evaluate whether the 2026 role is degradation, normalisation, or a new species.
incompleteThe 'FDE = consultant' argument rests on close reading of one Google Cloud job advert plus Orosz's plain-English translation. The OpenAI Deployment Company and Anthropic entity adverts are referenced but never analysed; comp structures, retention data, and FDE interviews from those orgs are missing.
Read next: Pull a sample of 10-20 current FDE job ads from Google, OpenAI Deployment Co., Anthropic's entity, Tomoro, Ramp, and incumbents (Accenture, Deloitte AI practices); compare title, responsibilities, comp, and reporting line. Look for first-person FDE writing (Anthropic's old FDE blogs, Ramp engineering blog).
incompleteNo counter-scenario for FDE demand. The forecast assumes integration friction stays high. The opposite trajectory — better agent tooling, MCP, vendor-native deployment workflows — could compress the FDE role within a few cycles.
Read next: Read MCP/agentic-deployment writing and self-serve enterprise AI adoption case studies. Watch for evidence that successful AI rollouts increasingly don't need embedded engineers — that would falsify the forecast.
incompleteThe 'equity = core' premise is load-bearing but undefended. Many genuinely strategic roles (compliance, security, design) are also outside equity-heavy product orgs; many fungible roles are inside them. The article treats corporate structure as a transparent revealed-preference signal, which it often isn't.
Read next: Read on how PE-backed carve-outs are typically structured (services arms of cloud vendors, IBM Global Services lineage) and whether 'externalised' has historically meant 'non-core' or 'differently capitalised.'
incompleteThe customer side is invisible. Whether enterprises actually want a 'white glove' integrator who won't push back, what FDEs displace inside customers' own engineering teams, and whether the FDE arrangement creates lock-in are not discussed.
Read next: Read enterprise-side accounts of working with FDEs / solutions architects (e.g., CIO trade press, the 'AI transformation' case studies the article alludes to). Look for the implicit theory of customer-vendor relationship the FDE role assumes.
closed byThe person your firm needs and cannot name — Provides a rare customer-side (rather than vendor-side) account of hiring an FDE-like integration role: the author explicitly valued that Sarah pushed back and diagnosed root process problems instead of being a compliant 'white glove' order-taker, and describes what the role displaced (the owner's own ad hoc, between-client-matters handling of process/tooling decisions). This only partially closes the gap — it is a single, promotional, small-firm anecdote, not the broader enterprise-side evidence the gap calls for.
uninformedThe author's '25% coding / 50% integration / 25% meetings' time split is asserted with no source. It may be roughly right, but it is presented as the punchline of the article and would benefit from at least one named source or survey.
Read next: Look for first-person FDE day-in-the-life accounts and any survey data (Pragmatic Engineer survey archives, Levels.fyi role pages, Reddit r/cscareerquestions threads tagged FDE).
incompleteLevie's recommendation is taken at face value. Levie runs an enterprise SaaS company that benefits from a larger FDE labour pool, so he is not a neutral observer of new-grad career advice.
Read next: Read independent career-research perspectives (e.g., Levels.fyi data on FDE comp trajectories, Pragmatic Engineer's own past coverage of career ladders) and compare new-grad FDE outcomes to new-grad SRE/PE/SWE outcomes 3-5 years out.

The Pulse: Forward deployed engineering heats up again

Structure

Key terms

Propositions

Arguments

Narratives

Questions addressed

Gaps

Related documents