Forward Deployed Engineer: what it is and why companies are looking for it

A recruiter recently asked me whether what I do is the same as consulting. I told them not exactly, and that the difference can matter when putting teams together or deciding who to work with on a critical project. I've spent 12 years building software for SMBs and companies like Santander or NTT DATA, and in most of those projects my role wasn't delivering a report or a recommendation: it was getting into the client's problem, designing the solution together with the team, and seeing it through until it was running in production.

That is, in a nutshell, the job of a Forward Deployed Engineer (FDE). In this article I share how I understand it from my own experience.

What a Forward Deployed Engineer is

A Forward Deployed Engineer is an engineer who deploys directly into the client's context —sometimes literally in their offices, sometimes in constant meetings with their team— to understand a specific business problem and build the solution end to end: from initial discovery to the system running in production.

It's an execution role with business judgment rather than an advisory one. The FDE doesn't just write code that someone else hands them in a ticket: they take part in defining what needs to be built and why, and they see it through until it works.

In my case, that meant going through very different stages within the same project: sitting down with end users to understand how they actually work (not how the manual says they work), designing the architecture together with the team to support those needs, writing the code, and seeing it through to the move to production. To me, that complete journey is what characterizes the profile.

How it differs from other similar roles

There's legitimate confusion here, because several roles overlap in appearance. It's worth separating them.

Forward Deployed Engineer vs. Consultant

A consultant typically analyzes, recommends, and delivers a plan or a document. Their value lies in diagnosis and strategy. The FDE also does that work of understanding the problem, but doesn't stop there: they build the solution and take responsibility for making it work in production. The difference is between "I tell you what to do" and "we do it together until it's up and running."

Forward Deployed Engineer vs. Product Developer

A product developer usually works on a roadmap defined by others (product managers, internal stakeholders) and builds features intended for a broad market or a general user base. The FDE, on the other hand, works closely tied to a client or a specific problem, often with requirements that aren't standardized or documented beforehand. Their initial task involves as much discovery as development.

Forward Deployed Engineer vs. Solutions Engineer

The solutions engineer tends to be closer to the sales process: they help demonstrate that a product can solve the client's problem, run proofs of concept, prepare demos. It's a key role, but it generally ends when the deal is closed or the prototype is delivered. The FDE comes in afterward (or in parallel) and stays with the actual implementation, the integration with existing systems, and the support until the project is genuinely running in production.

What skills this profile combines

After 12 years doing this kind of work, what I find hard to come by in an FDE isn't any single technical skill, but the combination of several that rarely coexist in the same person:

• Business: understanding why the problem exists, what impact it has on the client's operations, and what solution is viable within their real constraints (time, budget, people).
• Architecture: designing systems that not only solve the specific case but can be sustained and grow without becoming a problem in six months.
• Code: the ability to build the solution hands-on, not just describe it. This includes writing quality code, but also knowing when a simple approach is better than a sophisticated one.
• Communication: translating between business language and technical language, every day, with different stakeholders: end users, managers, other development teams.

None of these skills alone defines the FDE. What defines the role is that all four are needed simultaneously, in the same project, often in the same week.

When it can make sense to add a profile like this

Not every project needs a Forward Deployed Engineer. It can make sense to consider one when:

• The client's problem isn't well defined yet and requires serious discovery before writing a single line of code.
• The project involves integration with complex existing systems (banking, industrial, corporate) where design mistakes are costly.
• The company needs someone who takes responsibility for the final outcome —production up and running— and not just a partial delivery.
• There's a gap between what the business says it needs and what's technically feasible, and someone is needed who can move between both worlds without wasting time on constant translation.

In my experience working with organizations of different sizes —from SMBs to companies like Santander or NTT DATA— this type of profile contributes most in projects where the cost of an initial misunderstanding is high, and where there's no room for the solution to end up stuck halfway between design and actual implementation.

What I took away

• The value of this role is in accompanying the problem end to end, not in a single stage.
• Listening to end users before designing avoids building on assumptions.
• No single technical skill is enough: business, architecture, code, and communication are used at the same time.
• A simple approach that works in production is usually better than a sophisticated one stuck halfway.

If you're considering adding a profile like this to your team, or you'd like to exchange experiences on working this way, I'd be glad to talk: you can write to me on LinkedIn. My background is at estebanburgos.com.ar/about-me.