Role overview
A Product Manager (PM) owns the what and the why of what gets built — and is responsible for the outcomes those decisions produce. The role looks deceptively similar from one company to the next, but the actual job varies enormously by stage, surface area, and organizational maturity.
Match the candidate to the shape of PM work at your company, not the title. A PM from a 5,000-person org is rarely ready for the ambiguity of a 30-person company, and vice versa.
Job criteria
- Track record of shipped products with documented outcomes (metrics moved, customer adoption, revenue)
- Judgment under ambiguity — evidence of starting from a vague problem and reaching a shipped answer
- Comfort working directly with engineering and design, not as a relay
- Strong written communication — most PM artifacts are written
- For senior+: track record of setting product strategy, killing or descoping work, owning roadmaps
- Domain or persona overlap with your product (user-type fit usually matters more than feature-area fit)
What to screen for
- Outcomes, not outputs. "Shipped feature X" is not a signal. "Shipped feature X, which moved metric Y from Z to W" is.
- Original thinking. Read their cover letter and screening answers. Most PM applicants have the same template — the candidate who actually has a point of view stands out instantly.
- Decision pattern. Look for evidence of not shipping things — descoping, killing initiatives, saying no. Most weak PMs cannot point to a single "no."
- Stage match. Series A PMs and Big-Tech PMs have very different toolkits. Read for the work, not the logo.
- Cross-functional fluency. Resumes that lean engineering or design are usually a better signal than resumes that lean MBA case study.
Red flags
- Resume reads like a meeting calendar — "led syncs," "facilitated discussions," "drove alignment" — without any artifact attached
- No metrics, ever. Either they did not measure outcomes or they did not own them.
- Career arc that moved up titles without the responsibility shape changing
- "Product visionary" framing in the resume
- Generic resume that does not engage with your product, market, or domain
Resume keywords
shipped, product strategy, roadmap, discovery, PRD, OKRs, north star metric, user research, customer interviews, A/B testing, experimentation, conversion, retention, activation, growth, 0 to 1, 1 to N
Interview questions
- Walk me through a product you shipped end-to-end. What was the metric, and how did it move?
- Tell me about something you killed or descoped. Why, and how did the team take it?
- What is a product decision you made that you got wrong? What did you change next time?
- How do you decide between two roadmap items when both are good?
- We are at <stage / size>. Where in your career has the shape of work been most similar?
- Pick a product you use daily and tell me one thing you would change about it. Walk me through how you would validate that.