How Forward Deployed Engineering is done at Kepler — Vinoo Ganesh
Jul 28, 2026 · 22:20
Vinoo Ganesh, a former Palantir engineer who built the Frontline rotation program, argues that Forward Deployed Engineering is a product strategy, not a go-to-market motion, and shows how Kepler applies this philosophy. He illustrates with stories from Palantir: solving a shipping customer's 47-page requirements with a four-hour Slack alert, building a Parquet viewer after watching a data quality engineer manually spot-check CSVs, and the Groovy script that became a product supporting 100,000 people. Ganesh emphasizes detecting real problems by observing users' actions—any repeated task hints at a missing feature, and pulling out a phone mid-workflow is a bug report you'll never find in documentation. He also explains defining ontology: when different teams call the same entity 'clients,' 'billing,' or 'accounts,' the FDE must canonicalize terms to become the linguistic foundation. The hardest skill is discarding—ship everything as if it will run 18 months, because every hack goes into production. Ganesh concludes that FDEs drive product leverage by solving small problems on-site, then generalizing solutions into the core product.
