0%
Forward Deployed Engineering
Discovery and Scoping
Customer Data and Systems
Building in the Field
Running Deployments
FDE Compared with Neighbouring Roles
Forward deployed engineering sits among several roles that also combine technical skill with customer contact. Job titles overlap and companies use them differently, so it helps to understand what each role actually does. This lesson compares the FDE role with solutions and sales engineering, consulting, product and platform engineering, and customer success and support. The first section starts with the roles most often confused with FDE work.
What a sales engineer does
A sales engineer, sometimes called a presales engineer, supports the sales team during the buying process. They run demos, answer technical questions, complete security questionnaires and sometimes build small proofs of concept. Their main goal is to help the customer decide to buy. Once the contract is signed, their involvement usually drops, and other teams take over the deployment.
What a solutions engineer does
Solutions engineer is a broader title that varies a lot between companies. At some, it means the same as sales engineer. At others, solutions engineers design how the product will fit into a customer architecture, write integration guides and advise on best practices both before and after the sale. They usually write less production code than an FDE, focusing instead on design and guidance.
The key difference is ownership after the sale
The clearest difference between these roles and the FDE is ownership after the sale. Sales and solutions engineers help customers decide and plan. FDEs make the deployment work and stay accountable until the customer gets value. An FDE may join a deal before it closes, but their real work begins when the customer starts using the product on their own data.
The amount of production code
Sales engineers write demo code and small prototypes that rarely run in production. Solutions engineers may write reference implementations and scripts. FDEs write production code that customers depend on every day: pipelines, services, integrations and applications. This difference shows up in hiring, where FDE loops include serious coding rounds and sales engineering loops usually focus on demos and communication.
Time horizon
Sales engineers work on a time horizon of weeks, tied to the sales cycle. Solutions engineers may stay engaged for months but in an advisory role. FDEs often work with one customer for months or longer, through discovery, building, launch and handover. The longer horizon means FDEs live with the consequences of their decisions, which encourages careful engineering.
How they work together
In many companies, these roles work as a team. The sales engineer helps win the deal and shares what they learned about the customer. The solutions engineer may design the target architecture. The FDE then builds the deployment. Good handoffs between them save weeks, while poor ones force the FDE to repeat discovery that the sales team already did.
When a sales engineer acts like an FDE
At smaller companies, one person may do both jobs: helping win the deal and then building the deployment. This can work well, because there is no handoff and the customer deals with one technical contact throughout. The risk is that sales pressure pulls the person away from deployments, leaving customers without the engineering support they were promised.
Incentives differ
Sales engineers are often paid partly on commission tied to closed deals. FDEs are usually paid like engineers, sometimes with bonuses tied to customer outcomes. These incentives shape behaviour. A sales engineer may be tempted to promise features to close a deal, while an FDE has a stronger reason to set realistic expectations, since they will have to deliver.
The demo versus the deployment
A sales demo shows what the product can do under ideal conditions, often with clean sample data. A deployment shows what it does under real conditions, with messy data, strict security rules and real users. FDEs often inherit expectations set during a demo, so they need to understand what was shown and gently reset expectations where reality differs.
Reading a deal history
When an FDE joins a new customer, reading the deal history is one of the first tasks. Notes from the sales team show what the customer was promised, which competitors they considered and who championed the purchase. This history explains a lot about expectations and politics. FDEs who skip it often discover these things later, at a worse time.
Shared skills
Sales engineers, solutions engineers and FDEs share several skills: understanding the product deeply, explaining technical ideas clearly, handling objections and reading what a customer really needs. Many people move between these roles during their careers. A sales engineer who wants to write more code may move into FDE work, while an FDE who enjoys the earlier stages may move into solutions architecture.
Which role suits which person
People who enjoy fast cycles, persuasion and variety across many prospects often prefer sales engineering. People who enjoy architecture and advice may prefer solutions roles. People who want to build and own real systems for a few customers usually prefer FDE work. Knowing your preference helps you choose roles and read job descriptions accurately.
Reading job descriptions carefully
Because titles overlap, job descriptions are the best guide. Look for clues about ownership after the sale, the amount of production code, the coding bar in the interview and how success is measured. A role called solutions engineer that mentions building data pipelines and owning deployments may really be an FDE role, while a role called FDE focused on demos may not be.
The proof of concept
Many deals include a proof of concept, a short trial where the vendor shows the product working on a sample of customer data. Sales engineers often run these, sometimes with FDE help. A proof of concept that is built carefully can become the foundation of the real deployment. One built quickly with shortcuts often has to be thrown away, which surprises customers who thought the work was nearly done.
Security questionnaires and reviews
Sales engineers often complete the security questionnaire during the deal: long lists of questions about encryption, access control, data residency and incident response. The answers become commitments. FDEs should read them, because the deployment must honour every answer given. A questionnaire that promised data never leaves a region shapes the whole architecture, even if nobody mentions it at kickoff.
Promises made in good faith
Most overpromising is not dishonest. A sales engineer may describe what the product does in general, and the customer hears a promise about their specific case. FDEs who find a gap between expectation and reality should treat it calmly, explain what is possible, offer an alternative and agree a plan. Blaming the sales team in front of the customer damages trust in the whole vendor.
Joining before the contract
Some companies bring FDEs into the late stages of a deal, especially for large or complex customers. The FDE can check that the use case is feasible, meet the people they will work with and shape the plan. This early involvement reduces surprises later. The FDE should be careful, though, to describe realistic timelines rather than the most optimistic ones.
Feedback to the sales team
FDEs see which promises turn out hard to deliver and which use cases succeed. Sharing this with the sales team improves future deals. A short note such as customers in this industry always need a connector to the same system, so mention it early, saves the next FDE weeks and helps sales set better expectations from the first call.
Metrics for each role
Sales engineers are usually measured on deals won, win rate and the size of deals they support. FDEs are measured on time to value, adoption, customer satisfaction and renewals. Solutions engineers sit somewhere in between. These metrics explain why each role focuses where it does, and why healthy companies connect them so that winning a deal and delivering it are treated as one goal.
A short example
Consider a logistics company buying an analytics platform. The sales engineer runs a demo on sample shipment data and promises daily reports. The FDE joins after signing, reads the notes and discovers the customer expected reports every hour. Rather than arguing, the FDE checks the data feeds, finds that hourly is possible for two of three sources and agrees a phased plan with the sponsor.
Sales and solutions engineers help customers decide and design, with demo code and guidance over weeks. FDEs write production code, own the deployment for months and stay accountable for value. The roles often work as a team, so a clean handoff and a careful read of the deal history save a great deal of time.