What is time to landing?

Days from signature to the day a named person at the customer changes a prompt, a rule, or a threshold without calling the vendor and watches the eval rows run afterward. Go-live is the vendor's date. Landing is the customer's. Time to value and time to production stop at go-live and miss the stretch where the engineer is still holding the deployment up.

What is the reversal rate?

Of the workflows live at go-live, the share the customer switched off, overrode, or routed around by day 60. It comes from the day-60 reversal update in the handback and the watch list on the month-two page, and it is read next to whether the customer's eval rows still pass at the go-live rate.

What is the generalization rate?

Two parts: the share of handback packets that got a written decision from product within two weeks, and the share of patterns seen at three customers that shipped as product or configuration. Kill counts as a decision. It is a shared number. The FDE controls whether the packet went out, and product controls the answer. Gartner forecast on September 29, 2026 that through 2028 less than 20% of FDE engagements will turn recurring customer needs into core product, which is this number for the whole market.

Should FDEs be measured on utilization or revenue?

No. A utilization target pays for hours at the customer, and hours per deployment should fall as the product absorbs what the field learns. Revenue per FDE is a quota by another route, and FDEs should not carry one. Pull request counts fail for a similar reason: a harness change raises or lowers cost per case for every customer, so paying by the pull request buys more tools on every call.

Do the new FDE certifications measure performance?

They assess the engineer, not the engagement. Anthropic's Claude Frontier Academy, launched October 2, 2026 with $100 million to train 10,000 engineers by the end of 2027, ends in a 12-week residency and a badge. AWS's FDE Validated and FDE Advanced credentials are earned through hands-on validation in AWS-provisioned environments. Both tell a buyer the person can do the work. Whether a deployment worked is a question for day 60 at the customer.

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 with customer success, the scorecard, career, comp, and when not to hire FDEs at all.

How to Measure a Forward Deployed Engineer

How do you measure a forward deployed engineer?

THE SHORT ANSWER

Measure what the customer kept and what the product learned, with four numbers tracked against your own last quarter. Time to landing: days from signature to the first change a named person at the customer makes without the vendor. Reversal rate: of the workflows live at go-live, the share the customer switched off, overrode, or routed around by day 60. Generalization rate: the share of handback packets that got a written product decision within two weeks, and the share of three-customer patterns that shipped. Hours per deployment: FDE hours for the same class of customer, which should fall every quarter. The first two go on the engineer's scorecard, and the last two on the function's and on product's. Leave off headcount and badges, utilization, revenue per FDE, pull request counts, and CSAT on its own. There is no industry benchmark. Srikrishnan Ganesan of Rocketlane wrote exactly that in May 2026, and the targets in vendor posts are those firms' suggestions, not measurements.

The first week of October 2026 produced a lot of numbers about forward deployed engineers, and nearly all of them counted people: 10,000 to be trained by Anthropic's new academy, roughly 2,000 who fit the job description by Gartner analyst Mukul Saha's estimate, and new AWS credentials for partners. A badge says the engineer can do the work. It doesn't say whether an engagement worked.

For that I'd keep four numbers, each as a trend against your own last quarter, since nobody has a benchmark. Time to landing, reversal rate, generalization rate, and hours per deployment. The first two are the engineer's. The last two belong to the function and to the product owner who answers the handback. Each one comes off a page the earlier parts of the series already describe: the handshake, the handback packet, and the month-two page.

Part 7 of The FDE Transition, The FDE Scorecard: Count What Stayed, Not Who Was Sent, makes the case in full, including the five things to take off the scorecard. The handbook chapter on FDE economics covers why hours per deployment is the line to watch.

Last reviewed 2026-10-08 · 1 min read

How do you measure a forward deployed engineer?

SOURCES

THE LONG VERSION

RELATED ANSWERS