How Palantir Scaled: Why the Best Software Is Built Backwards

Video summary

Palantir’s Akshay Krishnaswamy explains FDEs, backward product building, Foundry, and avoiding the consultancy trap.

Palantir Chief Architect Akshay Krishnaswamy explains why forward-deployed engineering (FDE) is more than rebranded services: teams begin with a concrete mission—such as finding roadside bombs or improving petroleum operations—then build backward from the outcome and generalize what works. Unlike solutions architects tied to hours or contract deliverables, FDEs own customer results while turning field pain into reusable product. Krishnaswamy describes the role’s required traits, including technical versatility, high pain tolerance, and the ability to challenge core teams. He recalls Palantir’s former 6–12-month field rotation before product work and argues that Foundry’s mature platform should increase ambition, not reduce FDE engagement. To avoid becoming a consultancy, companies need focused teams, shared accountability across product and partnerships, and enough organizational “top cover” to solve hard problems without creating permanent bespoke dependencies.

Chapters

1. 0:00Introduction: Akshay Krishnaswamy and Palantir’s FDE Model
2. 2:17Defining Forward Deployed Engineering: Building Backward from Mission Outcomes
3. 4:49Differences Between FDE and Other Roles: Absorbing Pain into Product
4. 6:09Building and Managing Teams: Selecting High-Pain-Tolerance FDEs
5. 9:55Challenges and Evolution of FDE: Focus, Autonomy, and Product Leverage
6. 15:27Maintaining Product Focus and Customer Relationships: Scaling Ambition Without Becoming a Consultancy