The Rise of the Forward Deployed Engineer — and How To Do the Job Right
Vinoo Vodrahalli, who built FDE programs at Palantir, Citadel, and Kepler, argues that the term "forward deployed engineer" has been diluted to mean almost anything customer-facing. The real job is solving last-mile problems at customers while sending those solutions back to the product team to build generalizable features.
- Most companies misuse the FDE title for sales engineers, consultants, or quota-carrying reps, when the role should specifically mean a product-focused engineer who lives inside customer operations and feeds insights back to the core platform.
- The FDE function emerged because low-hanging fruit in SaaS is gone—you can't infer messy, undocumented workflows from discovery calls, so someone has to sit inside the customer's walls to understand what actually happens.
- An FDE's job is to learn a customer's "nouns and verbs" (the concepts and operations they treat as real) so they can both solve immediate problems and identify which solutions should become generalizable platform features; without that feedback loop, you're just running a consulting team with a better title.
Vinoo, CEO of Kepler, argues that "forward deployed engineer" has become a meaningless term because companies use it to describe wildly different jobs with different reporting structures and incentives. At a16z fellowship dinner, he discovered FDEs ranged from sales engineers on their second call to quota-carrying reps who code to consultants with statements of work—basically anything involving a customer. The confusion matters because these aren't the same role, yet everyone uses the same label. His point: the term has been so diluted that half the internet asks whether FDEs are just consulting rebranded.
Vinoo traces what he believes FDEs should actually be through his own experience at Palantir building a transaction store called Phoenix. The system worked perfectly in controlled environments but catastrophically failed at a bank when it hit real financial data with gaps and blank timestamps that test data never had. The root cause wasn't bad research—they understood the spec and use cases. It was that nobody stood in the actual building watching production data run. That failure forced him into the field as an FDE to fix what they'd shipped, and suddenly he could see the gap between design and daily reality. Phoenix then evolved into a platform that FDEs built on across cybersecurity, KYC, and AML—meaning the role became about solving customer problems to generate insights that informed what got built next.
The real issue is that low-hanging fruit is gone. Five years ago, well-designed products sold identically to a thousand companies solved most problems. What remains requires someone sitting inside customer walls because the work is bespoke and can't be standardized into a product. That's what an FDE should be—an extension of the product team who earns customer insight through solving real problems, not a salesperson with Python skills or a consultant pretending to be an engineer. The co-option of the term reflects a correct instinct that customers matter more now, but companies have attached the label to the wrong jobs.