Are Recruiters Ruining Forward Deployed Engineering?!?

Okey dokey my lovely recruitniks. There's a new unicorn in town.

The Forward Deployed Engineer.

You can find them wandering around the woods…naked, drinking from a mountain stream….aren’t they majestic?!? They are the answer to every hiring manager’s problems.

Do you run a website that generates “What K-pop band are you” quizzes? those guys need a Forward Deployed Engineer.

Sales team not selling 3 products for every one demo? Forward Deployed Engineer.

Leg fell off??? Forward Deployed Engineer.

If you've opened LinkedIn in the last six months, you've seen "The hottest job in tech." "A revolutionary new breed of engineer." "The future of AI." Folk left right and centre telling you FDEs are the Navy SEALs of software.

These posts are starting to give me the heebiejeebies.

I've seen this happen before.

When everyone moved to the cloud, every sysadmin job on earth got renamed "DevOps Engineer" overnight. Then SRE became the shiny one. Then DevOps engineers take a "DevOps" job, then spend the next two years babysitting servers.

So let's ask the question.

Is Forward Deployed Engineering bullshit?

Theres also some nifty tips on how to spot real FDE roles and candidates at the bottom, so stick around….

1. So what actually is an FDE?

Palantir coined the term in the mid-2000s, embedding engineers directly with US government customers. Internally they called them Deltas (typical Palantir making everything sound Arch and bond villain-y)

Deltas were paired with Echos (Palantir calls them Deployment Strategists). The Echo works out which problem actually needs solving. The Delta writes the code that solves it. An ex-Palantir insider described the whole thing as a product strategy that looks like services from the outside.

The cleanest definition I've found is Palantir's own:

A normal engineer builds one capability for many customers. An FDE builds many capabilities for one customer.

So a real FDE does four things:

1. Writes production code
2. Inside a paying customer's environment
3. Sticks around after go-live
4. Feeds what they learn back into the core product

And is it new? Not one tiny wee bit. When SAP started out, its engineers were forward deployed, working on customers' own computers. Field engineers, implementation engineers and embedded consultants have been doing versions of this for decades.

Palantir gave it a cool name though….

2. Is the demand real?

Yes. it actually is real.

Bloomberry analysed 1,000 FDE job ads and found postings up 1,165% year on year in 2025, with a median base salary of $173,816. Indeed data reported by Business Insider had them up 729% year on year by April 2026, and Indeed India saw a nearly 19x jump by June. And the big players are putting serious money behind it: AWS has put $1bn into a new FDE organisation, and Google Cloud has committed $750m.

So that’s demand, what about supply?

Gartner's Mukul Saha told Channel Dive there are roughly 2,000 active FDEs out there.

Two thousand. Meanwhile Indeed was carrying over 5,000 FDE listings in April alone. Even allowing for duplicate ads and Gartner's maths being a bit squishy, that's a lot of chairs and not many bums.

And when demand massively outstrips supply, what do companies do?

They stretch the definition until more people fit inside it.

3. Luke Get’s DevOps déjà vu

Quick history lesson. DevOps was coined in 2009 as a set of practices: developers and ops working together to ship faster. A way of working. Then we turned it into a job title, and slapped it on anything with a server in it.

One DevOpsDays veteran said most "DevOps engineers" were Linux engineers who, if they were lucky, did a little bit of automation.

Sound familiar?

Bloomberry analysed 1,000 FDE job ads and found companies are using the title for three completely different jobs:

So 60% of the time, it's an FDE….. every time.

The other 40% is businesses either inflating titles or not actually knowing what FDE is. that doesn’t make for a great experience for an actual FDE looking for a new job.

Gartner said the same thing in fancier words: lots of providers now use "forward deployed" as a label for implementation, pro services, solutions engineering or AI consulting. Some thoughtfully. Others because it ‘sounds more strategic’.

The rebrand is tempting because the title recruits better. Engineers who'd never open an ad for a sales engineer or implementation consultant will open one that says FDE.

4. Is your role really an FDE role?

Your stakeholder says "we need an FDE". Before you write a single word of the job ad, run these at intake:

1. Who's the customer? A paying external customer, or our own sales and CS teams?
2. When does the job start and finish? Before the deal is signed, or after? Will they still be on the account three months after go-live?
3. How much of the week is writing code? And does that code go into the customer's production environment, or is it demos and POCs?
4. How many accounts at once? Two or three deep ones, or fifteen?
5. Who do they report to? Engineering or a dedicated FDE team, or Sales?
6. Is there a quota, commission or OTE?
7. What happens to the stuff they build? Does any of it get fed back into the core product?
8. How much travel? Be honest. They'll find out.

Then match the answers to the real job:

If it lands in rows two to four, push back. Kindly. With data.

Try this: "If we call it FDE, we'll attract people who expect to write production code for customers. When they find out it's demos, they'll drop out at final stage, and we'll have wasted three rounds. Let's call it what it is and pay for what it is."

Then track it. Tag every FDE candidate who withdraws and log the reason. If "role wasn't as described" keeps coming up, you've got a chart to take to your next hiring manager catch-up.

And for the record, there's nothing wrong with a Solutions Engineer. Great job. Loads of great SEs out there. Just call it one.

6. Is your candidate really an FDE?

The title inflation goes both ways. Now that "FDE" is the hot thing, plenty of LinkedIn profiles have quietly updated themselves too.

Here's what I'd ask in a first screen. None of these need you to be technical.

1. "Tell me about something you built that's running in a customer's production environment right now. Who looks after it today?" Real FDEs light up. They'll know the system, the customer, and who got the 2am call.
2. "What did the product team build because of something you learned on site?" This is the feedback loop. It's the bit that separates an FDE from a consultant.
3. "Roughly, how did your last month split between writing code, customer meetings and internal stuff?" Bloomberry's builder FDEs sit at 70-90% coding. Ten per cent coding is a different job.
4. "How many customers were you working with at once, and for how long?" A few, for months, is FDE. Fifteen, for weeks, is pre-sales.
5. "Talk me through your worst day on site." Go three levels deep. Who was in the room, what broke, what they did next. Lived detail is very hard to fake.
6. "A customer exec says, 'Why are we losing customers?' and that's your brief. Where do you start?" This is the Palantir-style scoping question. You're listening for questions back before solutions.

What to listen for:

One important caveat. Looking at 100 FDE LinkedIn profiles, Bloomberry found 22% of current FDEs came from solutions engineering or architecture. So a Solutions Engineer who codes daily and wants to go deeper can absolutely become a great FDE.

So skip the gatekeeping. Just make sure everyone, candidate and hiring manager, knows which job they're actually talking about.

TL;DR - Is Forward Deployed Engineering Bullshit?

No.

The role is real. It's old, it's well paid, and done properly it's genuinely hard. Palantir built a whole company on it.

But about 40% of the job ads? According to Bloomberry's data, yes. Bullshit.

And that bit's on us. We're the ones writing the ads, and we're the last line of defence before a great engineer wastes three rounds on a job that doesn't exist.

So next time a stakeholder asks, "Can we call it FDE? It'll get more applicants", ask them one question back:

"Cool. Will they write production code for a customer, and still be there three months after go-live?"

If the answer's no, you've got your answer.

And if you're a real FDE reading this, sorry. We did the same thing to DevOps. We'll probably do it to whatever comes next.

Well... that's issue Eighty Three! If you have any questions about it, or any feedback on this issue of The Data Driven Recruiter, grab me on LinkedIn for a chat.

I'll see you next week!