Instead of focusing on specialized skills, the most revealing interview question for a PM is, "Have you ever launched anything before?" This simple query cuts through over-specialization and assesses if a candidate understands the entire go-to-market lifecycle, from build to sales enablement and customer adoption.

The PM role is a high-leverage position intended to be a force multiplier for engineering and design. If a PM isn't making the team at least twice as good or twice as fast, their presence may be hindering progress, and the team would be better off operating without them.

The ideal early startup employee has an extreme bias for action and high agency. They identify problems and execute solutions without needing approvals, and they aren't afraid to fail. This contrasts sharply with candidates from structured environments like consulting, who are often more calculated and risk-averse.

The traditional model promotes top PMs away from hands-on work. Whatnot reverses this by having senior leaders, including the CPO, spend most of their time as individual contributors. This keeps the best 'players on the field,' leading to faster, higher-quality decisions and a stronger connection to the product.

When hiring for the C-suite, the importance of domain expertise varies by role. For Chief Product Officers, a deep passion and knowledge of the problem space is critical for setting vision. For engineering leaders (CTOs/VPs), specific domain experience is less important than relevant tech stack knowledge and transformation skills.

While it's valuable for PMs to learn to build, they shouldn't forget their primary value. Their superpower isn't writing production code, but deep product sense and user empathy. Embrace new skills, but hone your core strengths to avoid becoming a lesser engineer.

Ditch standard FANG interview questions. Instead, ask candidates to describe a messy but valuable project they shipped. The best candidates will tell an authentic, automatic story with personal anecdotes. Their fluency and detail reveal true experience, whereas hesitation or generic answers expose a lack of depth.

Instead of seeking a specific PM archetype (e.g., innovator, maximizer), focus on hiring individuals who bring unique perspectives, skills, or backgrounds. This approach builds a more resilient and versatile product organization, even if the new hire's style differs from the manager's.

The standard 'pod' ratio (1 PM per 6 engineers) infantilizes engineers and designers by removing their decision-making reps. Instead, Whatnot only hires PMs for specific, high-leverage needs, forcing other roles to build their own product muscle and raising the bar for adding PMs.