7,300 FDE Postings Chase 3,805 Title-Holders. Source the Rest

If you're trying to fill a forward deployed engineer seat by searching for the title, you're working a pool of 3,805 US people. Lightcast counted more than 7,300 US FDE postings in the first nine months of 2026, and the four biggest posters - Deloitte, Accenture, Google and KPMG - are already working that same pool.

Most of the people who can do the job have a different title. This is where they came from, what they're called now, and how to write a search that finds them.

The FDE market has more jobs than people with the title

Across the US there are about 1.9 FDE postings for every professional who holds the title, so the titled pool is oversubscribed before you send your first message. Lightcast's count went from fewer than 200 postings in 2023 to about 1,200 in 2025, then to more than 7,300 between January and September 2026.

In Refolk's index of professional profiles, 3,805 US profiles carry a forward deployed engineer title. The UK has 599, which puts the US pool at about 6.4 times the size of the UK's.

A company can open hundreds of reqs in a quarter. An engineer has to build the experience and then decide to put the new label on their profile. Postings move at budget speed. People move at career speed.

1.9

What a forward deployed engineer actually is

A forward deployed engineer is a software engineer who embeds with a customer, writes the code that makes a product work inside that customer's systems, and owns the outcome after the sale. Palantir created the role in the early 2010s and called it "Delta."

Palantir paired the Delta with an "Echo," a deployment strategist. The Echo is usually not a software engineer, and that matters for sourcing. A Palantir alum is not automatically an FDE candidate. You want the Deltas.

Elena Magrini, head of global research at Lightcast, says FDE roles share roughly half their skills with software engineering. The other half is the part that's hard to search for, which is why a title or skill match alone tells you so little.

Forward deployed engineer vs solutions engineer

A solutions engineer works pre-sales and is paid against a quota. A forward deployed engineer owns what happens after the sale and is paid base plus equity. The cleanest test of a req is its reporting line.

If the role reports into engineering, it's probably a real FDE job. If it reports into sales, it's probably SE work with a new name. The solutions engineers worth contacting are the ones who stayed on after the contract was signed and kept building.

Why searching the title puts you in the worst part of the market

The titled pool is small, new, and already targeted by the four biggest posters. Deloitte (872), Accenture (688), Google (499) and KPMG (447) together advertised 2,506 FDE roles, which is about 66% of every US title-holder. Deloitte's 872 postings alone come to about 23% of the US titled pool.

Those are advertised positions, not completed hires. They're still a fair measure of inbox pressure. Magrini's reading of the salary data is blunt: "growing wages suggest employers are competing for a limited pool of talent."

Everyone with Forward Deployed Engineer on their profile already has several recruiters in their inbox. Start somewhere else.

The title is also getting noisier. Accenture and Google Cloud are building a 1,000-person FDE team, partly by retraining experienced software engineers. TCS has targeted up to 8,900 employees for these roles and Infosys about 6,000. A growing share of the title belongs to people whose employers gave it to them internally, and those employers will want to keep them.

Palantir is still where most FDEs come from

Palantir is still the biggest single source of FDEs. It was the top current employer in both of Refolk's country samples, and the market's largest poster is openly hiring its alumni. One Deloitte FDE listing requires 3+ years of work with Palantir Foundry.

In a 25-profile sample of US title-holders in Refolk's index, Palantir was the current employer for 5. In the UK sample it was 6 of 25. Read those as directional, not as a census. They do line up with how the role spread out from Palantir.

The catch is that Palantir alumni get pulled from two sides: consultancies that need Foundry experience to deliver Palantir work, and AI companies building their own deployment teams. The better move is to look one step out from Palantir itself. Signals worth searching:

• Foundry or AIP on the profile, especially in the context of a build rather than a certification
• Ontology work, a strong sign of hands-on deployment
• Client-side Palantir experience at government agencies or in internal teams such as Acrisure-style "Palantir Center of Excellence" groups
• Delta history, not Echo: past titles or descriptions that show writing code, not just running the engagement

People on the client side built the same deployment skills from the other end of the contract, and they don't carry the title that draws the crowd.

The adjacent titles that hide FDEs

A lot of companies run FDE teams under other names, so your search has to list the variants instead of relying on the literal title. The naming isn't consistent even among the companies that set the trend:

• Anthropic: "Applied AI Engineer"
• OpenAI: keeps "Forward Deployed Engineer," and The OpenAI Deployment Company showed up as an employer in both of Refolk's country samples
• Adobe: "Forward Deployed AI Engineer"
• Databricks: "AI Engineer, FDE"
• Team names, not titles: Applied AI, Deployment, Field Engineering
• Post-sale builders: Solutions, Implementation and Customer Engineers who stayed with accounts after go-live

The samples also turned up smaller employers that are easy to overlook: Cresta, Roboflow and Gecko Robotics in the US, and ElevenLabs (3 of 25) in the UK. The UK sample even had a "Head of Forward Deployed Engineering" title, which tells you the function is mature enough to have its own leadership track there. Location surprised me too. New York (7) beat San Francisco (5) in the US sample.

Writing all of that as a Boolean string gets out of hand fast: six title variants, three team names, and a set of past employers, each with its own synonyms. That's the gap Refolk closes. You describe the person in plain English, and it searches profiles, GitHub and the open web, then returns a ranked shortlist.

Skill tags will shrink your pool to almost nothing

Don't filter FDE candidates on self-reported skill tags. Requiring "Python" on US Solutions, Implementation, Sales or Customer Engineers in Refolk's index left only 685 people, fewer than the titled FDE pool you were trying to get around.

That doesn't mean these engineers can't code. It means people don't keep self-reported skill tags up to date. A Snowflake or Google customer engineer (the top two employers in that sample, with 3 each) may write Python every day and still have a stale skills section. Tags are noisy in the other direction too. The same sample included a "Yoga Instructor."

To be clear about the limits: the count wasn't rerun without the skill filter, so this doesn't tell you how big the full adjacent pool is. It tells you the filter is broken. Use evidence that's harder to fake and less likely to go stale:

• Past employers known to run deployment teams (Palantir, the AI labs, data platforms)
• Team names in role descriptions: Applied AI, Deployment, Field Engineering
• GitHub activity that looks like deployment work: connectors, integrations, customer-facing SDK examples, internal tooling pushed to public repos
• Tenure after go-live: an SE who stayed on an account long after the sale was doing FDE work

How to write the search, step by step

Treat a good FDE search as a description of a career path, not a title match. Here's the sequence I'd run:

1. Check the req first. If it reports into sales and pays on quota, you're hiring a solutions engineer. Source for that instead.
2. Start with the headwater. Palantir Deltas and client-side Foundry/AIP builders, excluding Echo-only backgrounds.
3. Add the title variants. Applied AI Engineer, Forward Deployed AI Engineer, AI Engineer FDE, plus deployment and field engineering teams.
4. Add post-sale builders. Solutions, Implementation and Customer Engineers whose descriptions show shipped code and long post-sale tenure.
5. Drop skill-tag filters. Swap them for employer, team and GitHub evidence.
6. Deprioritize the titled pool. Contact title-holders last. They have the most competing offers.
7. Look past San Francisco. New York led the US sample, and the UK has a real 599-profile market.

Steps 2 through 5 are one query in Refolk, not five tabs and a spreadsheet.

Forward deployed engineer salary 2026

The median advertised US FDE salary is $195,456, per Lightcast. That's up 40% from 2023 and more than three times the median across all US job postings.

Deloitte's own FDE listings for ServiceNow and Palantir work give a range of $134,500 to $265,100. A range that wide probably reflects a title that covers everyone from retrained internal engineers to senior Foundry specialists.

$195,456

When you're pitching a solutions engineer, the comp structure is part of the offer. Moving from quota-linked pay to base plus equity means trading upside tied to deals for upside tied to the company. For an SE who already spends their time building after the sale, it can also be the first time their pay reflects the work they actually do.

2027 brings a new signal: Frontier Academy credentials

Anthropic's Claude Frontier Academy expects to award its first credentials in early 2027, and its first cohort works inside consultancies, banks and pharma. Those engineers come from Accenture, Bain, Capgemini, Commonwealth Bank of Australia, Deloitte, McKinsey, Morgan Stanley and Novo Nordisk.

Expect "Frontier Deployed Engineer" to start showing up on profiles at Accenture, Deloitte and McKinsey. It'll be a real signal of training. It'll also be a retention flag, because these employers paid to build this capability and will work hard to keep it.

Meanwhile AWS announced its FDE org on June 30, 2026, "backed by a $1 billion investment" and starting with hundreds of engineers, with Asa Kalavade as its VP of forward-deployed engineering. Those hires will draw on the same adjacent pools covered above. The sooner you're searching them, the less you're competing with AWS when you get there.

FAQ

How many forward deployed engineers are there in the US?

Refolk's index has 3,805 US profiles with a forward deployed engineer title and 599 in the UK. Lightcast counted more than 7,300 US FDE postings in the first nine months of 2026 alone, so there are about 1.9 open postings for every US title-holder. Many more FDE-capable engineers work under titles like Applied AI Engineer or Implementation Engineer.

What is the difference between a forward deployed engineer vs solutions engineer?

A solutions engineer works before the sale, usually reports into sales, and is paid against a quota. A forward deployed engineer owns the deployment after the sale, reports into engineering, and is paid base plus equity. The SEs most likely to make good FDEs are the ones who stayed on accounts after go-live and kept writing code.

Where do I find forward deployed engineer candidates if not by title?

Start with Palantir Deltas and client-side Foundry or AIP builders, then add title variants such as Applied AI Engineer and AI Engineer FDE, deployment and field engineering teams, and post-sale solutions or implementation engineers with GitHub evidence of shipped code. Skip skill-tag filters, which shrink the pool without making it any better.