Forward deployed engineers
Don't hire a demo engineer: 5 questions for an FDE
By Ravi Karwal · · 4 min read
The forward deployed engineer worth paying for leaves behind a system your team runs without them. The one you are more likely to interview leaves behind a demo. The resumes look the same. Five questions tell them apart in under an hour.
The hire is judged in month seven
An FDE hire, or a quarter-long FDE engagement, is one of the larger lines in a mid-market AI budget, and the return depends on one thing: what your company can operate after the engineer is gone. A demo engineer produces a launch. A production engineer produces a runbook and a workflow that has survived its second month, owned by someone on your payroll.
The title covers both. Rollout means taking a product the company bought, getting it in front of 400 employees, handling training and the identity integration, then showing a demo. Construction means sitting inside one workflow, building the system that fixes it, running it in production, and handing it to your team. Both jobs get the same title and a similar price. The second one compounds.
The five questions
Ask them in this order. Score each answer 0, 1 or 2.
1. What did you build that is still running six months later, and who owns it now? A 2 names a person at the client and describes what that person changed after the handover. A 0 describes a pilot or a demo day.
2. What did you remove from the stack? Builders subtract: a spreadsheet retired, a vendor cancelled. A candidate who has done rollout work will list what they added. Additions score 0.
3. Walk me through the workflow before you tell me the architecture. A candidate who opens with the model has not sat with the operators. A candidate who opens with "the accounts payable clerk gets an email with a PDF attached" has. Score the order they chose, not the vocabulary.
4. What broke in the second month, and who fixed it? Production breaks in the second month. A 2 says what broke, who at the client fixed it, and what the engineer had left behind so that person could. A 0 says nothing broke, or that the engineer flew back in.
5. Show me the document the client's team runs from. If it exists, they can send it. If the answer is "most of it was in my head," you are hearing the dependency you would be hiring. No document scores 0.
Under 6 out of 10 is a rollout engineer regardless of the title. That is fine if rollout is the job, and expensive if construction is.
Write the posting around the outcome
The posting that attracts the construction type does not list technologies. It names a result: one workflow, in production, owned by your team inside ninety days, with the runbook written.
That forces a decision on your side before the hire, which is the right order. Pick the workflow first. A company that hires an FDE and then looks for something to point them at has bought a rollout engineer whatever the job description says.
The supply numbers make the questions matter more
Rebecca Bellan reported the market for TechCrunch, drawing on a Christian & Timbers study shared with the publication.
Source facts: about 17,000 people in the US hold the forward deployed engineer title. The study puts the number with the sector knowledge, gravitas and hands-on applied AI experience to deliver meaningful ROI at about 2,000, and adds its own line on that figure: "Not 2,000 available, 2,000 total." At the start of 2026, 5 to 10% of companies planned to hire an FDE. By the end of the second quarter it was 70%. The largest consulting and services firms told the researchers they need ten times their current FDE headcount. Jeff Christian, who runs the search firm, said enterprises are hiring in the middle of summer at a speed he had not seen before.
My read: if 70% of companies are hiring from a pool of 2,000, most of them will hire from the other 15,000. The questions above are how you find out which pool your candidate came from before the contract is signed.
If you cannot hire one
A 200-person company will not win a bidding war for one of 2,000 people, and it does not need a permanent hire to get the first system built.
Borrow one for a quarter. Put the handover in the contract: a written system your team can run, with the same five questions asked at the end of the engagement instead of the start. Then measure what your own people maintain after the engineer leaves. That figure is the point of the hire, and it is the figure most of the 70% will not track.
If you have hired an FDE or bought an FDE engagement in the last year, one question: what would that person have scored on question one, and would you have signed if you had asked it first?