← back
How Forward Deployed Engineering is done at Kepler — Vinoo Ganesh
Takeaway
Embed engineers in customer workflows to discover the real problem and feed concrete solutions back into product strategy.
Summary
- Forward-deployed engineering is framed as an extension of product discovery, turning customer work into generalizable product improvements.
- Palantir's Project Frontline rotated software engineers into deployments; an isolated storage design failed when real bank data triggered millions of time buckets.
- A requested 47-page dashboard specification ultimately became a four-hour Slack-alert solution after observing what dispatchers actually needed.
- FDEs should ask what users want to accomplish, what happens afterward, and how the problem is currently solved, then ship small solutions that build trust.
forward-deployed-engineeringproduct-strategycustomer-discovery
Original description
A shipping and dispatch customer wanted alerts, a massive BI tool, and a dev environment. What they actually needed Monday morning was one Slack message, so that is what got shipped first, and the real thing followed. Vinoo Ganesh spent seven years doing this at Palantir, where he later ran the rotation program that turned software engineers into forward deployed engineers, and his throughline is that the work was never a sales motion, it was product strategy in disguise. The engineer sits in the customer's environment, solves the concrete problem in under a day, and then generalizes it into something the whole product can use. The compounding lessons are less obvious. Watch what people actually do: any task a user repeats is a hint at a missing feature, and someone pulling out their phone in the middle of a workflow is a bug report you will never find in documentation. The deepest one is language. When a customer says clients, finance says billing, and support says accounts, the ambiguity costs real money, so the forward deployed engineer defines the terms, the ontology, and becomes the linguistic layer the rest of the system is built on. A throwaway Groovy script that quietly became a product a year later is the whole pattern: forward deployed engineers drive product strategy without anyone calling it that. Speaker info: https://x.com/vinooganesh / vinoo-ganesh https://vinoo.io Timestamps: 0:00 - Introduction: FDE's origins at Palantir 2:05 - Not a role, a product strategy 4:51 - Real stories: scoping down to a Slack alert 7:11 - Solve in a day, then ship the real thing 8:33 - The data quality engineer story 10:03 - Watch what users actually do 12:33 - Own the language: clients vs billing 14:54 - The ontology and the linguistic layer 16:51 - The Groovy script that became a product 18:09 - The most important skill: what to discard 19:38 - Ship everything like it runs forever 21:11 - FDE as an extension of product