I’ve been trying to figure out what exactly a Forward Deployed Engineer is, and it’s made me feel a little dense.
I got interested because the role is growing fast. Indeed data reported by Business Insider showed FDE job postings rising about 729% year over year by April 2026. Accenture, Deloitte and other major consulting firms are hiring for them too.
So I wanted to understand what all the fuss was about.
At its simplest, an FDE is an engineer who works directly with a customer to understand a business problem, build a solution on a technology platform, and iterate with users until it works in the real world.
My immediate reaction:
Isn’t this what technology consultants already do?
Consulting firms already have architects, engineers and implementation consultants who understand requirements, build solutions and help clients adopt them.
Then I came across Kevin Bai’s FDE 101 talk on youtube. Kevin worked at Palantir, built Rippling’s FDE function, and is now at Anthropic.
His definition:
“A customer-facing software engineer.”
That helped.
But where do you find someone who can understand the business problem, architect the solution, write production-grade software, test with users, iterate and help with adoption?
Ideally, an FDE crosses those boundaries.
In practice, it isn’t always one person.
Accenture, for example, describes FDEs working alongside engineers, domain experts and Deployment Strategists. So FDE can also be a team capability.
And that’s where the distinction became clearer to me:
Engineering gets pulled much closer to the customer, the business problem and the outcome.
Instead of:
Business gathers requirements → architect designs → engineer builds
those boundaries blur.
There is one other important requirement. FDEs build on top of a platform using reusable components rather than building everything from scratch.
But that itself isn’t new. SAP, ServiceNow and other platform consultants have done versions of this for years.
So why the sudden interest?
Kevin’s hypothesis is that AI has made sophisticated, customizable software much faster to build. But customers often don’t know what to build or how to operationalize it.
Someone has to bridge the gap between what technology can do and what the business needs.
My current understanding:
FDE is a customer-facing engineering capability, sitting in one person or a small team, that works directly with the client to understand the problem, build a solution, test it, iterate it and help operationalize it.
And the vendor isn’t really selling just a product or a service.
It’s selling a solution that combines product, services and engineering capability embedded with the client team.
For consulting firms, the interesting question is not whether you should start calling your engineers FDEs. It’s whether the way technology consulting is delivered is beginning to change.
What’s your understanding of a FDE? And if you are one, please chime in.
—
Ready to add $100k-$500k revenue to your consulting business in 12 months or less without burning out? Schedule a call and let me show you how.
