The three jobs hiding behind the FDE title

If you are hiring for this title, applying for it, or buying it from a vendor, the first question is which job is actually being described. The title does not tell you, and the difference is large enough to change the outcome.

The best public evidence on this is an analysis of 1,000 job postings carrying the title, published by Henley Wing Chiu on 18 November 2025 using data from Revealera. It found the postings sorted into three groups.

Job one: the builder, 60 percent of postings

This is the role the guides describe. A production engineer embedded with a customer, writing code that runs in that customer's systems, accountable for the deployment.

In this group, 70 to 90 percent of the week goes on coding. The advertised salary range in the analysis sat at $140,000 to $250,000. Pay is structured like engineering pay: base plus equity.

This is the job that produces the outcomes people associate with the model, and it is the one where the three tests from our definition page all pass.

Job two: the sales engineer with a better title, 30 percent of postings

This role supports the sale and helps with implementation afterwards. Demos, proofs of concept, technical objection handling, then assistance getting the customer live.

Coding drops to 30 to 40 percent of the week. The advertised range in the analysis sat at $120,000 to $200,000 plus commission, and the pay structure is the tell: variable compensation tied to bookings.

This is a legitimate and valuable job. It is presales, and calling it forward deployed engineering creates two problems. Candidates expecting to build production systems arrive and find they are demoing. Buyers expecting an engineer who owns their deployment get someone whose incentive ends at signature.

Job three: the internal tools builder, 10 percent of postings

This one surprised us. In 10 percent of postings the role faced no external customer at all: building internal tooling for go-to-market or revenue operations teams, with the company's own staff as the users.

The advertised range sat at $100,000 to $180,000. The work can be good work. It is not forward deployment in any sense the term originally carried, because the whole point of the model is being deployed forward, into somebody else's environment.

Three tests that sort them in one conversation

Ask for the coding percentage. "What share of a typical week does this person spend writing code that gets merged?" A number under 50 means job two or three, whatever the title says.

Ask about the quota. Across all 1,000 postings, 8 percent mentioned commission or on-target earnings and none were quota-carrying, while 70 percent mentioned equity. If a role carries a number, the incentive is the deal rather than the deployment. That is not disqualifying and it is worth knowing before you accept or buy.

Ask who the user is. If the answer is "our sales team" or "our revenue operations group", it is job three.

What this means if you are hiring

Say which job you are hiring for, in the first line of the description. Vagueness here is expensive twice: it widens your funnel with the wrong candidates, and the ones you hire leave when they discover the mismatch.

The experience mix in the data is worth planning around. Of the 1,000 postings, 12 percent targeted zero to two years of experience, 60 percent three to five years, 20 percent six to eight, and 8 percent nine or more. The role is being staffed mid-level, which is consistent with First Round Review's finding that ten or more years at a large tech company can be a red flag for this work, because the role needs someone who operates without the scaffolding a big company provides.

Our job description page has a template that names the job in line one.

What this means if you are buying

When a vendor says they will give you forward deployed engineers, the claim is compatible with all three jobs. Three questions settle it.

What share of the week will these engineers spend in our repository? Who is accountable, by name, if this does not reach production? Are these engineers compensated on our deployment going live, or on the contract being signed?

A vendor selling job one will answer all three without hesitating. A vendor selling job two will reframe the third question. Our questions to ask a vendor page has the rest of the list, and how to choose a partner covers the evaluation.

Why the title spread this fast

Titles inflate when demand outruns supply, and this demand grew faster than almost any role in the industry: the same analysis measured postings with the title up 1,165 percent year over year, comparing January to October 2025 against the same months in 2024, with October 2025 the highest volume on record.

When a title becomes the one candidates want, roles get relabelled to attract them. That is the whole mechanism, and it is why the definitional discipline on this page matters more than it would for an established job.

Our position

We think the industry should keep the term for job one and stop using it for the other two. Forward deployment means being deployed into someone else's environment with accountability for what happens there. A presales engineer and an internal tools engineer are both doing real work, and neither is that.

For what it is worth on our own account: our engagements are job one. Engineers in your repository, production code, a named production date, and a named handover date. That is the service, and it is the only version of this we sell.