May 11, 2025 · 1h 37m · lennys-podcast
How Palantir built the ultimate founder factory | Nabeel S. Qureshi (founder, writer, ex-Palantir)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Former Palantir engineer and founder Nabeel S. Qureshi joins Lenny Rachitsky to unpack Palantir's unique organizational culture, the mechanics of Forward Deployed Engineering, and the architectural principles that turned the enterprise data platform into Silicon Valley's ultimate startup founder factory.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 25.2% of the talking time here. How this is scored →
Lenny as informed peer 4.3 Guest teaching 6.1 Guest disagreement 0.8 Lenny pushing back 0.3
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 1:24:15 Rejection of the tech dropout dogma
Nabeel openly attacks the prevalent Silicon Valley narrative that ambitious 18-year-olds should routinely drop out of college, calling it misguided advice for 95% of people.
Hardest push from Lenny ▶ 13:29 Lenny questions the value of hyper-competitive hiringLenny pushes back on Palantir's preference for hyper-competitive, intense candidates, questioning how that produces a collaborative and productive team culture.
Biggest teaching moment ▶ 35:50 Deconstructing ERP obfuscation to invent OntologyNabeel provides a masterclass on how unreadable SAP data tables in an aircraft assembly plant necessitated translating raw database rows into human-legible business ontologies.
Lenny holds their own ▶ 5:12 Lenny presents global ranking data on Palantir alumniLenny establishes his product management research expertise by citing precise global metrics on Palantir alumni leading all tech companies in founder creation and promotions.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Understanding Palantir: The Data Platform Powerhouse | 6 | 4 | 0 | 0 | Lenny opens by presenting data from his own research showing Palantir ranks number one globally for PMs becoming founders and getting promoted. Nabeel gives a concise baseline explanation of Palantir's core data platforms, Gotham and Foundry. | |
| Palantir's Unconventional Hiring and Intellectual Culture | 5 | 6 | 1 | 0 | Nabeel describes Palantir's idiosyncratic hiring practices, founder interview vibe checks, and distinctive bat signal philosophy. Lenny draws parallels to establishing strong cultural values and clear exclusions at Airbnb. | |
| Tapping Undervalued Talent Pools for High Stakes | 4 | 6 | 1 | 3 | Lenny pushes back gently by questioning why screening for fiercely competitive traits produces a productive culture. Nabeel explains the talent arbitrage of hiring former military and intelligence veterans who excel in high-stakes environments. | |
| The 'No Titles' Philosophy and Meritocratic Fluidity | 3 | 6 | 1 | 0 | Nabeel explains Palantir's no-titles policy, citing Goodhart's law and title-chasing anti-patterns at legacy tech firms. He notes both the meritocratic fluidity and the subtle political downsides of titleless structures. | |
| The Anatomy of a Forward Deployed Engineer | 4 | 7 | 0 | 0 | Nabeel defines the Forward Deployed Engineer (FDE) role, describing how embedding on-site with clients four days a week creates high-speed feedback loops that serve as an ideal training ground for future founders. | |
| Transforming Bespoke Client Solutions into Platform Software | 4 | 7 | 1 | 0 | Lenny inquires how Palantir scaled from a perceived consulting outfit into an 80% margin SaaS platform. Nabeel explains how internal tools used by FDEs were unified into Foundry following an executive mandate to put software directly into customer hands. | |
| Core Product Architecture: Gotham Versus Foundry | 5 | 7 | 0 | 0 | Nabeel contrasts Gotham's defense-oriented, graph-based nodal analysis and geospatial mapping with Foundry's enterprise relational table workflows. Lenny synthesizes the unified three-tier architectural stack. | |
| The Airbus Case Study and the Birth of Ontology | 4 | 8 | 0 | 0 | Nabeel provides an in-depth breakdown of his deployment at Airbus ramping A350 production, describing how decoding cryptic SAP tables led to the development of Foundry's core Ontology layer. | |
| High-Intensity Travel and Deep In-Person Immersion | 2 | 4 | 0 | 0 | Nabeel discusses the intense pre-2020 travel expectations and the immense trust built by physically being in the room with enterprise stakeholders. The segment includes a brief mid-roll sponsor exchange with Andrew Luo. | |
| Evaluating the Forward Deployed Model for Startups | 5 | 6 | 2 | 1 | Lenny asks whether early startups should adopt the FDE model. Nabeel warns that full FDE requires enterprise-scale contract sizes, while advising founders not to cling dogmatically to initial product visions when encountering burning customer problems. | |
| Key Ingredients for Effective Forward Deployed Engineering | 4 | 6 | 1 | 0 | Nabeel details the non-negotiable requirements for effective FDEs: true de novo engineering capability and deep domain business comprehension, illustrating with operational dynamics in US healthcare. | |
| Product Leverage, Evolving FDE Ratios, and AI | 3 | 7 | 0 | 0 | Nabeel outlines Palantir's revenue per engineer north star metric, explaining how product leverage and modern AI coding tooling have shifted the ratio from multiple engineers per client to one engineer managing several accounts. | |
| Navigating Enterprise Data Silos and Bureaucracy | 5 | 6 | 1 | 1 | Nabeel explains that Palantir's primary competitors are internal IT gatekeepers and in-house bespoke builds. Lenny notes the similarities to enterprise search players like Glean. | |
| Startup Hiring: Filtering for Extreme Drive and Mission | 5 | 6 | 1 | 0 | Nabeel shares principles for early startup hiring, prioritizing obsessive mission drive over polished corporate backgrounds and using proxy traits like athletics. Lenny reinforces the value of knowing who a culture excludes. | |
| Product Management at Palantir and Founder Genesis | 5 | 7 | 1 | 0 | Nabeel details why Palantir strictly promoted PMs internally from high-performing FDEs rather than hiring traditional PRD-writing PMs from Big Tech, explaining the resulting high density of successful founders. | |
| Addressing Moral Questions and Defense Tech Ethics | 5 | 6 | 3 | 1 | Lenny addresses the moral criticisms surrounding Palantir's defense work. Nabeel rejects ideological disengagement, arguing that technological deterrence is necessary and that engaging directly improves ethical precision and accountability. | |
| Foundational Startup Principles from the Palantir Experience | 5 | 6 | 0 | 0 | Nabeel summarizes core startup principles carried over from Palantir: fast bet cadence, pricing early for high commitment, maintaining internal excellence benchmarks, and tackling messy real-world industries. | |
| AI Corner: Practical Coding and Productivity Workflows | 4 | 5 | 0 | 0 | Nabeel shares practical daily AI workflows, highlighting Whisper Flow for dictating prompts and Claude Code for terminal-based file and PR automation. | |
| Contrarian Corner: The Enduring Value of College | 4 | 6 | 3 | 0 | In Contrarian Corner, Nabeel forcefully challenges tech's anti-college dropout dogma, advocating for university as an irreplaceable window for deep intellectual exploration and peer bonding before drawing chess engine parallels. | |
| Lightning Round: Influential Books, Cinema, and Product Empathy | 4 | 6 | 0 | 0 | In the lightning round, Nabeel recommends Keith Johnstone's Impro, Shakespeare's Henriad, and Tolstoy's Anna Karenina, connecting literary theory directly to the empathetic imagination needed to build great products. |
Statements from this episode (36)
Rachitsky: 30% of departing Palantir PMs start a company
“I looked at which companies produce the most founders, especially out of their PM team, and Palantir is by far number one. 30% of PMs that leave Palantir start a company, and that's like, and number two is number, is 18%, and that's Intercom.”
Qureshi: Palantir historically required founder interviews for all job offers
“For the longest time they had, everyone does this now, I think, but it's like, at the time it was a little bit rarer as a founder had to interview you in order for you to receive an offer. And so a founder, it could have been Alex Karp. It could have been Step…”
Qureshi: Effective company recruiting signals must intentionally repel some people
“A lot of the best recruiters in the world, or like companies that attract talent, they put out this kind of distinctive bat signal, and it has to turn some people off. That's kind of the key of a good bat signal, right?”
Qureshi: Good operating principles must be stances people can reasonably oppose
“When people joined, they would write principles such as, you know, move fast. And I would always be like, everyone likes move fast. Like it's not a good principle actually, because nobody can really disagree with this reasonably. Right. You need something that…”
Qureshi: Military veterans possess skills uniquely suited for chaotic tech startups
“The people who succeed the most in the Marines or the special forces or whatever it is tends to be pretty smart people. They tend to have accomplished very difficult goals in very hostile environments. And it turns out that when you're starting a somewhat chao…”
Qureshi: Palantir actively trained employees into founders via operational design
“There was also a very concrete set of ways where that place was a training ground for founders. I even think it turned a lot of people who might not have become founders into Good founders because of just because of the way it works. So I think there was a sel…”
Qureshi: Palantir's only formal titles were CEO and six directors
“And the only people who did have titles were the CEO and then there were six directors and that was it.”
Qureshi: A no-titles structure preserves fluid meritocracy and performance accountability
“I actually am a big fan of this philosophy, though, the no titles one. I think what it did do is that it basically said you, if you are in, let's say you're in a role of you're leading a very important project, right, which would happen, what it said was, this…”
Qureshi: Palantir's average deals were multi-million dollars and value-priced
“The average kind of deal that Palance had was very large, right? It's in the many, many millions of dollars, which means that you could kind of pay for this as part of the thing that the customer got. And then it was sort of priced according to the value that …”
Qureshi: Rapid daily customer feedback loops make Palantir a founder factory
“Every week you would have like a cadence where it's like Monday, you go in, you do your meetings, Monday night, you build something. Tuesday, you show it to somebody. Tuesday, you get the feedback. Tuesday night, you iterate on it. Wednesday, you show it to so…”
Qureshi: Palantir operates at 80%-plus gross margins, disproving consulting label
“So they have like, 80% plus margins, which is not really what you would get if you were actually a consulting company. It would be closer to 20 or 30%.”
Qureshi: Palantir mandated customer tool adoption within three months per deployment
“And then Shamsankar is one of his I think he's a CTO or maybe he's the president now. He just mandated like, okay, every, every customer deployment, you have to have a customer using this within, you know, three months or whatever it is.”
Qureshi: Gotham is graph-based analysis, while Foundry focuses on SQL tables
“Another big difference is the idea of graph-based analysis. So Gotham, one of the kind of early use cases, right, was finding, combing through networks of terrorists and basically finding the bad guys. And so being able to do queries that are sort of graph-bas…”
Qureshi: Palantir Foundry's ontology stemmed from Airbus deployment
“And so the ontology became a huge piece of foundry. It was directly informed by the learnings that we had from building that application inside that factory. And I would say it's still a very big differentiator today. Like I don't think too many other companie…”
Qureshi: Palantir helped Airbus achieve 4x A350 production ramp in one year
“I didn't recall the exact stat, but we did ramp up production. I think at least forex that one year, which I mean, obviously they did this and we just helped with it, but you know, that CEO said that we played a critical part, so.”
Qureshi: Traditional FDE model requires billion-dollar revenue enterprise clients
“You need each customer's revenue to be probably in the billions of dollars. If it's below that, you're probably not looking at a traditional forward deployed engineer motion.”
Qureshi: Founders fail more by clinging to product vision than tailoring
“I think the error that People make more often than not as they are actually too stuck on their own product vision. That's the mistake I've seen a little bit more actually than the other way around”
Qureshi: AI labs are actively hiring forward deployed engineering teams
“I know that the AI labs are hiring forward deployed engineers now. They're building forward deployed engineering teams”
Qureshi: Palantir FDEs Succeeded Because Engineers Could Build De Novo Products
“The key things that made our model work were, one they were actually real engineers who could build product themselves. That's a very big difference, right? I think a lot of the time companies will say, this person's a forward-deployed engineer, but actually t…”
Qureshi: More Startups Will Use AI Coding Tools to Deploy Engineers
“I think this is a really interesting piece that you've just hit on, and I expect to see a lot more startups that take advantage of that insight.”
Qureshi: Palantir measured internal success via revenue per engineer
“One of the kind of metrics that the company had to measure its own success was essentially revenue per Engineer. Right. And so the more kind of quote unquote product leverage you had, the higher that number was.”
Qureshi: Palantir could 100x again due to proprietary data foundations for AI
“One lens through which you can view this company is they spent 20 years basically building the mother of all data foundations for every important institution in the world, and Guess what's very valuable now that AI models are out is proprietary data that isn't…”
Qureshi: Palantir is among the most generative product and UX companies
“People don't think of Palantir as this Place where innovative new product and UX ideas come out, but I actually think it's been one of the most generative companies for that specifically in the last 20 years.”
Qureshi: Palantir's biggest competitor is companies rolling their own solution
“Palantir's biggest competitor is a company rolling its own solution.”
Qureshi: FAANG engineers often struggle with startup outcome-oriented effort
“Like, I think when you hire out of, especially, not to pick on them, but I think if you hire out a fan, right, it's like people, People want like a 400 K a year job. They would like to work a certain number of hours. They would like to ship some code and then …”
Qureshi: Palantir hired veterans and pro-America talent for stronger mission drive
“So I think for Palento, they did hire a lot of Vets, for example, or maybe people who were a little bit more patriotic or pro-America than the average tech employee, and that those people had an extra reason to join Palantir and an extra reason to try that lit…”
Qureshi: Palantir only made employees PMs after proving themselves as FDEs
“The big difference, or one big difference I noticed was that they were extremely careful about only making people PMs who had first proven themselves out as forward deployed engineers. You basically could not become a PM any other way.”
Qureshi: At least six from his 25-person Palantir team became unicorn founders
“I was part of a pretty small team within Palantir. I think it was 20 to 25 people when I joined, and I think at least six of them now are either Unicorn or just pre-Unicorn founders from that, like, group of 25 people, which is actually a crazy ratio, and then…”
Rachitsky: More YC founders come from Palantir than from Google
“And when you look at YC founders and they're where they've come from, I think you may be shared in this in your post that there's more YC ex-Palantir founders than there are ex-Google founders in spite of Google being something like 50 times bigger sample size…”
Qureshi: Founders must immediately demand big money from customers to validate demand
“The classic YC thing is just when you take something to a customer, ask them to pay you a lot of money, and if they say no, then find a new problem. Like, don't wait three weeks, which is what every founding team typically does, because you don't have that kin…”
Qureshi: Enterprises are more open to working with small startups post-ChatGPT
“Post the chat GPT moment, People are willing to give chances to small startups that they weren't willing to do previously.”
Qureshi: Cost of forward deployed engineering has dropped 5x to 10x
“The cost of doing things like forward deployed engineering has fallen by maybe five to 10 X now at least.”
Qureshi: Claude Code is an exciting preview of AI coding agents
“I love Claude code for developing, even though I have my complaints about it. There's something just very addictive about just telling it what to do, and it can, it's basically something that you run within the terminal. Of your computer, and so you just type …”
Qureshi: Dropping out of college is bad advice for 95% of people
“I often see people saying just like, oh, if you can just drop out when you're 18 and just start working, why would you go to college? And I think this is completely wrong, but like maybe it's good advice for five percent of the population who probably would ha…”
Qureshi: The biggest AI winners will be hybrid cyborg operators
“The people who went here are going to be the kind of hybrid cyborgs who fuse with the AIs, right?”
Qureshi: Palantir required all forward deployed engineers to read 'Impro'
“And they made every kind of forward deployed engineer read that for the simple reason that I think it just helps you
Kind of read people better and interact with them better and become more conscious of how you are coming across and just modulate that.”