Feb 3, 2023 · 54m · 20product
20Product: When to Hire a CPO, The Three Different Types of CPO, How To Know What You Need, How To Structure the Hiring Process, What Are the Must-Ask Questions, What Tests and Case Studies Should Be Used, How Should Their Compensation Package Be Structur
compilation · excluded from per-person scoring
Harry Stebbings · 13m spoken Shreyas Doshi · 8m spoken Marty Cagan · 6m spoken David Lieb · 5m spoken Annie Pearl · 4m spoken Aparna Chennapragada · 2m spoken Scott Belsky · 2m spoken
0:00 / 0:00
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
A masterclass episode of 20Product featuring top tech executives—including Shreyas Doshi, David Lieb, Marty Cagan, Lenny Rachitsky, Annie Pearl, Aparna Chennapragada, Scott Belsky, and Kayvon Beykpour—who share actionable frameworks for when and how to hire product leadership, identify PM archetypes, structure interviews, and evaluate non-traditional talent.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 26.5% of the talking time here. How this is scored →
Harry as informed peer 3.0 Guest teaching 5.8 Guest disagreement 2.0 Harry pushing back 2.3
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 16:04 Annie Pearl rejects Harry's premise on lost artistry
When Harry suggests that scaling product organizations inevitably destroys product artistry, Annie directly rejects the premise with 'Absolutely not' and insists top companies retain craft.
Hardest push from Harry ▶ 28:17 Harry challenges Marty Cagan's 25-engineer thresholdHarry refuses to accept Marty's baseline rule that founders should wait for 25-30 engineers before hiring a PM, interjecting that it seems like an excessively high headcount requirement.
Biggest teaching moment ▶ 25:22 David Lieb on domain experience being anti-correlatedDavid reframes standard hiring conventions by revealing that at Google Photos, background domain experience was actually anti-correlated with top PM performance.
Harry holds his own ▶ 23:26 Harry synthesizes Shreyas' framework to critique operator CPOsHarry demonstrates keen industry insight by weaponizing Shreyas Doshi's operator persona to call out unproductive, process-obsessed Series C CPOs.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| Shreyas Doshi on the Three Product Leader Archetypes | 3 | 6 | 1 | 2 | Shreyas Doshi presents his framework of three product leader archetypes (Operator, Craftsperson, Visionary). Harry asks guiding follow-up questions to structure the interview, allowing Shreyas to educate the audience on common founder hiring missteps. | |
| Annie Pearl on Company Growth Stages, CEO-CPO Alignment, and Hiring Frameworks | 4 | 5 | 2 | 3 | Harry posits a provocative hypothesis about whether scaling product teams forces a loss of artistry. Annie Pearl directly counters this premise, explaining how CEO-CPO alignment preserves product craft. | |
| David Lieb on Avoiding Early CPO Hires and Overcoming Domain Dogma | 5 | 6 | 2 | 4 | Harry uses Shreyas Doshi's operator archetype to launch a sharp critique against process-heavy Series C CPOs. David Lieb strongly agrees and shares anti-intuitive insights, such as domain experience being anti-correlated with top performance. | |
| Marty Cagan on Founder-Led Product Management and Coaching Junior Talent | 4 | 7 | 3 | 5 | Harry actively challenges Marty Cagan's threshold of requiring 25 to 30 engineers before hiring a PM, as well as pushing back on Marty's skepticism of hiring tests. Marty delivers strong counterpoints grounded in developer coaching and domain dogma. | |
| Lenny Rachitsky on Hiring Triggers, Mini-CEOs, and Full-Day Case Studies | 2 | 5 | 1 | 1 | Lenny Rachitsky breaks down three hiring triggers and outlines a full-day project interview structure. Harry takes a supportive, facilitative role asking for practical breakdowns. | |
| Aparna Chennapragada on Hiring for Hustle, Back-Channeling, and High Ambiguity Tolerance | 2 | 5 | 2 | 1 | Aparna Chennapragada emphasizes hiring for hustle and ambiguity tolerance over general athlete credentials, warning against premature PM hires. Harry facilitates by asking how to screen for these behavioral traits. | |
| Scott Belsky on Preserving Founder Superpowers and Uncovering Team DNA | 2 | 6 | 3 | 1 | Scott Belsky challenges the default founder belief that product vision should be handed off as a company scales. Harry listens as Scott explains how a product's details expose team DNA. | |
| Kayvon Beykpour on Reactivity Signals, Early PM Traits, and Timely Offboarding | 2 | 6 | 2 | 1 | Kayvon Beykpour details reactivity signals in scaling teams and explains why taking too long to offboard misaligned PM hires is the single most expensive startup mistake. Harry asks candid, beginner-oriented questions. |
Statements from this episode (17)
Doshi categorizes product leaders into operators, craftspeople, and visionaries
“One of the patterns is the three types of product leaders, and they are the operator, the craftsperson, and the visionary.”
David Lieb: Domain experience anti-correlates with top PM performance
“Most of the really strong PMs that have emerged, say, on the Google Photos team came from backgrounds with no experience in this domain. I would probably go so far as to say that it's anti-correlated with the top performers.”
Doshi: Operator product leaders cannot achieve product-market fit alone
“It is nearly impossible for an operator to bring your product to product market fit.”
Doshi: Craftsperson product leader is the default early-stage hire
“That is a reasonable default, especially if you're early stage, say perhaps pre-PMF or just about reaching PMF. Then craps person is of good default.”
Pearl: Early product leaders must execute the founder's vision, not redefine it
“Pre-product markets sit, founders usually doing most of the product management, working directly with the engineers, getting things built. So then usually, you know, you find product market fit and maybe you bring on your first product manager or your first, y…”
Pearl: Visionary founders should hire product operators, not visionary product leaders
“The mistakes that I see happen is that the CEO founder goes to hire for a skill set that Is either at odds with what they really need, or they're not actually honest with themselves around the role that they want to continue to play within product. And so if y…”
Lieb: Bump prematurely hired a product lead before reaching PMF
“I made this mistake myself at Bump. We got to like, maybe it was 30 employees. All of our vanity metric graphs were like going way up. We were feeling really good. And I thought our company is going to need to like figure out our business model. Eventually we'…”
Lieb: Founders must not delegate their startup's primary problem
“Generally, that is a very dangerous place to be where the founders or the CEO of the company is not working on the most important problem for the company's success.”
Lieb: Over-indexing on past team scale ruins product hires
“The number one failure mode when people hire product leaders is they over index on previous scale. How big of a team have you previously managed or tenure?”
Cagan never invests in startups lacking a founder product leader
“I personally never invest in a startup unless at least one of the founders is a proven product leader.”
Cagan: Take-home tests for hiring product managers are ineffective
“I'm not a fan, by the way, of tests in terms of people will have these assignments. In my experience, they're not very indicative of what you're really looking for. And let me put it this way. I still haven't found that test that I think is any good.”
Cagan: Almost all innovative tech products come from domain outsiders
“My evidence for that is just look across our industry, across time, that all the innovative products, almost all of them, came from people and teams that had no real domain experience.”
Chennapragada: Early-stage startups should not hire generalist PMs
“Do not hire a general athlete PM is my advice.”
Chennapragada: Differentiate PMs who drove growth from those riding tailwinds
“So you have to differentiate between people who were in the parade versus help the parade. And you certainly have to look for the jerks who pushed everybody aside and somehow got to the front of the parade.”
Belsky: Founders should retain direct control over their superpower function
“I think you should abstract yourself out of almost every function, except for the one that is your superpower, that you are the unique person in the world to do, and you should keep doing that as long as humanly possible.”
Belsky: Software products directly reveal the organizational DNA of their teams
“A product always speaks to the DNA of the team behind it. You can tell who wasn't talking to one another, you know, what the values were, whether there was a designer outsourced, or in the room, sufficiently empowered, etc.”
Beykpour: Big-tech PMs struggle at early startups due to excess structure
“Sometimes see like folks that have only worked at larger companies struggle with this because they're so used to having a lot of structure and clarity around like, okay, my job is this and therefore my expectations are this.”