Forward Deployed Engineering 101 — Kevin Bai, Anthropic, ex Palantir & Rippling Founding FDE

Palantir’s core product, Foundry, is a software platform designed to centralize all data for organizations of any size into a single location. This centralization creates an 'ontology,' essentially assigning proper nouns (standardized labels) to data elements instead of relying on disparate tables or warehouses. The platform then allows companies to build applications upon this centralized and organized data foundation, but its success hinges on the customer’s ability to effectively utilize it.

Initially, Palantir struggled because customers were burdened with the cost of both the platform itself and the training required to use it effectively. To address this, Palantir shifted its business model from selling solely software or services to offering a combined solution. This involved sending experienced engineers directly to customer sites to build solutions on top of Foundry, delivering tangible outcomes rather than just technology.

Forward Deployed Engineering (FDE) is necessary when a company sells a highly technical product to non-technical buyers. This scenario arises because large tech companies have internal engineering resources, while organizations in industries like oil and gas often lack the expertise to fully leverage complex platforms like Foundry. The FDE role bridges this gap by providing specialized knowledge and implementation support.

Palantir's adoption of FDE was driven by the nature of Foundry as an application building platform. Because it is not as appealing to large tech companies with robust engineering teams, Palantir needed a way to ensure its Fortune 500 clients – who often lack in-house data expertise – could fully realize the value of the platform. FDE fulfills this need by providing direct support and implementation.

Kevin Bai emphasizes the critical importance of avoiding single points of failure when performing custom work for customers. He illustrates this with the example of a key person possessing all project information going on vacation, which would effectively halt progress. To mitigate this risk, he suggests collaborative approaches involving multiple teams or individuals to distribute knowledge and ensure continuity.

A question arises regarding the distinction between engineering changes applicable to a platform versus those specific to forward-deployed environments. Kevin Bai clarifies that bespoke and unique solutions tailored for individual customers should remain isolated to those clients. Conversely, any functionality or improvement with broader applicability should be generalized and integrated into the core platform over time.

Kevin Bai highlights that even when starting out in forward-deployed engineering (FDE), a limited set of primitives is acceptable. He explains that FDE serves as a valuable scouting mechanism, allowing teams to identify opportunities for new product services and features that can further enhance customer success and overall business enablement.

Responding to a question about the ideal profile for an FTE, Kevin Bai succinctly defines them as 'customer-facing software engineers.' This means they possess the technical skills of a standard software engineer but also the communication and interpersonal abilities necessary to interact directly with customers. He emphasizes that this role requires adaptability and ongoing learning.