How Palantir Scaled: Why the Best Software Is Built Backwards

影片總結

Palantir Chief Architect Akshay Krishnaswamy explains how forward-deployed engineers turn customer pain into products while building backward from outcomes.

On the a16z podcast, host Erin Price-Wright talks with Palantir Chief Architect Akshay Krishnaswamy about forward-deployed engineering (FDE), a model now sought by companies in defense, robotics, and AI. Krishnaswamy describes building backward from mission outcomes—such as finding roadside bombs or improving petroleum operations—then generalizing solutions into products. Unlike services roles measured by hours or contract deliverables, FDEs own customer outcomes and feed field problems back into product development: they “absorb pain and then excrete product.” The work demands technical range, resilience under customer pressure, and the ability to translate specific fixes into reusable tools. For early teams, he recommends focus: treat field engineers as an extension of the product team, not scattered tiger teams. High autonomy can bring speed and insight, but requires leaders to integrate parallel work. As Palantir scales, its platform should increase ambition rather than reduce field engagement; custom requests can be handled through platform features, tailored applications, or partners. The model fails when it is merely a branded offshoot without organization-wide support, shared teams, and leadership cover.

章節

1. 0:00Introduction: Akshay Krishnaswamy’s biomedical engineering path to Palantir
2. 2:17Defining FDE: Build backward from field outcomes, then generalize
3. 4:49FDEs own outcomes and turn customer pain into product improvements
4. 6:09Building FDE teams: technical range, pain tolerance, and mission-driven hires
5. 9:55FDE evolution: Focus teams, integrate autonomy, and use platform leverage
6. 15:27Maintaining product focus: ambitious commitments and shared customer teams

完整分析還有什麼

6 章 · 31 個重點 · 6 段段落總結 · 心智圖

其餘 28 個重點、段落總結與心智圖在完整分析裡。 分析這支影片,看完整內容 →