Forward Deployed Engineer: What It Is, Which Companies Need One, and How to Hire One in Spain

If you're researching the Forward Deployed Engineer role in Spain, you've probably already got the problem: a technically powerful product, customers who aren't getting full value from it, and a product team that can't be everywhere at once. Or maybe you're just curious.

The role has existed in the United States for years — Stripe, Databricks and Palantir have long had dedicated FDE teams. In Spain, there are currently 84 active listings on LinkedIn. A year ago there were likely none. That's a clear signal that the Spanish market is starting to demand these positions. The same pattern as the US, just with an 18–24 month lag.

This guide explains exactly what an FDE is, which companies need one, and why finding one in Spain is harder than it looks.

Why this role is emerging now

The Forward Deployed Engineer isn't a new role invented by Silicon Valley. It's the answer to a problem many tech companies have but can't quite name: customers buy complex platforms and can't extract value from them without real technical help. Not support help. Not a how-to guide. Actual engineering help — adapting the product to their specific problem.

When that problem was small, the product team absorbed it. When it scales, it needs a name and a dedicated person.

This has been around for years. Companies have always had engineering teams dedicated to their biggest, highest-paying clients.

What is a Forward Deployed Engineer

An FDE is an engineer who works at the intersection between their company's technical product and the customer's real-world environment. They don't sell. They don't do support. They're not a strategy consultant.

David Bonilla captured it well in a recent Bonilista: https://app.supermo.no/share/766888b38136dc26/594c54df8c

What an FDE does:

• Embeds in the customer's technical context to understand their systems, data, and real constraints — and genuinely understand their problem.
• Identifies how to integrate or adapt the product so it generates value in that specific environment.
• Builds custom solutions, automations or integrations when the standard offering isn't enough.
• Acts as the bridge between what the customer needs and what the product team can (or should) build.

What an FDE is not:

• An account manager who happens to be technical and gives demos.
• An implementation consultant who follows the playbook and nothing more.
• A product developer building features for the entire customer base.

The key difference lies in direction: an FDE doesn't work from inside the product outward. They work from inside the customer's problem inward toward the product. That shift in direction changes everything.

Gergely Orosz, author of The Pragmatic Engineer, has written about the challenges of filling a role that resembles a Solutions Architect more than a traditional developer.

Source: The Pragmatic Engineer, Gergely Orosz

Why the role is particularly relevant right now

One factor has sharply accelerated FDE demand over the last two years: AI.

Generative AI platforms and B2B SaaS products built on language models are powerful but opaque. A customer can buy an AI platform for document processing, workflow automation or data analysis — and still have no idea how to connect it to their stack, their data or their actual workflows.

The gap between "what the product can do" and "what the customer knows how to do with it" has never been wider.

Companies that bridge that gap systematically — with engineers deployed inside the customer's problem, not just with documentation and support — see dramatically higher retention and expansion rates*. The FDE is the structural answer to that gap.

The most frequently cited metrics in the sector are:

• 70% higher net revenue retention
• 3x faster time-to-value
• 40% reduction in support costs
• 2.5x more expansion revenue

These figures appear across several specialist posts on the role, but there's no traceable primary source. At Manfred we like verifiable data — so take these with a healthy dose of scepticism.

Which companies need a Forward Deployed Engineer

This isn't a profile for every company. There are clear signals that you've reached the point where you need one:

• Your product is technically powerful but real adoption is low. Customers buy it but don't use it fully. Churn arrives at the 6–12 month mark because they never saw the promised value — they simply couldn't get it out of the product on their own.
• Your Customer Success team constantly escalates technical complexity to product. If CS can't resolve customers' technical problems without pulling in a product engineer every time, you have the problem.
• Every implementation is different. If your customers have highly heterogeneous technical environments and the standard product never quite fits without customisation, you need someone who does that customisation from the customer's side.
• You're in a market where time-to-value is critical. If a customer takes more than two weeks to see real value with your product, every day of delay is churn risk.

Clear examples include Salesforce, SAP and Atlassian — products that require implementation by external consultancies. But the reality is there are many less prominent products and companies that work exactly the same way.

Why this profile is hard to find

The profile doesn't exist in the places you'd normally look. And when it does appear, it's usually described as something else. It's a relatively new role.

The ideal FDE has an unusual combination of skills: real technical depth (can write code and understand complex systems), communication ability with non-technical clients and stakeholders, and product judgment to know what's worth building and what isn't.

That profile doesn't come out of standard hiring channels. They're not scrolling LinkedIn Jobs. They're working — probably in a role that isn't called FDE but does exactly that. A lot of excellent people in consulting are doing this work right now.

There's also a naming problem: in Spain the role is not yet widely established as a category. Professionals who fit the profile don't self-identify with the term because they've never heard it. Companies searching for them call them "technical consultant", "solutions architect", "technical account manager" or simply "senior backend engineer who can also talk to clients."

The result: the best candidates for this role aren't where the companies that need them are looking.

That said, as home to Spain's largest technical community, Manfred can identify them.

How to find a Forward Deployed Engineer in Spain

With 84 active listings on LinkedIn Spain, the market is at a very early stage. That has two implications:

• First, there's no large pool of candidates with the title on their CV. You need to search by capability, not by label.
• Second, companies that move now have an advantage. This profile will become far more competitive in 18–24 months as the Spanish market normalises around the role.

Where these profiles actually are:

• Senior engineers with client-facing experience at product companies. Solutions architects, technical leads who've worked with enterprise clients, seniors from integration teams.
• High-level technical consultants who've operated in complex, heterogeneous environments and want more technical depth than consulting typically offers.
• Engineers from B2B SaaS companies who've been on the implementation side and know the problem from the inside.

None of these profiles are actively looking. That has always been Manfred's strength: the ability to reach professionals who are not job-hunting but would listen to the right opportunity, presented the right way.

At Manfred, we've been working with exactly these profiles for years. We know candidates before they're searching, we speak their language because we come from the same technical world, and we validate both technical and cultural fit before presenting them to you. For a role like the FDE — technical, cross-functional and hard to evaluate on paper — that prior context is the difference between presenting candidates who fit and presenting CVs with the right keywords.

If you're thinking about opening a Forward Deployed Engineer position in Spain and don't know where to start — what to look for, how to define the profile, or where to find real candidates — get in touch. We know the role, we know the people, and we know how to reach profiles that aren't in the visible market. Talk to us about this position.n en el mercado visible.Habla con nosotros sobre esta posición.

How to evaluate an FDE in the hiring process

Once you've found a candidate, the most common mistake is evaluating them like a product engineer or like a consultant. They're neither. What should you assess?

• Technical diagnostic ability in an unfamiliar context. Put a real technical problem from a hypothetical customer in front of them — with incomplete information. Don't look for them to solve the problem: look at how they decompose it, what questions they ask and how they prioritise.
• Ability to communicate technical complexity without losing the audience. Ask them to explain something technically complex to a non-technical person. If they can't, they have a structural problem with this role.
• Orientation toward customer outcomes, not technical elegance. An FDE who prioritises the perfect solution over the solution that works today for the customer hasn't grasped the role. Look for evidence of pragmatic technical decisions made with judgment. Ideally they understand this is the right approach for now to get a short-term result, and can manage the trade-offs that come with it.
• A track record of building in ambiguous contexts. Projects where the brief wasn't clear, requirements changed, and they had to improvise within the customer's constraints. Those contexts reveal whether the profile can handle the real pressure of the role.

Frequently asked questions

How much does a Forward Deployed Engineer earn in Spain?

The market is still forming. Reasonable ranges for 2026 sit between €55,000 and €85,000 gross per year for profiles with 4–8 years of experience, depending on technical level, the company, and whether the role has an international component. FDEs with demonstrable experience at reference companies can exceed that range with ease.

In practice, many candidates come from Solutions Architect backgrounds already earning around €70–75K. It's an expensive role because the supply is thin — and the people who exist are already well placed. From there, you'll need to calibrate your offer to the company and context.

As a data point: Karumi recently posted an FDE role at $100–150K (13 applications in one week). That's above the typical Spanish market rate, but they're looking for someone with proven experience in a specific type of company and unambiguously demonstrated skills in this role. In other words: within any market range, there will always be outliers hunting for the best, and the best gets paid accordingly.

Is it the same as a Solutions Architect or a Technical Account Manager?

There's overlap, but they're not the same. The Solutions Architect tends to operate in pre-sales — explaining, demonstrating, designing on paper. The Technical Account Manager manages the relationship but rarely writes code. The FDE does all three and executes them inside the customer's real technical environment. They're more of an engineer than the other two, and more customer-oriented than a product engineer.

Does it make sense to hire an FDE if my company has fewer than 50 customers?

It depends on the technical complexity of each implementation, not the number of customers. If each customer requires real integration, if there's a recurring technical adoption problem, or if churn comes from failure to perceive value — the size of your customer base isn't the relevant criterion. The right signal is: how many engineering hours are we putting into customer technical problems that aren't product features? If your business ends up adapting the solution for every customer, it may start to make sense to have an adaptable product core with a dedicated FDE for each implementation.

Why are there so few FDE roles in Spain when it's an established role in the US?

Because the company model that generates the most FDE demand — technically complex B2B SaaS with enterprise clients — is less developed in Spain than in the US. But it's growing. AI-native companies, vertical SaaS platforms and data platforms are the first demand clusters. In 12–24 months, the role will be far more common.

A role on the rise and in transformation

The Forward Deployed Engineer isn't a trend. It's the answer to a real problem that grows as technical products become more powerful and harder to adopt without engineering support. And AI makes it significantly easier to adapt to each customer's unique context.

Companies that understand this now have a clear advantage: the profile is scarce, the Spanish market is at an early stage, and the candidates who fit aren't looking at job boards.

If you have the problem and don't know where to start, Manfred can help. We know the role, we know the people, and we know how to find profiles that aren't in the visible market.

Talk to us about this position.