Papers  /  Bloomberry · 1,000 FDE jobs
Job-market census~10 min readRead Aug 2026
Breakdown

One title,
three different jobs

Reading a thousand job postings is a better way to understand a role than reading a thousand opinions about it. A posting census of the forward deployed engineer market found what anyone who has interviewed for several of these already suspected: the title covers at least three distinct jobs, and the posting frequently does not tell you which one you are applying for.1

01

The three species under one title

SpeciesWhat the posting emphasisesWhat your week looks like
BuilderShip in the customer’s environment; own the full arc of a deployment9Few customers, deep, milestone-driven. Production systems someone depends on.
Pre-salesDemos, proofs of concept, technical qualification, supporting the account teamMany customers, shallow, quarter-driven. Often with quota or OTE attached.
Internal / platformEnablement, tooling, reference architectures, making other FDEs fasterRoadmap-driven, closer to a normal product team, further from customers.

Roughly a third of postings using the title are the pre-sales shape.1 That is not a criticism — it is a legitimate, well-paid career with its own progression — but it is a different rhythm from delivery work, and accepting one while expecting the other is the most common source of unhappiness in this role.

1,206strict-definition postings across 669 companies3
~$185Kmedian posted base for those roles3
~1/3of FDE-titled postings are pre-sales-shaped1
02

What every posting asks for

Across frontier labs, AI infrastructure companies and vertical startups, the same cluster recurs.

The technical list

  • Strong general engineering — usually Python and TypeScript, plus whatever the customer runs.
  • LLM application patterns: retrieval, tool use, agents, structured output.
  • Evaluation. The most-cited hard skill and the least-taught anywhere.
  • Integration reality: auth, pagination, rate limits, idempotency, other people’s schemas.
  • Deployment where you do not own the cloud — VPC, on-prem, sometimes air-gapped.
  • Increasingly: MCP servers and agent harnesses named as deliverables.10

The list that decides who is hired

  • Reframing a vague ask into a problem worth solving, before writing anything.
  • Learning an unfamiliar domain in days, well enough to be useful.
  • Saying no to a customer request and keeping the relationship stronger.
  • Judging when to ship something rough and when that would be negligent.
  • Being the only person who understands the system — then engineering your way out of it.

The technical bar is a strong generalist rather than a specialist; the differentiator is the second column. First Round’s account of hiring for this role puts the engineering bar at staff level, plus a temperament most strong engineers have never been asked to develop.11 If you are technically strong and have never sat in front of an unhappy customer, that gap is what to work on — not your algorithms.

→ The skill nobody teaches, and everybody asks for

Evaluation is the most-cited hard requirement across these postings and has almost no training material aimed at practitioners. Turning “it should be accurate” into a golden set, a human-agreement ceiling, a calibrated judge and a CI gate is a learnable, teachable skill — and being able to describe that pipeline in an interview is disproportionately effective. The method is in evals for client work.

03

Reading a posting properly

1

Find the compensation shape

Any mention of quota, OTE or a bookings-linked bonus means the role is pre-sales-shaped whatever the title says. Neither answer is disqualifying; not knowing before you accept is.

2

Count the customers

“Own the full arc of a deployment” is a builder posting.9 “Support the account team across a portfolio” is not. One deep engagement is a different job from six shallow ones.

3

Look for the product loop

Anthropic’s posting publishes a 40/30/30 split with 30% feeding learnings back into the product.10 A posting with no such loop is describing consultancy, and the work will not compound.

4

Check the travel line

Some roles are contractually 25–50% travel.15 It is uncompensated cost, and at 40% the effective hourly rate is not what the headline says.

5

Read the interview loop as data

A decomposition round scored on your questions means a builder role. A live product demo and a mock discovery call means pre-sales. The loop describes the job more honestly than the posting does.

→ The two questions that settle it

“What fraction of last quarter was spent pre-sale versus post-sale?” and “What did the last deployment contribute back to the product?” Ninety seconds, and they distinguish the three species better than any job description. Both answers are fine; a vague answer to the second one is the informative case.

04

Why the market looks like this

The posting growth is not a fashion cycle, and it is not really about hiring. It is a response to a measurement problem: capability is broadly available, enterprise outcomes are not, and a widely-reported finding put roughly 95% of enterprise AI pilots at no measurable P&L impact.17 The strategic answer several companies reached simultaneously was to spend margin on deployment depth — a16z’s services-led-growth argument — and the operational expression of that decision is a job posting.8

Hence the capital: OpenAI standing up a deployment organisation,5 Anthropic and Blackstone launching a $1.5B venture,6 Microsoft committing $2.5B to embed engineers with customers.7 A thousand postings is what that strategy looks like from the outside.

→ The honest caveat on all of this

Posting counts measure demand signals, not filled roles, and title inflation is real in a hot market — some of those postings are existing solutions-engineering jobs renamed. Treat the census as a map of what employers are asking for, which is genuinely useful for preparing, and not as a headcount. The compensation picture is bimodal and is handled separately in the salary breakdown.

If the builder variant is what you want

The loop is unusual, and practisable

Frequently asked

Quick answers

What does a census of forward deployed engineer job postings reveal?

That one title covers at least three distinct jobs: builder roles that own a deployment end to end, pre-sales roles built around demos and proofs of concept, and internal or platform roles that make other FDEs faster. Roughly a third of postings using the title are the pre-sales shape, and the posting frequently does not make clear which one you are applying for.

How do you tell whether an FDE role is pre-sales or delivery?

Look for the compensation shape first — any mention of quota, OTE or a bookings-linked bonus means pre-sales whatever the title says. Then count the customers: one deep engagement is a different job from six shallow ones. Then ask two questions directly: what fraction of last quarter was spent pre-sale versus post-sale, and what did the last deployment contribute back to the product.

What skills do FDE job postings ask for most?

Strong general engineering, LLM application patterns such as retrieval and agents, integration realities like authentication and rate limits, deployment into environments you do not own, and increasingly MCP servers as deliverables. Evaluation is the most-cited hard skill and the least taught anywhere. The differentiator in hiring is rarely the technical list — it is reframing a vague ask, learning a domain fast, and saying no while keeping the relationship.

Why has demand for forward deployed engineers grown so fast?

Because capability is broadly available while enterprise outcomes are not, and a widely reported finding put roughly 95% of enterprise AI pilots at no measurable profit-and-loss impact. Several companies reached the same strategic answer at once — spend margin on deployment depth — and the operational expression of that decision is a job posting. Hence the accompanying capital commitments from OpenAI, Anthropic and Microsoft.

Are posting counts a reliable measure of the FDE job market?

They measure demand signals rather than filled roles, and title inflation is real in a hot market — some postings are existing solutions-engineering jobs renamed. Treat a census as a map of what employers are asking for, which is genuinely useful for preparing, rather than as a headcount. Compensation in particular is bimodal and needs separate treatment.

Receipts

Sources

Every number on this page traces to one of these. Where a figure is self-reported or crowd-sourced rather than first-party, it is labelled inline.

Cited on this page

  1. Bloomberry — “I analyzed 1,000 forward deployed engineer jobs” — posting growth, builder/pre-sales/internal split. bloomberry.com/blog/i-analyzed-1000-forward-deployed-engineer-jobs-what-i-learned/
  2. Plank — FDE job-market census — 1,206 strict-definition postings across 669 companies; median posted base $185K. www.joinplank.com/fde-job-market
  3. OpenAI — launching the Deployment Companyopenai.com/index/openai-launches-the-deployment-company/
  4. TechCrunch — Anthropic and Blackstone launch “Ode” ($1.5B)techcrunch.com/2026/07/15/anthropic-blackstone-ode/
  5. CIO Dive — Microsoft commits $2.5B to embed engineers with customerswww.ciodive.com/news/microsoft-25b-embed-engineers/824392/
  6. a16z — Services-Led Growth — the margin-for-moat thesis behind FDE hiring. a16z.com/services-led-growth/
  7. OpenAI — Forward Deployed Engineer job description — “full arc of a deployment”. openai.com/careers/forward-deployed-engineer-(fde)-nyc-new-york-city/
  8. Anthropic — Forward Deployed Engineer, Applied AI (JD) — 40/30/30 split; MCP servers, sub-agents and agent skills as deliverables. jobs.menlovc.com/companies/anthropic/jobs/69674588-forward-deployed-engineer-applied-ai
  9. First Round Review — “So you want to hire a forward deployed engineer” — the staff-engineer bar. review.firstround.com/so-you-want-to-hire-a-forward-deployed-engineer/
  10. PostHog — “WTF is a forward deployed engineer?” — first-party account of the role at a product company, including travel reality. posthog.com/blog/forward-deployed-engineer
  11. MIT NANDA “State of AI in Business” — 95% of pilots with no measurable P&L impact — widely reported; figure cited via press coverage rather than a public PDF. techcrunch.com/2026/07/30/forward-deployed-engineers-are-the-ai-industrys-latest-talent-obsession/
1,000 FDE jobs, analysed · part of the FDE track · Vibe Engines · 2026
Finished this one? 0 / 111 Paper Breakdowns done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Paper Breakdowns