Product Manager Hiring Guide for IT
PM hiring in IT staffing is messy because the title spans junior product owners (writing tickets) to senior PMs (owning P&L). Most candidates over-claim. The strong IT PM combines customer empathy, technical literacy, and ruthless prioritization. This guide tests for all three with concrete questions.
Key skills
Must-have
Customer discovery practice
Has done real customer interviews — at least 30+ in their career. Can describe what they learned.
Prioritization framework
Has used and can defend a prioritization framework (RICE, ICE, Kano, weighted shortest job first). Not "I prioritize by gut feel."
Technical literacy
Can have a substantive conversation with engineers about trade-offs without becoming the bottleneck. Not "I leave that to engineering."
Outcome ownership
Has owned a metric (activation, retention, revenue) end-to-end. Can describe the metric, the baseline, and the outcome.
Nice-to-have
Engineering or design background
PMs with prior eng/design experience consistently produce more shippable specs.
Domain depth
Fintech, healthtech, B2B SaaS — domain expertise reduces ramp dramatically.
Data fluency (SQL, A/B tests)
PMs who can pull their own data make 5x better decisions than those who wait for analysts.
Public speaking / storytelling
Can tell the product story to execs, sales, and customers. Underrated for senior PM roles.
Interview questions (7)
Walk me through a feature you killed. Why did you kill it, and what did you learn?
What to listen for
Real example with real reasoning. Vague answers = candidate has not killed enough features (most PMs ship too much).
How do you decide what NOT to build?
What to listen for
Cost-of-delay, opportunity cost, alignment to strategy. Not "I build whatever the customer asks."
Describe your last customer interview. What did you ask, what did you learn?
What to listen for
Specific person, specific questions, specific insights. Reveals if they actually do customer discovery.
A senior exec wants a feature you think is wrong. What do you do?
What to listen for
Asks why, presents data + alternative, escalates if needed, then commits. Not "I just build it" or "I refuse."
Tell me about a metric you owned. What was the baseline, what did you change, what was the outcome?
What to listen for
Specific numbers, specific interventions. Vague answers = candidate has not owned outcomes.
How do you write a PRD that engineers want to build from?
What to listen for
Problem first, then solution, then measurable success. Inclusion of out-of-scope. Not "I write user stories."
What is a product decision you made that you would change today?
What to listen for
Honest reflection. Strong PMs always have an example.
Evaluation rubric
Score each candidate against these weighted criteria. Total: 100%.
| Criterion | Weight | Signal |
|---|---|---|
| Customer discovery | 25% | Real interview practice. Specific customer insights influencing decisions. |
| Prioritization discipline | 20% | Has and can defend a framework. Says no often and well. |
| Outcome ownership | 20% | Has moved real metrics. Can attribute outcomes to specific decisions. |
| Technical literacy | 15% | Substantive conversations with engineers. Asks informed questions. |
| Communication / storytelling | 20% | Crisp PRDs, persuasive exec updates, clear customer narratives. |
Red flags
Has never killed a feature
Cannot name a specific customer insight that changed a decision
Defaults to "the engineers said it would take too long" for missed outcomes
Has never owned a measurable metric
Treats PRD writing as ticket writing
Apply this rubric automatically with CVPRO
Upload Product Manager CVs and let AI score every candidate against the same 42-point evidence rubric.
Try CVPRO Free