Product Manager: A JD That Filters Out the 80% Mismatches
Product manager is the most JD-noisy role on earth — three companies will describe three different jobs under the same title. Here's a template that forces you to commit to which kind of PM you're hiring, written in editorial form with customization levers for the other archetypes.
"Product manager" describes at least four meaningfully different jobs: feature PM, platform PM, growth PM, and 0-to-1 PM. The same JD cannot recruit for all of them. The most common JD failure we see is to describe a feature-PM role using growth-PM language, which floods the funnel with the wrong candidates and signals to the right ones that the company doesn't know what it's hiring.
The template below commits to one archetype — feature PM — and is the starting point we use across product searches at TheHireHub. The Customize section at the end shows how to convert it for the other three archetypes.
What this JD filters for (feature-PM variant)
- Candidates who can run a customer-driven product process: discovery, prioritization, scoping, launch, iteration.
- Candidates who are strong on craft (writing, scoping, deciding) and quieter on stakeholder politics.
- Candidates with patience for building inside an existing product surface — not 0-to-1 hunters.
The template
Role summary
We're hiring a Product Manager to own the candidate-experience surface of our product. You'll partner with engineering, design, and customer-facing teams to identify the most valuable problems to solve, scope the work, ship it, and measure the result. This is a feature-PM role: you'll operate inside our existing product, in close partnership with PMM, customer success, and sales. You'll not be expected to launch a new product line in your first year.
What you will do
- Run discovery: customer interviews, support-ticket analysis, sales-call review, and quantitative segmentation. Synthesize into a prioritized problem list — not a feature list.
- Decide what ships: turn the problem list into a quarterly roadmap with explicit tradeoffs (what we are not doing, and why).
- Write tight specs: lightweight, decision-focused PRDs that engineering and design can execute against without 10 follow-up meetings.
- Lead launches: coordinate with marketing, sales, and support; write release notes; brief the customer-facing teams; own the post-launch result.
- Measure outcomes: define and instrument the success metric before launch — not after. Decide what success looks like and what would force a rollback.
- Be the customer voice in product reviews: bring real quotes, real video clips, real numbers — not gut feelings.
Must-haves
- Three or more years as a product manager (or in a closely adjacent role: strategy, founder, technical lead with product ownership).
- A demonstrated track record: a feature you shipped, why it mattered, what the result was, and what you'd do differently.
- Crisp written communication. We will ask for a writing sample.
- Comfort with quantitative tools — SQL or equivalent — well enough to answer your own questions, not blocked on a data analyst.
- A user-empathy reflex: you talk to customers regularly, not just as a project step.
Nice-to-haves
- Domain experience in B2B SaaS, fintech, marketplaces, or AI tooling.
- Technical depth — comfortable in the codebase, comfortable in design tools.
- Experience with pricing, packaging, or growth experimentation.
Compensation guidance
Mid-market 2026 PM bands typically run: US $145–200k base + 10–20% bonus + equity. UK £80–120k. India ₹35–60 lakh fixed CTC. The highest PM comp at this level goes to candidates with proven outcome ownership at scale — not feature-ship volume.
Success metrics — first 12 months
- Shipped at least three meaningful releases with a measured outcome — wins, losses, and learnings all counted.
- A clear pre/post comparison on the team's North Star metric for the surface they own.
- Customer-facing teams (sales, support) self-report that this PM has improved their visibility into product direction.
- Engineering self-reports that PRDs and prioritization from this PM are clearer and more decisive than before.
Interview rubric
- Customer and problem framing (30%): we walk a real customer scenario and watch how they prioritize, slice, and decide what not to build.
- Execution and scoping (25%): a structured exercise on turning a fuzzy problem into a one-week scope with explicit cuts.
- Communication (20%): a writing sample plus a verbal-decision exercise — can they tell us "the right call is X, here are the tradeoffs"?
- Domain and analytics (15%): comfort with the data and the domain-specific gotchas of your product space.
- Values and ownership (10%): how they handled their hardest project, with explicit follow-ups on what they got wrong.
Customize this template
- 0-to-1 PM: swap the discovery section for a market-sizing exercise, double the weight on judgment and ownership, and call out the pre-PMF context explicitly.
- Growth PM: replace the customer-interview emphasis with a funnel-instrumentation exercise; weight quantitative skill higher.
- Platform PM: replace the customer-interview emphasis with internal-stakeholder management; add an API-design judgment exercise.
- Decide your archetype before writing: ask "what does great look like 12 months from now?" — the answer dictates the JD shape.
Secure Your Competitive Edge with TheHireHub.ai
By harnessing AI through TheHireHub.ai, HR leaders can eliminate the pain of losing top talent, slash time-to-fill and vacancy costs, and drive organizational success. Visit thehirehub.ai today to schedule a demo and experience 70% faster hiring tailored to your needs. Transform recruitment from a cost center into a strategic advantage—start now.
Stop scrolling resumes. Start hiring.
TheHireHub's AI hands you pre-screened, ready-to-interview candidates in hours, no agency fees, no signup gauntlet.
Curious how this works inside a real product? Explore TheHireHub’s agentic AI recruiting and see how it compares.
Not sure how to write the perfect JD? Let AiRA craft it for you — free.
Sign up for a free trial to build your JD, get AI-matched candidates, and run your first search — all in minutes.
Start Free TrialFrequently Asked Questions
How do we know which PM archetype we are hiring for?
Ask: "What does great look like for this hire 12 months from now?" If the answer is "shipped X feature, customers love it" — feature PM. If it is "a new product line off the ground" — 0-to-1 PM. If it is "moved retention/activation/conversion" — growth PM. If it is "API/SDK partners onboarded" — platform PM. Write the JD that matches that 12-month picture.
Do we need a writing sample?
Yes. PMs ship via writing — PRDs, decision memos, launch notes, customer comms. A writing sample (their old PRD, even redacted) is the highest-signal artifact in the pipeline. Make it a soft requirement at the screening stage.
What's the cheapest filter for fit?
A 30-minute call walking a real recent decision they made. Senior PMs can name the alternatives they considered, the tradeoff that drove the call, and what they would do differently. Mid candidates often describe outcomes without the decision behind them. That gap is your filter.
