← All speakers

Bio, Work & Ideas

Kevin Bai

Conference affiliation: Member of Technical Staff · Anthropic · 2026

Kevin Bai is a member of technical staff on Anthropic’s applied AI team and a practitioner of forward-deployed engineering: embedding software engineers with customers to turn adaptable technical platforms into concrete business outcomes. He previously worked at Palantir and became Rippling’s founding forward-deployed engineer, helping establish its customer-facing engineering organization.

From international affairs to applied AI

Bai studied environmental science, economics, and public policy at the University of California, Berkeley, and also pursued studies at the University of Oxford and the American University in Dubai. His early work included private-sector partnerships for UNHCR in Dubai and advocacy connected to the Comprehensive Nuclear-Test-Ban Treaty Organization.

He entered enterprise software at Globality, working on its AI-oriented procurement platform, before joining Palantir. There, he built customer-facing applications for operational problems, including consumer-packaged-goods and airline workflows. At Rippling, he helped create the forward-deployed engineering function behind Rippling Solutions, which builds customer-specific applications using the company’s existing data, permissions, and policies.

Bai subsequently joined Anthropic’s applied AI team. In announcing the move, he connected his interest in AI safety with his earlier engagement in nuclear-risk issues.

  • Customers buy operational outcomes. Bai argues that forward-deployed engineers bridge the gap between sophisticated platforms and buyers who lack the technical capacity to implement them independently. He treats the relationship as an enterprise-scale design partnership, with engineers learning the customer’s business and building solutions against real operational requirements.
  • Reusable platform primitives prevent bespoke-software sprawl. Customer-specific applications should draw on shared data models, permissions, integrations, and workflows. His account of forward deployment uses Palantir Foundry’s ontology to show how enterprise data becomes meaningful business entities that support practical applications. Features valuable across customers belong in the core platform; genuinely specific requirements remain local.
  • Forward deployment requires a real product mismatch. The model fits technically complex products sold to buyers who cannot readily configure or extend them themselves. Bai cautions that companies need both a legitimate customer-facing implementation problem and a sufficiently developed platform; otherwise they risk creating an expensive custom-development shop.
  • Agentic software makes customer context more valuable. As AI lowers the cost of building customizable applications, more companies face the adoption problems historically associated with flexible enterprise platforms. Bai positions forward deployment as a growth function, combining production engineering, product judgment, and direct customer engagement to accelerate adoption and identify reusable product improvements.

Through FDE Pod, Bai continues developing these ideas at the intersection of enterprise software, applied AI, and responsible technology deployment.

Read the topics behind these talks

1 conference talk

References