Forward Deployed Engineering 101 — Kevin Bai, Anthropic, ex Palantir & Rippling Founding FDE
Forward-deployed engineering fits technical products sold to nontechnical buyers, but only when customer work composes shared platform primitives instead of creating bespoke codebases.
Kevin Bai defines an FDE as a customer-facing software engineer. He helped grow Rippling’s function from its first hire to **about 25 people in one year**, and frames FDE as enterprise-scale design partnership work.
Use the model when a technical, customizable product must serve a nontechnical buyer. Build customer solutions from **shared platform primitives**, pair engineers to avoid knowledge silos, and move reusable work back into the core platform.
Kevin Bai defines an FDE as a customer-facing software engineer. He helped grow Rippling’s function from its first hire to **about 25 people in one year**, and frames FDE as enterprise-scale design partnership work. Use the model when a technical, customizable product must serve a nontechnical buyer. Build customer solutions from **shared platform primitives**, pair engineers to avoid knowledge silos, and move reusable work back into the core platform. Without that platform, the function becomes a custom development shop with mounting maintenance costs. The appropriate granularity of primitives depends on the breadth and needs of the customer base.
This narrows FDE from a broad customer-accountable role into an operating model with a hard architectural prerequisite: reusable platform primitives. It explains how the function can scale without becoming staff augmentation or accumulating bespoke maintenance, and adds pairing plus product reintegration as organizational safeguards against customer-specific knowledge silos.