Content-First Leadership Hiring
Test what candidates would do, not how fluently they describe a process.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 97%
Content-First Leadership Hiring distinguishes knowing what to do and when from knowing how to administer a process. Saxena argues that startups should hire leaders with product, customer, and industry content, then teach them the required process; reversing that sequence is much harder. The interview centers on a realistic work challenge with incomplete data. Candidates must explain specific actions and trade-offs inside generic stages such as ideation or execution, not merely present a polished methodology. Interviewers also examine past work and isolate the candidate's personal role from the achievements of the team. The final test is operational: if the leader's organization disappeared, could that person still specify what to build, when, and how, even without the capacity to do every task? This protects the company from making process itself the product.
Origin
Airbnb changed its interview process around Brian Chesky's belief that executives should know how to execute. Saxena describes using an Airbnb Plus work challenge and detailed probes into candidates' prior roles.
Core principles
- 01Content is knowing what to do and when; process is how the work is organized.
- 02Content expertise is harder to teach than process.
- 03Leaders must remain capable of doing the core thinking if their team disappears.
- 04A realistic work challenge exposes depth better than a polished presentation.
- 05Past impact must be separated from the achievements of the candidate's team.
How to run it
- 1
Define the required content
List the customer, product, market, and sequencing decisions the new leader must make. Separate those decisions from the meetings, rituals, and tools used to administer them.
Pro tip Ask what the leader must still know if every current team member leaves.
Watch out Do not use familiarity with your current process as a proxy for domain judgment.
- 2
Build a real work challenge
Give candidates a consequential problem the company genuinely faces, with enough context to reason but not enough data to reveal a single correct answer. Ask what they would do.
Pro tip Use a problem whose solution requires choices about customers, sequence, and operating model.
Watch out A generic presentation prompt rewards polish more than judgment.
- 3
Probe inside the process labels
When a candidate says ideation, execution, or iteration, ask for the actual action inside that stage. Look for concrete decisions such as evaluating a third-party operating partner before building internally.
Pro tip Keep asking, 'What would you do next, specifically?'
Watch out Fluent process vocabulary can conceal shallow content knowledge.
- 4
Isolate personal contribution
Review important past outcomes and ask precisely what the candidate did, decided, or changed. Distinguish their work from the collective résumé of the team.
Pro tip Ask why they made each major career and product choice, not only what happened.
Watch out Team-scale outcomes can make a process coordinator look like the content owner.
- 5
Run the team-disappears test
Imagine the candidate's future team vanishes. Assess whether the person could still roll up their sleeves and determine what should be built, when, and how.
Pro tip Capacity can shrink; judgment cannot disappear.
Watch out A leader who can only rebuild the organization before producing content creates a scaling bottleneck for the founder.
- 6
Teach process after hiring
Once content capability is established, onboard the leader into the operating rituals needed for coordination and scale. Keep process in service of the product and customer.
Watch out Rejecting all process is also a mistake; the claim is priority, not elimination.
In the wild
Airbnb asked candidates how they would create millions of homes at Airbnb Plus quality when the company did not know how to scale the operation. A generic answer such as ideation, execution, and iteration was insufficient. A candidate who proposed first investigating third-party companies that could scale the operation demonstrated content about what to do inside the process.
→ Interviewers could evaluate depth of thought and concrete operating judgment even though candidates lacked the internal data needed for a single right answer.
Common mistakes
Hiring the polished process expert
Knowing Scrum or a presentation structure does not show that a candidate knows what the company should build or how it wins.
Crediting the candidate with team output
A résumé summarizes collective outcomes. Interviews must isolate the choices and actions the candidate personally owned.
Eliminating process entirely
Saxena says companies need process to scale. The error is making it the answer instead of a support for content.
Is it for you?
Best for
Founders hiring product leaders or executives who must own strategy and execution in an early or scaling company.
Not ideal for
Highly standardized roles where process compliance is itself the primary job and content decisions are intentionally centralized elsewhere.
From the episode
Sanchan Saxena (VP of Product at Coinbase) on the inside story of how Airbnb made it through Covid; what he’s learned from Brian Chesky, Brian Armstrong, and Kevin Systrom; much more