The original is one click away. Open original ↗
How to hire, be hired, and recruit as a product leader
Executive overview
Most early-stage founders hire the wrong product leader by chasing big names — people who are far from the work and need a full team of executors around them. The better question isn't "who is the best talent in the world?" but "who is best for this specific role right now?"
Before kicking off any search, founders must define the mandate precisely: what this person will do in 90 days, one year, and two years. Failing to do that dooms the search from inception.
The long game — building relationships before you need them — is the single most effective hiring strategy for founders, candidates, and recruiters alike.
Common founder mistakes when hiring a first product leader
- Chasing "big name" CPOs from Google or YouTube who are far from hands-on work
- Failing to define what success looks like in 90 days, one year, and two years
- Hiring broadly ("we need a head of product") without specifying the actual mandate
- Bringing in one leader to do everything — platform, growth, monetization, UX — instead of identifying the most urgent need
- Hiring C-level executives too early; "head of product" is usually the right title until Series D/E
Defining the right product leader profile
- Decide where this person should major and minor: platform/infrastructure, core consumer product, or specialist (growth, monetization, UX/design)
- Work backwards from the outcome: are you hiring to ship an ads platform, improve core UX, or scale the team?
- "Best talent in the market" and "best talent for this role today" are two very different questions
- Closer-to-the-work candidates who can operate as a senior PM some days and lead on others are often more valuable than senior executives at early stages
- Avoid the unicorn trap: if the profile requires someone to do everything, it's too vague to hire against
Titles: head of product vs. VP vs. CPO
- Most startups are title-agnostic until Series D/E; "head of" is the default for senior product roles at seed to Series C
- "Head of product," "VP of product," and "CPO" are functionally equivalent at early stages — they all mean the most senior product leader in the org
- Avoid over-promising a C-title early; companies are dynamic and people can be layered as the company scales
- Candidates who will only consider CPO roles eliminate themselves from strong early-stage opportunities
Building a talent pipeline before you need to hire
- Always keep a pulse on the market — which companies are thriving, which individuals are standout performers
- Reach out to great people with no agenda: "I just want to know great people" is flattering and opens doors
- Bring candidates in as advisors or give them product involvement before a formal role exists
- Play the long game: the best hires often come from relationships cultivated over six to twelve months
- Network beats LinkedIn cold outreach for finding top 1% talent; many of the best people aren't active on LinkedIn
Running the search efficiently
- Tap five trusted people with strong networks; they will never refer someone who isn't excellent
- Ask those trusted contacts: "Who is the best person you've ever worked with? Can you put me on a thread with them?"
- Cold LinkedIn outreach is worthwhile for one-off conversations but not for time-constrained executive searches
- Ask investors and board members who they would target — they often have strong opinions
- Identify the best companies in a category first (market mapping), then go one layer deeper to find the breakout individuals within those companies, not just logo-holders who rode the wave
When to engage a recruiter
- Engage recruiters proactively and early, even informally, as a sounding board
- Series A (depending on check size) to Series B is typically when it makes sense to bring in a firm for senior roles
- Firms are usually better than one or two in-house hires at early stages for executive searches
- To evaluate a recruiter: tell them what you're looking for, then ask them to recite it back; ask for candidate ideas in real time to test calibration speed
What product managers should focus on for career growth
- Breadth of experience matters most for those aiming at leadership: touch platform, consumer product, growth, and monetization — not just one specialty
- Always keep a pulse on the market regardless of how happy you are in your current role
- Diversify both within an organization (types of product work) and across companies (stage, sector)
- Taking a bet on something entrepreneurial, combined with time at a more established company for best practices, is a strong combination
How long to stay at a company
- Logo collecting (less than a year, repeatedly) is a red flag that recruiters spot immediately
- Staying too long when the company is clearly failing is also a mistake — sometimes you must be selfish about your career
- The minimum bar: stay long enough to have a meaningful, visible impact that others can speak to on a reference call
- If you made an impact but only you know about it, it doesn't count; cross-functional visibility matters
- Don't hide short stints from your resume — it's more suspicious than explaining them honestly
Interview and resume advice for product leaders
- Practice telling your story; most candidates can't do it fluently until their tenth interview
- Never speak down on counterparts or blame engineering for missed deadlines in an interview
- Be honest about real weaknesses — interviewers see through "I work too hard" answers immediately
- Don't use vague job titles on LinkedIn (e.g., "whatever at Reddit") to avoid recruiters — it backfires
- Keep LinkedIn accurate and current; showing "present" for a role you left two years ago erodes trust
Reference checks: how to get real information
- Provided references are almost always positive; back-channel references are the real source of truth
- Ask hard questions: "Why would I not hire this person?" / "What are their actual weaknesses?" / "Would you report to them?"
- Even a slight pause in a reference's voice is worth noting
- If 10 people who worked alongside someone can't point to anything concrete they accomplished, no news is not good news
- Back-channel references are like tagged photos; provided references are like Instagram posts
What recruiters do wrong
- Treating candidates as commodities rather than human beings with lives, families, and careers outside work
- Ignoring explicit signals (e.g., a candidate who says they never want to work in crypto) and pushing irrelevant roles anyway
- Failing to listen and remember what candidates said in previous conversations
- Chasing placement quotas over relationship quality
- Recruiters who build trust can get candidates to hear out opportunities; those who don't will lose them permanently
- The fix: start with relationship building, find common ground, listen actively, and connect with people outside the context of a job opening
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.