The reading room · Digna Legi
How to Hire a Product Manager
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Some advice is explicitly historical and updated, so the score reflects durable framing plus visible caveats rather than timeless validity of every tactic.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Norton’s PM hiring standard favors earned influence, judgment, technical fluency, product instinct, and shipped work over formal authority.
AI brief · Checked against source text
The main idea
A strong product manager is valuable precisely because the role is not automatically necessary: the organization can limp along without one, so the PM must prove leverage through judgment, translation, and execution. Norton’s hiring screen favors raw intelligence, technical fluency, product instinct, earned leadership, multi-perspective thinking, and evidence of having shipped, while his updates reject puzzle interviews in favor of structured work samples and situational problems.
Go a little deeper
Expendability changes the job
Norton’s sharpest role definition is negative: PMs are not indispensable in the way engineers, salespeople, or designers visibly are. That makes the PM’s authority contingent, not granted. The practical consequence is that hiring should look for people who can create coordination, judgment, and decision quality that other functions would not reliably produce on their own.
Technical fluency is not technical ownership
The technical-background requirement is narrower than simply preferring ex-engineers. Norton values technical fluency because it helps a PM translate requirements to engineers and explain complexity to nontechnical stakeholders. But he warns that former engineers can fail if they keep trying to own implementation decisions; the successful transition is from builder to product leader, not from coder to unofficial engineering manager.
Product instinct shows up in small decisions
Norton distinguishes product instinct from big strategic talk. The revealing test is whether a candidate notices problems, improvements, or future risks that feel obvious once said but were not already visible to the team. That makes the interview less about asking for polished opinions and more about seeing whether the candidate can improve the interviewer’s understanding of the actual product.
Cross-functional empathy needs real evaluators
The essay’s stakeholder advice is operational, not sentimental. Because PMs must represent absent perspectives, Norton recommends involving carefully selected representatives from engineering, design, marketing, and other relevant functions. The point is not unanimous approval; it is that each function is best placed to detect whether the candidate understands its pressures and can support its work.
A case from the article
Startup hiring punishes narrow fit
Norton contrasts Yahoo-style hiring with startup hiring. In a large company, a candidate can be acceptable because they match a specific, stable role. In a startup, that logic is dangerous because the work may change within months, so adaptability and generalist strength matter more than narrow role fit. The case illustrates why the same PM profile can be rational in one environment and wrong in another.
How the case is made
The case is made through hiring experience, interview heuristics, retrospective updates, and role-specific distinctions between startups and large companies.
Where the idea has limits
Several judgments are explicitly subjective, especially product instinct; Norton treats them as essential but hard to evaluate, and later revises older interview advice where industry practice changed.
A question to take away · from Digna Legi
Where does your hiring process actually test earned influence rather than merely rewarding confident product vocabulary?
What the original adds
The source includes many concrete interview questions for technical adaptation, product instinct, leadership, cross-functional empathy, and stakeholder work, plus a startup-versus-big-company hiring distinction.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.