20Product: The Five Step Process to Hiring the Best Product People, The Four Core Skills the Best PMs Need to Have, The Two Product Documents that Drive World Class Product Teams & Why the Best PMs are Writers with Scott Williamson, Former CPO @ Gitlab
Scott Williamson, former Chief Product Officer at GitLab, shares golden insights from his extensive career in product management. He emphasizes that a background in sales can be a solid foundation for product leaders and discusses the four core skills every PM should master: validation, building, business acumen, and communication. Scott reveals his rigorous hiring process and stresses that the best product teams are often made up of excellent writers. He also touches on balancing innovation with execution, making clear communication key to successful team dynamics.
55:52
forum Ask episode
web_stories AI Snips
view_agenda Chapters
menu_book Books
auto_awesome Transcript
info_circle Episode notes
insights INSIGHT
Product Management: Art vs. Science
Product management blends art and science, roughly 50/50 for most roles.
The ratio varies; growth PMs lean towards science, while startup PMs lean towards art.
volunteer_activism ADVICE
PM Hiring Process Structure
Structure PM interviews with five stages: recruiter screen, hiring manager interview, engineering manager interview, peer interview, and finalist/bar raiser interview.
Each stage assesses different competencies, from basic qualifications to domain expertise and case study performance.
volunteer_activism ADVICE
Core PM Competencies
Evaluate PMs on four core competencies: validation, building, business acumen, and communication.
Strong candidates excel in customer research, engineering collaboration, business metrics, and clear communication across stakeholders.
Get the Snipd Podcast app to discover more snips from this episode
Working Backwards provides a detailed look at Amazon's approach to culture, leadership, and innovation. The book is written by Colin Bryar and Bill Carr, who collectively have 27 years of experience at Amazon. It outlines the company's 14 leadership principles and how they are applied in practice, focusing on customer obsession, long-term thinking, and operational excellence. The book is divided into two parts: the first part explains the leadership principles and practices, while the second part includes case studies on the development of products like Kindle, Amazon Prime, and Amazon Web Services. The authors provide practical steps and insights that can be applied to any business, regardless of size or industry[2][4][5].
Scott Williamson was most recently Chief Product Officer for GitLab, where he led a team of 65 in Product Management, Product Operations, Growth, Pricing, and Corporate Development functions. Before GitLab, Scott was VP of Product for SendGrid for over six years, where helped lead the company to a successful IPO and $3B acquisition by Twilio.
In Today's Episode with Scott Williamson We Discuss:
1. From Sales to Product Leader:
Why does Scott believe sales is a great starting point for product people?
To what extent does an MBA help someone wanting to pursue a career in product management?
What does Scott know now that he wishes he had known when he started his career in product?
2. What, Who, When: How to Build a Product Team:
Is product management art or science? What is the ratio?
What are the four core roles of a product manager today?
When is the right time to hire your first PM?
What is the ideal profile for this first PM hire?
What are the single biggest mistakes founders make when hiring PMs?
3. Hiring the Best Product People:
What does Scott's hiring process look like for all new product hires?
How does Scott test for systematic thinking and problem-solving ability?
What questions does Scott always ask in interviews?
What are the best case studies to use to test a candidate's skill set?
How important is it for the candidate to have domain expertise in your product category?
4. The Best Product Teams are the Best Writers:
What are the two different types of documents that product teams must use?
How do you know when to use a one-pager vs a six-pager?
How does the discussion and planning cycle for the different documents differ?
How important is it for PMs to be great writers also?