What is a forward deployed engineer, and does your business need one?

The short answer

A forward deployed engineer, or FDE, is an engineer placed inside the customer's business instead of the vendor's office. The job is to build on the customer's own data and systems until the solution is live and the team can run it. The output is a working system, not a recommendation.

The word "forward" is borrowed from the military, where forward deployed units are stationed where the action is instead of at headquarters. The engineering version means the same thing: the person who can actually build the fix is placed where the problem is.

Where the role came from

Palantir popularised the title in the 2010s. Its software was powerful and nobody could use it out of the box, so it sent engineers to sit inside customers and make it work on their data. That turned out to be the product. The same pattern now appears wherever a technology is capable but hard to land: OpenAI, Anthropic, Databricks and Salesforce all employ forward deployed engineers, and in August 2026 AWS confirmed at its Johannesburg Summit that its billion-dollar forward deployed engineering programme will be offered in South Africa.

The reason is simple. AI and automation tools have outrun most businesses' ability to adopt them. A licence does not change a process. Someone has to go in, understand how the work really happens, and build the thing that makes it happen differently.

What a forward deployed engineer actually does

Day to day, the work looks less like a software project and more like joining the team for a while.

• Maps the process as it runs, by sitting with the people who run it, not by reading the org chart.
• Puts a number on the friction: hours lost, errors caught late, revenue sitting in a queue.
• Decides what to build against what to configure. Often the right answer is a tool the business already pays for and nobody set up.
• Builds on real data and real edge cases, because the exceptions are where manual processes hide.
• Shows working software every fortnight, so a misunderstanding surfaces in week four, not week twelve.
• Hands over a system the team owns: training, documentation, and credentials in the client's name.

If that reads like how we have always worked, that is because it is. We did not adopt the method when the title became fashionable. We just stopped having to explain it.

FDE vs consultant vs solutions engineer vs contractor

The titles get used loosely. The differences matter when you are deciding whom to pay.

Role	Works where	Leaves behind	Watch out for
Management consultant	Your boardroom, then their office	A recommendation	Nothing gets implemented
Solutions engineer	The sales process	A demo or proof of concept	Disappears once the deal closes
Contractor	Your desk, your instructions	Hours worked	Knowledge leaves when they do
Outsourced dev shop	Their office, from your spec	Software matching the spec	The spec was wrong
Forward deployed engineer	Inside your team, on your systems	A live system your team runs	Scope creep, unless it is fixed up front

Does your business need one? Six questions

Answer yes to three or more and the forward deployed model is probably the cheapest way to fix the problem. Fewer than three, and a smaller fix or a simple configuration job will do.

1. Does someone in the business re-type information that already exists in another system?
2. Have you bought software in the last two years that nobody fully adopted?
3. Have you received a consultant's report that is still a report?
4. Is your team capable of running a better system but too stretched to build it?
5. Are staff already using AI tools informally, with no policy and no production use case?
6. Has a previous development project delivered what was specified rather than what was needed?

How to get one in South Africa

You have three routes, and the first two are harder than they sound.

Through a vendor programme. AWS, Salesforce and Palantir delivery partners are standing up forward deployed teams locally. These are built for enterprise accounts and normally come attached to a platform commitment. If you are a bank or a miner, this is probably your route. If you have 80 staff and a Sage licence, it is not.

Hire one. The local adverts for forward deployed engineers come from Salesforce, PwC and Palantir partners, which tells you who you are competing with for the same person. You would also be hiring for a problem that takes weeks, not years.

Engage a firm that works this way. That is what we built Go Implement's forward deployed engineering service to be: the same way of working, for businesses with 10 to 1,000 people, on a fixed scope or a day rate in rands, with everything built in accounts you own.

Three things to ask before you sign with anyone

• "What do we own at the end?" The answer should be everything: code, accounts, credentials, documentation. If it is not, you are renting.
• "When do we first see working software?" If the answer is "at the end", the risk is all yours.
• "What happens if the process turns out not to be worth automating?" A good answer is "we tell you in week one and stop". A bad answer is a phase two.

This article describes how the role works in practice, drawn from implementation engagements. Vendor programme details are as announced publicly at the date of writing and may change.

Common questions

Related reading

• Forward deployed engineering: how we deploy
• How we work: discover, design, implement, embed
• AI adoption vs AI implementation: which do you need first?