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

Source: [AI Engineer](https://www.youtube.com/watch?v=KwhgfwOSToQ)  
Feed7 permalink: https://feed7.dev/p/forward-deployed-engineering-101-kevin-bai-anthropic-ex-palantir-ripplin-1rzcr0v  
Published: 2026-07-28T15:00:06.000Z  
Trust: Source Linked (source_linked)

## Why Included

Forward-deployed engineering fits technical products sold to nontechnical buyers, but only when customer work composes shared platform primitives instead of creating bespoke codebases.

## Source Summary

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.

## Practical Implication

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.

## Agent-Ready Context

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.

## Connected Context

Feed7 judgment across 262 accumulated Signals:

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.

- [The Dirty Secret of Forward Deployed Engineering — Natalie Meurer, Sierra](https://feed7.dev/p/the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97) — Bai gives architectural and organizational structure to Sierra’s broader role definition: customer-accountable work scales when field engineers build from shared primitives and return reusable changes to the platform.
- [Forward Deployed Engineering at Cursor — Pauline Brunet](https://feed7.dev/p/forward-deployed-engineering-at-cursor-pauline-brunet-1wkd3r1) — Shared primitives and product reintegration provide the platform-side counterpart to Cursor’s requirements for customer ownership, measurable use cases, and documented handoff, all aimed at avoiding staff augmentation.

## Context Map

- Layer: industry
- Domains: coding
- Topics: enterprise, adoption

## Uncertainty

- 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.