What is the one test before hiring forward deployed engineers?

Who takes the work back, and what can they take it into. An FDE absorbs what one customer needs and the product absorbs it next, so the following customer needs less of an engineer. If no product manager is named as the reader of the handback and no configuration boundary exists for the pattern to land in, the company is hiring custom developers at a premium. Milos Mandic estimates around three in four self-described FDE teams are development shops, and Gartner's forecast that fewer than one in five engagements turn customer needs into product implies a share a little above 80 percent.

Why is forward deployed engineering an upmarket motion?

Because an engineer embedded with one customer costs more than a small contract returns. James Honsa, formerly head of legal engineering at Ironclad, told First Round Review that forward deployed engineering is definitionally an upmarket motion and that a company expecting a product-led or freemium end state should not do it. Frank Bien built Looker around roughly $25,000 a year per customer and 2,000 customers, with free trials and pre-sales implementation instead of embedded engineers. Gartner estimates FDE consulting fees alone could top $200,000 a quarter per use case.

Should an enterprise buy forward deployed engineers from a vendor?

Only for the workflow nobody can yet specify. Gartner's advice, reported by Matt Ashare at Channel Dive, is that customers who don't build their own engineering skills may pay premium rates for work that, once the scope is clear, a traditional services or partner model could deliver more cost-effectively. Buy the seat for discovery, with a named person on your side who can change the customer layer after the engineer leaves. For work you can specify, use a partner or your own engineer.

What should a company hire instead of an FDE?

The job that is actually open. Implementation engineers when the product is standardized and the work is onboarding, configuration, and integration. Sales engineers when success is measured in deals closed and demos run. A partner or ordinary services when the buyer's scope is clear. An internal AI engineer when the company wants its own people to own the trade-offs. Each is cheaper than an FDE and is the job most FDE requisitions describe.

How many forward deployed engineers are there really?

Gartner's Mukul Saha counts about 2,000 active FDEs and says demand is probably quadruple that. DXC committed to training tens of thousands of Claude-certified FDEs and, per CEO Raul Fernandez, had 86 on the books as of July 31, 2026, working in 57 customer environments. Microsoft plans to send 6,000 engineers into the field and Accenture has about 1,000 in its Gemini Enterprise Business Group, with the first federal cohort announced October 19, 2026. Anyone hiring the title at scale is mostly hiring people who are not yet FDEs, which is why Saha warns against a large team of consultants sitting on the bench.

When Not to Hire Forward Deployed Engineers: Five Cases

When should a company not hire forward deployed engineers?

THE SHORT ANSWER

Don't hire forward deployed engineers unless there is a loop for the work to come back through: a product manager who reads the handback, a configuration boundary the pattern can land in, and deals large enough to pay for the engineer. Five cases where the seat is the wrong hire. The product is opinionated and the work is implementation, so hire implementation engineers; Tiffany Siu at First Round says most founders asking for FDEs want someone closer to sales. The deals can't carry the seat; James Honsa calls forward deployed engineering definitionally an upmarket motion, and Gartner estimates FDE fees above $200,000 a quarter for one use case. Nobody in product will read what comes back. The buyer's scope is already clear, where Gartner says ordinary services or a partner deliver more cheaply. And the company is hiring the title because everyone else is, in a market Mukul Saha puts at about 2,000 active FDEs with demand around four times that. Milos Mandic's estimate is that three in four self-described FDE teams are development shops. In every case, name the job that is actually open and hire for that.

Don't hire forward deployed engineers unless there's a loop for the work to come back through, and you're willing to pay for it. The seat absorbs what one customer needs and the product absorbs it next. If nothing in the company can take the work back, you're hiring custom developers at a premium.

Five honest cases. The product is opinionated and the work is implementation, which Tiffany Siu at First Round describes as founders who "probably want someone closer to sales, not an FDE." The deals can't carry the seat, since James Honsa calls the motion "definitionally" upmarket and Gartner estimates fees above $200,000 a quarter for one use case. Nobody in product will read the handback. The buyer's scope is already clear, where Gartner says ordinary services deliver more cheaply. And the company is hiring the title because everyone else is, in a market Mukul Saha puts at about 2,000 active FDEs. Milos Mandic's estimate is that three in four self-described FDE teams are development shops.

Part 11 of The FDE Transition, When Not to Hire Forward Deployed Engineers: The Honest Cases, makes the case in full. The handbook chapter on what has to change in the product before FDEs can work lists the five things the loop needs, and the FDE versus sales engineer chapter has the one-question test for which job is actually open.

Last reviewed 2026-10-24 · 2 min read

When should a company not hire forward deployed engineers?

SOURCES

THE LONG VERSION

RELATED ANSWERS