💡

InsightHunt

Hunt the Insights

N

Nabeel S. Qureshi

Episode #216

Founder (Stealth); Former Forward Deployed Engineer

Ex-Palantir

🎯Product StrategyExecution👥Team & Culture

📝Full Transcript

19,734 words
Lenny Rachitsky (00:00:00): 30% of PMs that leave Palantir start a company. Just give us a picture of what the people are like. Nabeel S. Qureshi (00:00:05): I feel like they screened really hard for a few traits in particular. One is like very independent-minded people who weren't afraid to push back. Two is people with broader intellectual interests. Lenny Rachitsky (00:00:15): What's the difference between, say, a PM at Palantir versus a traditional PM? Nabeel S. Qureshi (00:00:18): 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. There's two types of engineer at Palantir. So, there's one that works on the core product and they're a traditional software engineer. There was a different type of engineer which you sent into the field. You would spend maybe Monday to Thursday and you would actually go into the building where the customer worked and you would work alongside them. You would literally get a desk there and so, that engineer became known as a forward deployed engineer. Lenny Rachitsky (00:00:51): What's something that you believe that most other people don't? Nabeel S. Qureshi (00:00:54): I think this is a somewhat contrarian view within tech. Lenny Rachitsky (00:00:58): Today, my guest is Nabeel Qureshi. Nabeel is a founder, a writer, a researcher, and an engineer. He was recently a visiting scholar researching AI policy at the Mercatus Center alongside Tyler Cowen. At one point, he worked with the National Institute of Health and major clinical centers to create the largest medical data set in the world. He worked at the Bank of England for a bit. He was founding member and VP of Business Development at GoCardless, one of Europe's biggest financial technology unicorns. (00:01:23): And most related to the topic of this conversation, Nabeel spent almost eight years at Palantir as a forward deployed engineer working on public...

💡 Key Takeaways

  • 1Palantir’s 'Forward Deployed' model serves as a forge for founders, with 30% of alumni PMs starting their own companies.
  • 2Real product innovation often comes from solving 'unsexy' data plumbing problems (access, cleaning, integration) rather than just analytics.
  • 3The 'Ontology' layer is the secret sauce: mapping cryptic database tables to human-readable business concepts (e.g., 'Aircraft' instead of 'Table_F4').
  • 4Hiring should filter for 'spikiness' and mission alignment (the extra 20% effort) rather than just generic competence.
  • 5High-touch, in-person engagement with customers builds trust and feedback loops that remote work cannot replicate.

📚Methodologies (3)

🎯 Product Strategy

Instead of building software in a vacuum, deploy engineers to the client site to work side-by-side with users. Solve the specific, messy problem manually or with custom scripts first, then abstract successful patterns into a scalable software platform.

Core Principles

  • 1.Embed engineers on-site (Monday-Thursday) to gain visceral empathy and context.
  • 2.Charge for the outcome (value-based pricing), not just the software seats.
  • 3.Rapid Iteration Cycles: Build on Monday, get feedback Tuesday, iterate Tuesday night.
  • +1 more...

"You learn to live and breathe the customer's problems... you would have to create new software such that it could actually solve the novel problem that was in front of you."

#forward#deployed#product
View Deep Dive →
Execution

Recognizing that 90% of data work is ingestion and cleaning, this framework focuses on creating a semantic layer between the raw database and the user. It maps technical data to 'real world objects' (e.g., a Plane, a Hospital Bed) so non-technical users can interact with it.

Core Principles

  • 1.Ingest Everything: Use universal adapters to pull data from any source (S3, ERPs).
  • 2.Map to Human Concepts: Translate cryptic table names (e.g., 'T_79_Z') into business objects (e.g., 'Work Order').
  • 3.Enable Object-Based Traversal: Allow users to click from 'Plane' to 'Parts' without writing SQL joins.
  • +1 more...

"If you can pull in these tables... and map them to human concepts... then a user can just log in and say, 'Okay. Aircraft 79, where is that?'"

#'ontology-first'#execution#process
View Deep Dive →
👥 Team & Culture

A rigorous pre-mortem process where a project lead presents a plan to a group of smart, disinterested parties whose sole job is to tear the plan apart to find flaws in logic, strategy, or principles.

Core Principles

  • 1.Write a 2-Page Memo: Vision, goals, and tactics must be written down clearly.
  • 2.Define Controversial Principles: Principles must be actionable and debatable (not generic like 'move fast').
  • 3.Invite Disinterested Critics: Include smart people who don't know the project to avoid confirmation bias.
  • +1 more...

"You invite three or four smart folks who don't know anything about the project and their job is just to tear apart your plan."

#murder#board#planning
View Deep Dive →