Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To maximize their value, forward deployed engineers (FDEs) should not be a separate services team. Integrating them directly into the product organization ensures faster, higher-fidelity customer feedback and context capture, which directly shapes the core product.

Related Insights

Embed engineers directly with customers to hear feedback and ship solutions, often on the same day. This radical structure eliminates layers of communication (Product Managers, Customer Success) and scales the 'founder energy' of talking to users and immediately building what they need.

Instead of a traditional product roadmap, give engineers ownership of a broad "problem space." This high-agency model pushes them to get "forward deployed" with customers, uncover real needs, and build solutions directly. This ensures product development is tied to actual pain points and fosters a strong sense of ownership.

Harvey's Forward Deployed Engineering team isn't just for building custom solutions. It's a strategic product discovery tool. By embedding engineers with large clients who have undefined GenAI needs, Harvey identifies and builds the next set of platform features, effectively using customer problems to pave its future roadmap.

Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.

The conventional software feedback loop is 'can I sell it?' Palantir's forward deployed engineers use a stronger loop: 'did it deliver the outcome?' This requires embedding obsessive, technical problem-solvers on the factory floor or in the foxhole to continuously solve backward and generalize learnings into the product.

Complex agentic products require hands-on help to deploy successfully. Gating Forward Deployed Engineers (FDEs) to only large customers leads to failed 'zombie deployments.' AI companies should view FDEs as an investment in customer success and word-of-mouth, even if it means initially spending a dollar to make a dollar.

Veeva structures its product teams using a "two in a box" model that pairs a customer-facing strategy leader with an internal product leader. This formalizes the integration of market feedback directly into the development lifecycle, with the strategy role acting as the "glue" across all customer-facing functions.

The best products are built when engineering, product, and design have overlapping responsibilities. This intentional blurring of roles and 'stepping on each other's toes in a good way' fosters holistic product thinking and avoids the fragmented execution common in siloed organizations.

Serval hires 'future founder' types as Forward Deployed Engineers (FDEs). Their primary function isn't just implementation but to replicate the early-stage founder motion: directly interacting with customers, identifying pain points, and channeling that feedback immediately into product improvements, thus scaling the founder-led feedback loop.

By embedding product teams directly within the research organization, Google creates a tight feedback loop. Instead of receiving models "over the wall," product and research teams co-develop them, aligning technical capabilities with customer needs from the start.