Org structure and culture propagate directly into product architecture; deliberately cross-hatching teams with opposing mandates converts external friction into internal alignment pressure.
Key Takeaways
Palantir’s FDE/SWE split is a canonical cross-hatching example: FDEs own one customer across the whole product, SWEs own one product area across all customers.
Tension between the two orgs was intentional, not accidental – it forced customer pain inside the org and aligned everyone around outcomes.
Separate people leads and project leads (with counter-weighted mandates) decoupled mentorship from management and let leadership grow independently of headcount management.
At Spiral, the seam between open-source Vortex and proprietary Spiral reproduces the FDE/SWE problem: features ship in Vortex but lag in deployment, or workarounds land in Spiral instead of being fixed upstream.
AI tooling shifts the bottleneck from code output to consensus, design, and taste; optimal pod size shrinks to 3-4, raising demands on structural scaffolding around those pods.