Get your free personalized podcast brief

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

Shiva Rajaraman says Beast Industries embeds 'four deployed engineers' inside studio and marketing functions. They sit with the people they support, prototype fixes quickly, and because prototyping is cheap, try ten solutions and discard the ones that fail. He calls the motion liberating and worth copying.

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.

Unlike companies viewing field teams as a cost center, Peregrine considers its 'Forward Deployed' strategists its core R&D engine. 'Hacky,' unscalable solutions they build on-site to solve immediate customer problems provide the best signal for what the core platform needs, creating a rapid, customer-driven prototyping loop.

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.

Rob Ferguson says features are far too easy to copy, so management must restructure teams to engage customers directly. He warns against sitting in the design pantheon and says the durable thing is the relationship on the other side, even with seasonal businesses. Forward-deployed teams are the management response.

To ensure platform R&D directly serves customer needs, Skydio uses 'strikes.' Core platform engineers temporarily embed with a specific vertical product team for months at a time. They co-locate and work exclusively on that team's goal before returning to the platform, which prevents silos and accelerates feature delivery.

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.

Stripe's Experimental Projects Team discovered that embedding its members directly within existing product and infrastructure teams leads to higher success rates. These "embedded projects" are more likely to reach escape velocity and be successfully adopted by the business, contrasting with the common model of an isolated R&D or innovation lab.

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.

To overcome high AI pilot failure rates, companies like Pace use "forward deployed engineers" (FDEs). These founder-type individuals work onsite, deeply understand customer problems, and do whatever it takes—from prompt tuning to data cleaning—to ensure successful production deployment.

Forward-deployed engineers should serve internal teams, not just clients | RiffOn