When an enterprise AI program stalls, the instinct is to add people. And for the past few years, the person everyone wanted was a forward deployed engineer. That’s someone who sits inside the business, learns how it works, and writes whatever code it takes to get AI into production. The role works. The problem is that almost nobody can hire enough of them.
That's the contradiction at the center of forward deployed engineering. The model proves that embedded expertise is what gets AI over the line, and it also shows how hard that expertise is to staff, keep, and scale. Companies that try to build an internal FDE bench usually find they're competing for the same small pool of people as the AI companies themselves.
So the question has shifted. It's no longer whether you need what FDEs provide. It's whether you need to employ them to get it. Have I got your attention now? Good. Because I want to help you get what you need without the headache. So keep reading.
What does a forward deployed engineer do?
A forward deployed engineer, or FDE, is a software engineer who works directly inside a customer's environment to turn a product into a working solution for that customer. FDEs combine engineering, consulting, and product skills. They learn the customer's workflows and legacy systems, build the integrations and data pipelines a deployment needs, and adapt the product to the customer's rules. See how that fits the build vs. buy decision.
The role is a bridge between the product team and the business that uses it. Product teams build for many customers at once. An FDE builds for one, closing the distance between what the product does out of the box and what the customer needs in production. In high-stakes domains, where integration is complex and every deployment looks different, that bridge is often the difference between a pilot and a live system.
What skills does a forward deployed engineer need?
A forward deployed engineer needs three kinds of skill at once: engineering depth, the ability to work with business owners, and fast domain learning. Most job descriptions for the role reflect that mix. For what to look for in a partner with those skills, see how enterprises evaluate AI solution providers.
- On the engineering side, FDEs write production code, build integrations with systems of record, design data pipelines, and debug problems in environments they didn't design.
- On the customer side, they run discovery with business teams, translate vague requirements into working software, and explain trade-offs to people who aren't technical.
- On the domain side, they pick up how an insurer prices risk or how a lender monitors covenants quickly enough to make good decisions in the first weeks of a deployment.
That combination is what makes the role so effective, and it's also why it's so hard to fill. Strong engineers who enjoy customer work are uncommon. Strong engineers who enjoy customer work and learn new industries quickly are rarer still. And they're often the first people to be recruited away.
Why did forward deployed engineering become central to enterprise AI?
Because early AI products couldn't adapt to enterprise environments on their own, so people had to do the adapting. Models were capable, but they didn't understand a company's data, terminology, or approval chains. Someone had to translate between the two, and that someone was usually an engineer embedded on site. For what successful deployments look like now, see our guide to moving from AI pilots to production impact.
Forward deployed engineering was a natural fit when products needed heavy customization, data integration was manual, and value depended on deep context about one business. It also suited a market with a few large deals, where the cost of embedding engineers in each account could be absorbed by the size of the contract.
The frontier model providers noticed. As they moved into the enterprise, many began hiring forward deployed engineers of their own to get customers into production. That's one reason searches for the role have climbed so sharply, and it's a signal of where the bottleneck sits. The constraint on enterprise AI was never only the model. It was the work of fitting the model to the business.
Why can't most enterprises hire their way to forward deployed engineering?
Because the people who can do the job are scarce, expensive, and in demand from the companies selling AI. A good forward deployed engineer needs strong engineering skills, enough consulting ability to work with business owners, and enough domain knowledge to understand what the business actually needs. That combination is rare in any one person. See the hidden cost of building AI for production.
Enterprises that try to build an internal bench run into three problems:
- Recruiting. They compete with AI providers and well-funded startups for the same candidates, often with less interesting work to offer.
- Retention. Engineers who've learned to deploy AI inside one business are highly marketable. When they leave, the knowledge of how systems were built goes with them.
- Coverage. Even a strong team of four or five can only support a handful of use cases at once, which caps how far the AI program can grow.
The result is a familiar pattern. The first use case ships because a talented person carried it. The second takes nearly as long, because most of the first one lived in that person's head. By the third, the team is maintaining what it already built instead of delivering anything new. We've written about how that maintenance load consumes the business case in the hidden cost of AI in production when you build.
Why does the FDE model struggle to scale?
Because it puts the hardest part of every deployment in people rather than in the system, so each new customer or use case starts close to zero. Our breakdown of why enterprise AI adoption fails traces the same pattern. That structure creates three limits.
- The first limitation is complexity. FDEs handle variation in workflows well, but AI adds variation in data, models, and governance on top. Managing all of that by hand across many deployments doesn't hold up.
- The second limitation is slower learning. AI systems improve through feedback, and when a human intermediary sits between the product and the business context, those loops slow down.
- The third limitation is blurred product boundaries. When engineers embed deeply in each account, every deployment risks becoming a one-off build, and the lessons from one rarely transfer to the next.
The myth of reusable AI shows up here too. Teams expect the second project to reuse the first, but when the integration logic and business rules sit in custom code written by one engineer, very little carries over.
How does an applied AI lab deliver what FDEs provide?
An applied AI lab keeps the embedded expertise and moves the repeatable work into a platform, so each deployment builds on the last instead of starting again. The lab's experts still learn each customer's problem and domain before building anything. What changes is where the result lives. That platform side is covered in our guide to the managed AI delivery platform.
Unframe described the category in Introducing the Applied AI Lab: frontier labs advance capability, applied labs put it to work for a specific business, and an upgraded workforce knows how to use both. In that model, the lab plays the role an internal FDE team would play, without the enterprise having to recruit, retain, and scale that team itself.
The platform is what makes the difference. Unframe's Knowledge Fabric captures business context, including data sources, taxonomies, and operational metadata, in a shared layer that every solution draws on. Reusable AI building blocks carry the engineering for extraction, search, reasoning, and routing. The work an FDE would once have written as custom code becomes configuration on shared components, which is why it carries forward.
As our CEO Shay Levi put it, "The next era of enterprise AI won't depend on forward deployment engineers to bridge context. It will depend on platforms that understand it intrinsically."
What does forward deployed engineering as a service look like in practice?
It looks like a dedicated team that works inside your business, ships on a shared platform, and stays accountable for the result in production. Many enterprises now search for exactly this, asking which firms offer forward deployed engineering models or FDE as a service, because they want the outcome without the hiring problem. Before signing with one, review 5 questions to ask before signing for managed AI services.
The difference shows up over time. With an internal FDE bench, the tenth use case costs about as much effort as the first. With an applied AI lab, each use case leaves behind data connections, governance, and components the next one reuses.
The lab builds review steps into each workflow, so the people who own a decision still approve it. That design is covered in why human-in-the-loop verification is non-negotiable for enterprise AI.
Should you hire forward deployed engineers or partner with an applied AI lab?
Hire forward deployed engineers when AI is your product and you need that capability in-house for years. Partner with an applied AI lab when you need AI working across many business processes and can't staff a team large enough to cover them. To limit the risk either way, see how to de-risk enterprise AI adoption with no upfront cost.
The right question for leaders is no longer whether a vendor offers FDEs. It's why the system needs them. If a solution depends on deep human embedding just to function, it isn't ready to scale. If the embedded expertise produces reusable assets that make every later deployment faster, it is.
For teams weighing the broader trade-off, our guide to custom AI development without a build team walks through when building in-house still makes sense.
How does Unframe approach forward deployed engineering?
We bring the embedded expertise and keep the result on a platform you can build on. Unframe's AI experts learn your domain and your problem, then deliver on the Unframe platform in your cloud, on-premises, or as fully managed SaaS, with your data staying in your environment. See how the Unframe platform works.
You can work with us through managed delivery, build on the platform with our team behind you, or start with advisory work.
A focused AI workshop is a practical way to pick the first use case. If you're ready to get the outcome FDEs promise without building the team, book a meeting.
What else do teams ask about forward deployed engineer?
What does FDE stand for?
FDE stands for forward deployed engineer. An FDE is a software engineer who works inside a customer's environment to turn a product into a working solution for that customer.
What does a forward deployed engineer do?
A forward deployed engineer learns a customer's workflows and systems, builds the integrations and data pipelines a deployment needs, and adapts the product to the customer's rules so it runs in production.
Why is it hard to hire forward deployed engineers?
The role needs engineering, consulting, and domain skills in one person. Enterprises compete with AI providers for a small pool of candidates, and retaining them is difficult once they've built valuable experience.
What is the alternative to hiring forward deployed engineers?
An applied AI lab provides the same embedded expertise as a service and delivers on a shared platform, so each deployment reuses what earlier ones built instead of starting from scratch.




