How many forward deployed engineers are there?

Per the Christian & Timbers figures TechCrunch reported in July 2026, about 17,000 in the US market, of whom roughly 2,000 can deliver measurable ROI. The same report described enterprises building internal teams of 20 to 100 and large consulting firms increasing their FDE needs tenfold. Treat the counts as a search firm's estimate, not a census.

What separates the 2,000 from the rest?

Mostly the product they work inside, not the person. The elite FDEs learned to build flagship features inside products that fight them: they work around missing harnesses, hand-roll evals, and force their learnings back into roadmaps by sheer persistence. A product that gives an ordinary engineer a harness they can change on site, an eval to add cases to, a handback owner, and a bounded sales promise turns that engineer into one of the 2,000.

Should we hire from the 2,000 or train the rest?

Train the rest, by fixing the product. The bidding war for the 2,000 runs against frontier labs whose staff-level FDE comp reaches around a million dollars, and a star FDE inside a product with no harness mostly produces forks. Fund the harness and the eval before headcount, put a product owner on the handback path, rewrite what sales may promise, then hire for judgment and customer accountability.

What should an FDE ask in an interview?

Three questions. How does a prompt change reach a customer's production and how long does it take. Is there an eval I can add the customer's cases to. Who on the product team owns what I learn, and what happened to the last three things an FDE brought back. The answers tell you whether the product will let you be effective.

Where can I read the whole FDE series?

The FDE Transition on falkster.com, a twice-weekly series for people in the seat and the leaders building around it. It starts with the thesis that the FDE is the Product Builder arriving from services and continues through the handback to product, the contract with engineering, the promise with sales, month two, metrics, career, comp, and when not to hire FDEs at all.

Why There Is a Shortage of Forward Deployed Engineers

Why is there a shortage of forward deployed engineers?

THE SHORT ANSWER

Because two jobs are hiding under one title, and the market is hiring for the harder one while equipping for the easier one. Christian & Timbers, reported by TechCrunch on July 30, 2026, counted about 17,000 forward deployed engineers in the US and about 2,000 who can deliver measurable ROI, with demand projected up 2,100% by year end. Chris Taylor of Ode with Anthropic drew the line: many FDEs can roll Claude Code out to a workforce, few can build a flagship AI feature. The second job needs four things the engineer does not carry in: a harness they can change on site without a redeploy, an eval the customer's cases can join, a handback path with a product owner on the other end, and a sales motion that sells scope. Give a competent engineer those and they deliver ROI. Take them away from one of the 2,000 and you get bespoke forks and a resignation. The shortage is real, and its cause is the product operating model around the seat.

The number that travels is 2,000. The number that matters is 15,000, because those are the engineers a leader can actually hire, and whether they deliver ROI is decided before they arrive.

An FDE is only as effective as the product lets them be on site. If a fix is a pull request and a release train, the customer waits and the engineer forks. If a fix is a context edit and an eval run, the customer sees it the same afternoon and the next customer inherits it. That difference is a product decision, and it is the whole shortage.

Part 2 of The FDE Transition makes the case in full and lists the four prerequisites. The handbook chapter on what has to change in the product before FDEs can work is the implementation guide.

Last reviewed 2026-09-22 · 1 min read

Why is there a shortage of forward deployed engineers?

SOURCES

THE LONG VERSION

RELATED ANSWERS