FDE job postings up 1,165%: the numbers count titles, not work

Three sources, three growth figures: more than 800%, 1,165% and 5,230%. Yet on 30 May 2026 a curated index counted only 224 open forward deployed engineer roles, across 39 companies.

The gap does not mean anyone got it wrong. It shows that the percentages measure something quite different from what you care about. They count how often the words “Forward Deployed Engineer” appear in postings, not the work you would actually do.

For engineers already working as FDEs, or hoping to become one, the question worth asking is not how big the market is. It is what the posting on your screen actually describes. To answer that, you first need to understand what each number counts.

Three numbers, three different measures

Bloomberry compared the number of postings with an FDE title between January and October 2025 with the same period in 2024, and arrived at growth of 1,165%. That method counts titles. A company that renames its solutions engineer role as FDE is added to the tally, even though not a single extra line of code gets written at a customer.

The figure of more than 800% comes from the Financial Times, cited by Fast Company, and covers January to September 2025. It too counts postings, not hires. Fast Company’s own article notes that an FDE’s duties can vary from one company to another.

The most startling figure, 5,230%, is cited by KDnuggets from Indeed and compares April 2026 with January 2025. KDnuggets itself warns that this is an index calculated from a small January 2025 base, drawn from a single job site, and does not reflect headcount.

A hypothetical calculation shows the problem: a market that goes from 10 postings to 100 has grown 900%, yet 100 postings is still a very small market.

Figure	Source	Period	What is counted	What it does not tell you
More than 800%	Financial Times, via Fast Company	January – September 2025	Number of postings	Number of hires, nature of the work
1,165%	Bloomberry	January – October 2025 vs same period 2024	Postings with an FDE title	Which are real FDE roles and which are just renamed
5,230%	Indeed, via KDnuggets	April 2026 vs January 2025	Index on a small base, one job site	Absolute size
224 roles, 39 companies	JobsByCulture index, via KDnuggets	As of 30 May 2026	Curated open roles	Rate of growth

Taken together, the four rows show that the three percentages describe the momentum of a label. Only the absolute figure in the last row hints at scale, and that scale is far smaller than the headlines lead readers to imagine.

One title used for three jobs

Counting alone cannot show what is inside. That is why Bloomberry’s most valuable finding is not the 1,165% figure but the result of reading 1,000 postings closely. The author found that companies are using the same FDE title for three different kinds of work.

About 60% are builder FDEs, the group Bloomberry describes as the majority. About 30% are close to sales engineers, and about 10% are roles building internal tools. Bear in mind that this is one person’s manual classification of a sample, not official statistics, but it is enough to change how you read job postings.

Imagine you have saved 10 FDE postings to apply for. If Bloomberry’s proportions hold for your list, only about six of them involve building software at the customer.

All 10 carry the same title, but a year in they would leave you with three very different skill sets.

Renaming titles is nothing new

According to Tom Hollands of a16z, the FDE title was itself born of a renaming. In 2011 Palantir took its solutions engineers and integration engineers and gave them a new name. Hollands calls this title arbitrage: creating new titles to signal new powers taking shape inside an organisation.

The definition rewards a close reading: it is about signalling authority and says nothing about whether the work changes. Hollands also sees the downside of the mechanism: titles can enter a Red Queen race, in which prestige is inflated with no substance behind it.

Once a title becomes a hot signal in the market, renaming a role costs almost nothing and still makes the posting more attractive.

Tandem, a company with its own interest in the subject, argues that after the FDE title took off, companies began putting the FDE label on adjacent roles.

According to Tandem, a significant share of the growth in postings comes from renaming. You need not accept that claim wholesale. It is enough to note that it fits the roughly 40% of postings Bloomberry placed outside the builder group.

Two tests for reading a posting

Since the aggregate figures do not help, the sorting has to be done posting by posting. Tandem offers an output-based test: if the content of the posting is configuration but the title is FDE, it is an implementation engineer role.

KDnuggets offers a second, sharper test: does the work at the customer come back and change the product? If not, according to KDnuggets, it is consulting with a nicer title.

Try applying both tests to two hypothetical postings. Posting A reads: “configure workflows on our platform for enterprise customers, train users, support product demos”.

Posting B reads: “write production code to integrate with customer systems, identify recurring patterns across deployments and work with the product team to build them into the platform”.

Posting A fails both tests. Its main verbs are configure and demo, and there is no route for results to flow back into the product. Posting B passes both: you write software, and what you learn at the customer has somewhere to go in the product.

Posting A is not a bad job. Implementation engineering and sales engineering are respectable careers. The problem is that if you take it believing you are doing FDE work, two years later your CV will tell a different story from the one you meant to tell.

What to do about the hype

When filtering postings, read the verbs first and the title second. Words such as “build”, “ship”, “write production code” or “work with product” usually belong to the builder group. “Configure”, “demo” and “support the sales cycle” lean towards the other two. The job description is more honest than the title.

In interviews, turn the KDnuggets test into a question: when was the last time code or a finding from a deployment made it into the core product, and by what route? A real FDE team can usually answer straight away, with a concrete example. If the interviewer struggles, you have your answer.

When writing your CV, apply the same test to yourself. Do not just write “deployed for 5 customers”. Show the feedback loop, for example an integration pattern you wrote for one customer that later became a shared feature.

A line like that shows you have done the work of an FDE, not merely held the title.

The 1,165% figure will cool, like every growth curve measured on a new label. When it does, what will still count is whether you have actually taken a finding from a customer and got it into the product.