reading list
The best Forward Deployed Engineer books & resources (2026)
There is no curriculum for this job. The Forward Deployed Engineer role asks one person to find the real problem, integrate systems nobody documented, build something that survives contact with production, and do all of it inside an organization that did not ask for the change. No single book covers that combination, which is why lists like this one tend to be padded with generic business titles.
This one is short on purpose. Three books, each for a specific failure mode in the field, followed by the primary sources — Palantir's own engineering writing, first-hand accounts, and a handful of talks — that were the research base for Forward Deployed. If you want the internal version instead, Palantir hands new hires its own five-book kit — the Palantir reading list.
Three books
- 01
Forward Deployed: Inside the Palantir Framework
Riste Gramatikov · 2026
The FDE role is usually described as a job title. This book treats it as the visible part of a system — customer selection, flat structure, mission-autonomous cells, and the feedback loop that turns field pain into platform capability.
It is the only book-length decomposition of that system, assembled from Palantir's own engineering blog, S-1, earnings calls, and conference talks, and worked through a single manufacturing case study end to end.
- 02
The Mom Test
Rob Fitzpatrick · 2013
The most common way a deployment fails is that the team builds exactly what the customer asked for. Requirements are a description of what someone already imagines the solution to be, not of the problem.
This is the shortest usable guide to conversations that produce facts rather than compliments: ask about what people already do, not about whether your idea is good. Read it in an afternoon before your first workshop.
- 03
Inspired: How to Create Tech Products Customers Love, 2nd edition
Marty Cagan · Wiley, 2017
FDEs operate as the product manager, designer, and engineer for one customer's problem at once. Cagan's book is the reference for the half of that job most engineers have never been taught.
The parts that transfer directly are discovery versus delivery, the difference between a roadmap of features and a set of outcomes, and why empowered teams beat teams that receive specifications.
Articles, essays, and talks
Everything below is a primary or first-hand source. Where Palantir has explained its own practice, that writing is better than any summary of it, including mine.
The role itself
- A Day in the Life of a Palantir Forward Deployed Software Engineer →
Palantir
The primary source. What the work looks like hour by hour, written by the company rather than about it.
- A Day in the Life of a Palantir Deployment Strategist →
Palantir
The FDE's counterpart. Read both — the pairing is the point, and most companies copying the model only hire one half.
- Dev versus Delta: Demystifying Engineering Roles at Palantir →
Palantir
The clearest explanation of the split between building the platform and deploying it, and why both directions of pressure are needed.
- Understanding Forward Deployed Engineering →
Barry McCardel
An outside practitioner's account, and the best treatment of the mission-command idea: give intent, not instructions.
- Forward Deployed Engineers: AI's Hottest New Role →
Index.dev
Useful for the market picture — who is hiring FDEs now and how fast the listings grew through 2025.
How the organization works
- Reflections on Palantir →
Nabeel Qureshi
The single best first-hand essay on working there. Start here if you only read one thing on this page.
- The unconventional Palantir principles that catalyzed a generation of startups →
Adam Judelson, Lenny's Newsletter
Titles, hierarchy, and why influence was deliberately detached from rank.
- The Primacy of Winning →
Shyam Sankar, Pirate Wires
Sankar's own writing on the culture. The source of the artist-colony framing and the argument against process as a substitute for judgment.
- How We Do Agile →
Palantir
Delivery practice adapted to environments where requirements are discovered rather than given. Read the follow-up, Has Agile Gone Rigid?, with it.
- How to Get a Job →
Alex Karp, Bloomberg Businessweek
Karp on hiring for extreme strength in one area rather than for a balanced résumé — short, and the origin of a lot of later imitation.
The platform
- Connecting AI to Decisions with the Palantir Ontology →
Palantir
Why a semantic layer over the data is what makes model output actionable instead of merely interesting.
- From Human-Defined to Software-Defined Data Integration →
Palantir
The series on automating the integration work FDEs used to do by hand. This is the compound learning loop written up as engineering.
- Leveling Up Your Company: A Lexicon for Digital Transformation Success →
Palantir
The levels-of-autonomy framing. A useful diagnostic for where a customer actually is before you promise them anything.
- Deploying Full-Spectrum AI in Days: How AIP Bootcamps Work →
Palantir
How a multi-month sales cycle was compressed into a few days of building against the customer's real data.
Talks worth the time
- The FDE Playbook for AI Startups →
Bob McGrew
A former Palantir and OpenAI leader on how to run the model at a startup, and what breaks when you do it badly.
- Palantir AIP Capabilities Demonstration →
Shyam Sankar
Watch a deployment-shaped demo rather than a product demo. The framing of the problem is the interesting part.
- Building with Palantir AIP →
Palantir Developers
Hands-on build-alongs. The procurement episode is the best single entry point.
- From Analog to Digital | Tyson Foods + Palantir →
Scott Spradley
A customer CIO describing the same deployment from the other side of the table. Rare and worth it.
If you want the model rather than the skills — how the FDE role, the Deployment Strategist, the flat structure, and the platform fit together into one system — start with the free chapter on organizational implementation.