Team Perspectives

What is an FDE? On-site engineers deliver systems, FDEs deliver results

·4 min read

FDE stands for Forward Deployed Engineer: an engineer deployed to the front line. The role appeared at Palantir in the early 2010s, but it only became widely visible once AI companies started hiring FDEs.

We won't get into how the FDE role has changed since AI arrived. The role came into view alongside AI in the first place, so that question doesn't get us very far. What we want to look at is what an FDE actually does, how that differs from the on-site engineer most people are familiar with, and when a business needs one.

How Palantir uses the term

At Palantir, FDE refers to engineers who don't sit back at the office waiting for requirements, but go and work directly at the customer's site. Palantir has since gone as far as naming the AI agent in its Foundry platform AI FDE, which its documentation describes as:

"an interactive agent that operates Foundry for you through conversational commands"

According to the documentation, it works through data transformations and builds and maintains the ontology based on the conversation, then checks the results and corrects itself. To us, the fact that even an AI agent borrows the FDE name says a lot about what the role is at its core: understand the business first, then make the system work the way the business does.

How an FDE differs from an on-site engineer

In a sentence: an on-site engineer delivers a system (or a tool); an FDE delivers a result.

The real dividing line is who defines the problem.

Say a company tells you: "It takes us ten days every month to reconcile accounts receivable across our banks. We'd like your help automating it."

What an on-site engineer typically does

The client hands over the reconciliation rules, the fields, the system APIs and the requirements documents, and the engineer takes care of integration, development, testing and deployment. Success means the system meets the spec and works as intended.

What an FDE typically does

An FDE gets deep into how the finance staff actually do the work and digs into why it takes ten days. For example:

  • Which data arrives late, is missing, or can't be matched up?
  • Which reconciliation rules have never actually been written down?
  • Which exceptions need a human to make the call?
  • Which human decisions could be handed off to rules, AI or workflow automation?
  • Could the solution carry over to other banks, other ERPs, or even other clients?

What gets delivered in the end isn't just a reconciliation program. It's a reconciliation capability that can keep growing, covering exception handling, rules, data mapping and a process for human review.

An FDE still writes code, integrates APIs and solves deployment problems, but those are the means to a business result, not the whole job.

Interviews aren't enough: you have to be where the problem is

The way we work, people have to be directly involved where the problem actually happens. Interviews alone come nowhere near enough.

Here's an example. At a trading company, one of our engineers worked side by side with the cashier and sales team for three full weeks. Throughout those three weeks, they did the work while continually revising their understanding of the business and where it got stuck. In the end, it took them less than a week to put forward a plan that could improve overall efficiency by nearly 35%.

That plan didn't come out of a requirements document. It came out of those three weeks of real work.

Where ProCheck fits in

The FDE goes on site and gets the problem clearly defined. ProCheck handles managing and training the AI agents, which takes a great deal of work off people's plates. Things like cost management and model management are already built in.

Because so much is built in, ProCheck has hundreds of parameters, and realistically only trained professionals can use it to train an AI agent. Once the agent is trained, though, using it day to day doesn't take that kind of expertise: a business can simply treat the AI agent as another employee.

In other words, the expertise is concentrated in the rollout and training stage, and the FDE carries it. Everyday use stays at a level the business can handle on its own.

When does a business need an FDE?

From our perspective, the test is straightforward: if certain delays, whether you sense them or see them in the numbers, are seriously dragging down operating efficiency, and fixing them would save significant cost or help win revenue, it's worth considering.

One very common sign is a manager thinking, "This looks simple. Why is it taking so long?"

When that thought comes up, it may be time to bring in one of our consultants, or to have a conversation with us first. Often an hour or two is enough to tell whether you need an FDE.

Closing thoughts

Engineers' logical rigor has always been a valuable strength. What an FDE does is put that rigor to work not just on getting the spec right, but directly on helping the business grow.

To learn how we embed with clients and roll out solutions, see our services.

Need Professional Assistance?

Our team are senior engineers and former executives with 20+ years in commercial product development — from apps serving hundreds of millions of users to B2B SaaS platforms serving tens of thousands of merchants. In recent years the focus has been enterprise AI adoption, from mapping the opportunity through to tuning what is live. Whether that means:

  • Mapping AI opportunities and sequencing them
  • Preparing data flows and integrating existing systems
  • Building forecasting and optimization models
  • Monitoring and tuning after go-live
  • Test strategy and process review
  • Building and adopting test automation

We can provide professional advice and concrete solutions for teams of different scales and types. If you're facing similar challenges, feel free tocontact our consulting team.