0%
Forward Deployed Engineering
The Role
Discovery and Scoping
Customer Data and Systems
Building in the Field
Field Feedback into Product
Forward deployed engineers see the product in use more closely than anyone else in the company. They watch customers struggle with a missing feature, write the same workaround for the third customer in a row and learn which parts of the product are trusted and which are avoided. That knowledge is one of the most valuable things an FDE team produces, but only if it reaches the people who decide what the product becomes. This lesson covers why field feedback matters, how to capture it, how to turn it into clear product requests, how to work with product and engineering teams and how to close the loop with customers.
Two kinds of output
An FDE team produces two things. The first is working deployments for customers, which earn revenue and trust. The second is learning about what customers need, which shapes the product. Teams that only produce deployments become expensive custom services, with each deployment as hard as the last. Teams that also feed learning back make each deployment easier, because the product steadily absorbs what used to be custom work.
Why the field sees what others miss
Product managers learn from interviews, surveys, usage data and sales calls. These are useful but filtered: customers describe what they think they need, and usage data shows what people do, not why. FDEs work inside the customer environment for weeks, see real data and real workflows and hit the same problems the customer hits. They see the gap between how the product was designed to be used and how it is actually used.
The cost of custom work
Every workaround an FDE builds has a cost: time to build it, time to maintain it, risk when the product changes and difficulty handing it over. When the same workaround appears in many deployments, the total cost grows quickly, and every new FDE has to learn it again. Turning repeated custom work into product features is one of the highest value things an FDE team can do for the company.
Custom work as a signal
Custom work is not a failure. It is often the fastest way to make a deployment succeed, and it shows where the product falls short. The useful question is not whether custom work happened, but whether anyone noticed patterns across deployments and acted on them. A connector written for one customer is a deployment detail; the same connector written for five customers is a product gap.
Feedback the product team cannot get elsewhere
Some knowledge only comes from the field: which configuration options nobody understands, which error messages lead customers to call support, which integrations fail with real enterprise systems, which data quality problems are common in an industry and which promised features matter in practice. Product teams value this most when it is specific and backed by evidence from several customers.
When feedback is lost
Feedback is lost in predictable ways. It stays in an FDE head or a private notes file. It is shared in a chat message and scrolls away. It is described vaguely, such as customers want better reporting, and nobody can act on it. It reaches a product manager who does not know which deployments it came from or how important it is. Each of these failures is fixable with simple habits and a shared process.
Feedback and the FDE reputation
FDEs who bring clear, well evidenced feedback earn influence with product teams. Their requests are taken seriously, they are invited into planning and they shape what gets built. FDEs who send a stream of vague complaints, or who push every customer request as urgent, lose that influence quickly. The quality of feedback matters more than the quantity.
Who owns the product
The FDE does not own the product roadmap. Product managers weigh field feedback against many other inputs: strategy, the wider market, sales pipeline, technical debt and cost. A request that is right for the deployments an FDE sees may still be the wrong priority for the company. The FDE job is to make the case clearly and honestly, then accept and explain the decision, while keeping evidence flowing.
Feedback beyond features
Field feedback is not only requests for new features. It includes bugs that only appear with real enterprise data, documentation that misleads customers, defaults that are wrong for most deployments, pricing or packaging that blocks adoption and performance limits reached at real scale. Some of the most valuable feedback is about removing friction rather than adding capability, such as an installation step that takes a day and could take ten minutes.
Feedback about what works
Positive feedback matters too. When a feature works well across customers, saves hours or wins a deal, tell the product team. It shows them what to protect when they redesign, where to invest further and which stories to tell new customers. Product teams often hear only about problems, so evidence of success helps them make balanced decisions.
Patterns by industry and size
Some gaps appear only in certain industries or sizes of customer. Banks need detailed audit trails, hospitals need specific data protections and large enterprises need delegated administration across many teams. Recording the industry, size and region of each deployment with its feedback lets product teams see whether a gap is universal or belongs to a segment they may or may not want to serve.
Feedback as early warning
The field often notices problems before they appear in metrics: a competitor that customers keep mentioning, a new regulation that will change requirements, a shift in how customers want to buy or a quality issue that is getting worse slowly. Sharing these early signals, even when the evidence is still thin, can give the company months of extra time to respond. Label them clearly as early signals so they are weighed correctly.
Making it part of the job
Feeding back should be an expected part of FDE work, not an extra done in spare time. Leaders can make it so by setting aside time for it, reviewing feedback in regular meetings, recognising FDEs whose feedback led to product changes and including it in performance reviews. When feedback is part of the job, the habit survives busy deployments.
Feedback and the customer relationship
Customers notice when their feedback leads somewhere. A customer whose request appears in the product, or who is told clearly why it will not, feels like a partner rather than a buyer. That feeling supports renewals, references and expansion. Feedback that disappears without an answer slowly teaches customers that raising problems is pointless, and they stop telling you what is wrong, which is far worse than hearing complaints.
A simple test
At the end of each deployment, ask: what did we learn here that the product team should know, and have we told them? If the answer is nothing, either the deployment was unusually smooth or the learning was not captured.
If you cannot answer, spend an hour with the deployment notes before moving to the next customer.
Then write down the three most important lessons, share them with the product team and link each one to the deployment where it was learned.
Treat field learning as an output of every deployment, look for custom work that repeats across customers and count its cost. Capture what only the field sees, avoid the common ways feedback is lost and build influence with clear, evidenced requests rather than volume. Remember that product teams own the roadmap and weigh feedback against other inputs.