The Rise of the Forward Deployed Engineer — and How To Do the Job Right
- ID
- 23810
- Status
- summarized
- Published
- 12 Sep 2026, 11:01 PM
- Fetched
- 13 Sep 2026, 12:50 AM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/forward-deployed-engineer-best-practices
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 7.0
- Created
- 13 Sep 2026, 12:51 AM
- Tags
- Audience
- developerssaas_foundersai_ml_learners
What happened
Vinoo Ganesh, CEO of Kepler, draws on building forward deployed engineer (FDE) programs at Palantir (Project Frontline, ~250 engineers rotated through, many now running FDE teams at OpenAI, Anthropic, xAI, Anduril), Citadel, and Kepler to explain what the role actually is and where teams get it wrong. He notes that at an a16z FDE Fellowship dinner, people from Snowflake, Anthropic, and startups were all using 'forward deployed' to describe fundamentally different jobs — sales engineer on the second call, quota-carrying rep who writes Python, or a consultant delivering what the product couldn't.
Why it matters
If you're hiring FDEs or considering the role, the article's core warning is that 'forward deployed' has become a meaningless label covering sales engineering, consulting, and product engineering. The practical decision: clarify whether your FDE function sits in sales or product, and define what success looks like before hiring — Ganesh places Kepler's FDE function inside product, not sales, because in his domain a plausible wrong answer is worse than no answer.
Discussion angle
For founders building AI products for enterprise customers: when do you need an FDE versus a sales engineer versus a consultant, and should that function report into product or sales? The article argues these are being conflated in ways that waste money and misset expectations.