AI Deployment is the new function
Frontier models are capable. The hard part is getting them deployed, integrated and trusted inside a real business — and that work has hardened into a distinct function with its own roles, ladders and budgets. Here is what the function is, why it appeared, and where the Forward Deployed Engineer sits in it.
“An FDE exists to fill the gap between what the product does and what the customer needs.” — Bob McGrew, who created the Forward Deployed Engineer role at Palantir; later Chief Research Officer, OpenAI
What this function is — and why it appeared
“AI deployment” is the work of taking a capable model and making it actually run inside one customer’s business — wiring it into their data and systems, earning the trust of cautious stakeholders, and turning a demo into a dependable workflow. It is customer-facing delivery, not model research. And it appeared as its own function because the value gap is enormous:
As Forbes put it, “the most expensive job in enterprise AI is no longer the researcher building frontier models but the engineer flying to a customer site to make those models work” (May 2026). The frontier labs agree with their capital: in May 2026 OpenAI launched a dedicated “Deployment Company” — a $4B+ venture whose entire job is to embed Forward Deployed Engineers into enterprises and turn AI pilots into running systems. When the model-maker stands up a separate company just to deploy, deployment is a function.
IK's FAANG+ instructors have shipped deployments like these themselves — the FDE track is structured end-to-end around the four-phase lifecycle above.
The deployment roles, in one picture
Two roles carry the function, and they are routinely confused. The cleanest way to see the difference is to stop thinking of one straight pre-sale-to-post-sale line and look at two lanes — a commercial lane that wins the deal, and a delivery lane that ships it.
So does the FDE do discovery and scoping? Yes — just a different kind. The pre-sale discovery is commercial (“is this the right deal?”); the FDE’s is technical (“how do we build this in your stack?”). The FDE is not “post-sale only” — it is delivery-owning, and delivery starts with the FDE’s own scoping. The two lanes overlap, and at several labs one person spans both.
Customer-facing from the first conversation. Qualifies the opportunity, proves it can work, designs the architecture, and gets the deal technically over the line — more advise than build.
Engaged once the deal is real. Runs its own technical discovery, then builds the solution inside the customer's environment, integrates it, ships it to production, and hands it over — more build than advise, customer-facing throughout.
FDE vs Solution Architect — the skill shape
Same two poles, drawn as a skill radar. They share discovery, scoping and architecture — but the FDE pushes production engineering, while the Solution Architect pushes commercial and advisory work.
Two fixed poles. The FDE owns the build half (left); the Solution Architect owns the advise / sell / enable half (right). They meet on discovery & scoping — the shared craft. Every real role sits somewhere between these two shapes. 1 = not in JD · 3 = peripheral · 5 = role-defining.
How this is scored · the gap on each axis
Six fixed axes, one 1–5 rubric, scored against the canonical FDE and Solution-Architect JD language — the same framework every lab-page radar now uses, so the four real roles (below) are directly comparable. 1 = not in the JD · 3 = peripheral expectation · 5 = load-bearing (role-defining). Source of truth: FDE/research/adjacent_roles_framework.md.
Want the bigger picture — how the FDE compares to the ML and AI Engineer? See the three-role career map →
The FDE is not one job — it is a leveled role
The biggest misread of the FDE is treating it as a single seniority. It is a full career ladder. Colin Jarvis, who leads OpenAI’s Forward Deployed org, grew the team from 2 to roughly 52 engineers in a single year and calls it “the hardest job to hire for.” The labs have published their ladders — here are two.
OpenAI — the forward-deployed org
People-manager for a pod of 6–10 FDEs. Owns hiring, growth, and end-to-end delivery for the customers the pod is tagged to. Three open postings: SF — the first US FDE leadership role with a posted band ($280–335K) — plus London and Munich.
Delivery lead for one customer engagement — runs milestones, scope, stakeholder alignment. Not a people manager. OpenAI brands these openings as "Founding TDLs," accountable for early design-partner deployments.
People-manager for the Platform Engineering sub-team. Translates recurring patterns across deployments into platform bets — what to build once so 20 FDEs don't rebuild it 20 times.
The customer's engineer-on-the-ground. Owns discovery, technical scoping, system design, build and production rollout for one strategic account. Judged on delivery breadth and customer credibility.
Pairs with the FDE on the same account, but owns the code. Builds the custom software that ships the model into the customer's production environment — often coding side-by-side with the customer's engineers.
Leverage function — builds reusable platform capabilities so the FDE team doesn't reinvent the wheel for every engagement. Heavier SWE/ML bar; comp lands in Staff-SWE territory.
FDE shape applied to high-trust deployments. Embeds with security-sensitive customers, hardens model deployments to enterprise compliance bars. Reports into OpenAI Security org, not the FDE org.
Internal-facing PM. Builds the systems that ramp every new FDE — onboarding paths, playbooks, knowledge bases. Live in the May snapshot but currently unlisted — its existence signals OpenAI funds FDE training as a discipline.
How we drew this — built from 33 live OpenAI FDE-family postings on Ashby (July 2026 snapshot). OpenAI hasn't published an internal org chart; the structure is read off the JD corpus.
Observed in the JDs
- One department: 30 of 33 postings sit under "Model Deployment for Business" — single FDE org. The other 3 are edge cases (Security, Hardware, Gov).
- Two pillars in the JD language: the phrase "intersection of customer delivery and core platform development" recurs across postings — the basis for splitting Row 2 into TDL (delivery) and Platform Eng Mgr (platform).
- FDE + FDSWE explicitly pair on accounts: the FDSWE JD says "work with our customers and OpenAI Forward Deployed Engineers" — they're staffed together, not independently.
- Manager FDE manages ICs: the Manager JD asks for "2+ years managing FDE or customer-facing engineers" — confirms the apex role.
- Security Eng sits outside the FDE org: Ashby's department tag is "Security," not "Model Deployment for Business" — uses the FDE title for shape, not reporting line.
Inferred (not stated in any JD)
- TDL reporting to Manager FDE — the most parsimonious read given title structure and shared department, but no JD says it.
- The two pillars being siblings under one Manager FDE — the 2 open Manager FDE postings are both EMEA; US likely has additional Manager FDEs that aren't currently hiring.
- Enablement PM sitting parallel, not inside the chain — it's in the same department, but its scope is internal-facing program management, not delivery.
This is a role-shape archetype, not a seat-count chart. The actual graph likely has multiple pods (the 2 Manager FDEs are EMEA; TDL, Platform Mgr, Platform Eng openings are SF/NYC).
Google Cloud — the two-track FDE ladder (I–V)
- FDE V$262000 – $3650008+ yrsJD →
- FDE IV$207000 – $3010008+ yrsJD →
- FDE III$174000 – $2530005+ yrsJD →
- FDE II non-USComp not published · non-US2+ yrsJD →
- FDE I Taken downComp not published3+ yrsOffline JD →
- FDE VNo posting at this level
- FDE IV$207000 – $3010008+ yrsJD →
- FDE III$174000 – $2530005+ yrsJD →
- FDE II Taken down$147,000 – $211,0002+ yrsOffline JD →
- FDE I Taken down$123,000 – $174,0001+ yrsOffline JD →
Numbered structure now extends to a GenAI FDE V at the top; Applied AI tops at IV. Same posted comp band at most shared rungs. They diverge at FDE I: Applied AI is currently the only US entry path; GenAI's US FDE I has been retired (still posted abroad). The partner-channel "Partner FDE" roles sit outside this direct-customer ladder — see the Delivery-channel lens below. Comp bands last rotated 2026-06-06 — earlier bands recorded in state.json history.
Want the exact skill set this role demands at each level? Walk the full FDE skills roadmap →
The same role, across every major lab
This is not an OpenAI-and-Google story. Every frontier lab — and the enterprise platforms and consultancies behind them — now runs a forward-deployed ladder. The biggest names in AI have put ~$9.75B directly behind it (OpenAI $4B+ · Microsoft $2.5B · Anthropic $1.5B · Amazon $1B · Google $750M), and our scan of 408 US FDE postings found the title at 232 distinct hirers. The newest — and largest single — bet is Microsoft’s July-2026 $2.5B Frontier Company, embedding 6,000 experts inside customers and positioned “beyond FDE,” landing two days after AWS’s June $1B in-house FDE org — the pattern now reaching from the AI-native labs into the enterprise-incumbent + Big-4 ecosystem.
| Company | FDE family | Levels | US comp | Signal |
|---|---|---|---|---|
| OpenAI | Forward Deployed Engineer (+ FDSWE) | IC + manager tracks | $153K–$385K | Multi-track, scaling fast |
| Google Cloud | Forward Deployed Engineer I–V | Full IC ladder + EM rail | $123K–$365K | A whole FDE org |
| Databricks | FDE + AI-Engineer FDE | Full IC → Head ladder | $181K–$360K | Most built-out · ~15 countries |
| Anthropic | Forward Deployed Engineer | Founding IC + manager | $200K–$400K OTE | Applied AI team |
| Meta | FD Engineer + FD Solutions Architect | Build + sell titles | $130K–$210K | Two forward-deployed titles |
| Amazon (AWS) | Forward Deployed Engineering org | In-house org (announced) | Not yet posted | $1B · “thousands” embedded |
| xAI | Forward Deployed Engineer, X API | IC · DevEx/productized | $180K–$440K base | Tops the comp landscape |
| NVIDIA | Forward Deployed Architect | L5–L6 + adjacent SA | $224K–$431K base | First infra-layer FDE |
| Deloitte | Forward Deployed Engineer – Databricks | FDE / Senior / Lead | Rarely posted | #1 hirer · 69 of 408 US JDs |
Comp bands and levels are drawn from our own lab deep-dives (each company links to the full breakdown). Hirer breadth from the 408-JD LinkedIn scan, snapshot 2026-06-16. The pattern — every lab, the same ladder, real capital — is the tell: this is a standing function, not a hype cycle.
You have the function and the role. Next, go to the source — what 408 real Forward Deployed Engineer job postings actually ask for, decoded into the skills, levels and pay you can position against.
408 LinkedIn FDE JDs, decoded →An Interview Kickstart advisor walks you through where you stand today, the exact gap to close, and the fastest route to a Forward Deployed Engineer offer — built around your background.
Book a call with an advisor →