Product Manager Job Description Template (2026)

A template built around outcomes, what product managers do all week, how to set pay without a federal benchmark, and questions for round one.

Copy this product manager job description, swap in your details and post it. It's free, and it's built around the outcomes a PM will own rather than a list of buzzwords. After the template: what the job involves, how to think about pay when federal data doesn't track the title, sample interview questions and tips for the post itself.

Product manager job description template

Job title: Product Manager [or Senior Product Manager / Technical Product Manager]

Location: [City, State / Remote / Hybrid, X days a week in office]

Reports to: [Head of Product / Director of Product Management / CPO]

About [Company]

[One or two sentences about your company and mission.]

About the role

We're hiring a product manager to own [our onboarding experience / the billing product / our mobile app] for [type of customer]. You'll work with a team of [X engineers and a designer] to decide what we build, why, and in what order, and you'll be measured on [activation rate / retention / revenue from the area]. In your first 90 days, you'll talk to at least [15] customers, learn our data, and ship one meaningful improvement with the team.

What you'll do

  • Run regular customer interviews and review support tickets, sales calls and usage data to find the problems worth solving.
  • Own the roadmap for [product area] and explain the reasoning behind every priority to leadership and the team.
  • Write short product briefs or PRDs that state the problem, the goal, the metric and what's out of scope.
  • Work daily with engineering and design to shape solutions, cut scope wisely and keep the team unblocked.
  • Define success metrics before launch and track them in [Amplitude / Mixpanel / Looker] after.
  • Plan and read experiments, such as A/B tests or staged rollouts, and decide what to keep.
  • Plan launches with [marketing, sales and support], including release notes and training.
  • Say no, clearly and kindly, to requests that don't fit the strategy, and explain why.

What you'll bring

  • [3+] years as a product manager, or in a role like engineering, design, analytics or consulting where you shaped what got built.
  • A track record of shipping products or features and showing their impact with numbers.
  • Comfort with product analytics, and enough SQL or tool skill to answer basic usage questions yourself.
  • Experience running customer interviews and turning what you hear into clear problem statements.
  • Strong written communication: briefs, updates and decisions people can follow without a meeting.
  • Experience working with engineers on trade-offs between scope, quality and time.

Nice to have

  • Experience in [B2B SaaS / fintech / marketplaces / our market].
  • A technical background, or experience with APIs and platform products.
  • Experience with pricing and packaging decisions.
  • Experience with [Jira / Linear], [Figma] and [Amplitude / Mixpanel].

Pay and benefits

[Salary range, e.g. $X to $Y per year, based on level and location]. [Equity or bonus, if any.] [Health, dental and vision coverage, retirement plan with match, paid time off.]

How we hire

Every candidate follows the same path. We start with a [30]-minute structured interview about past product decisions and how you work with engineering and design. Next is a [60]-minute product case: we share a real problem from our product (with sensitive details removed) and talk it through with you live. No unpaid take-home projects. Finally, you meet [the head of product, an engineering lead and a designer]. We'll decide within [10] business days and tell you why either way.

What a product manager does

A product manager decides what a team should build next and makes sure it actually solves a customer's problem. The work is part research, part prioritization and part communication. In a given week, a PM might sit in on three customer calls, rewrite a brief after an engineer finds a simpler approach, review last week's launch metrics, and explain to sales why a requested feature isn't on the roadmap yet.

PMs usually have no direct reports. They lead a group of engineers and a designer through clear goals and good reasoning, and they work closely with marketing, sales, support and leadership. The best product managers are known less for their ideas than for picking the right problem and getting a team to agree on it.

At a startup, the PM may be the first product hire, doing research, design input, analytics and launch work alone, often with the founder still making big calls. At a large company, PMs usually own one area of a bigger product, inside a structured planning cycle with product leads, design systems and data teams supporting them. Senior titles such as group PM or director add managing other PMs.

Skills and qualifications

SkillMust-have or nice-to-haveWhy it matters
Customer discoveryMust-haveBuilding the wrong thing well is still a waste.
PrioritizationMust-haveThere's always more to build than time allows.
Written communicationMust-haveBriefs and decisions keep the team aligned without extra meetings.
Product analyticsMust-haveProves whether a launch worked and where users drop off.
Working with engineering and designMust-haveGood trade-offs come from shared understanding, not handoffs.
Experiment designNice-to-have (must-have for growth roles)Separates real gains from noise.
SQLNice-to-haveLets the PM answer simple data questions without waiting.
Technical backgroundNice-to-have (must-have for platform or API products)Helps with estimates and technical trade-offs.
Domain expertiseNice-to-haveShortens ramp-up in complex markets like healthcare or finance.

There's no license or required credential for product management. Product managers come from engineering, design, analytics, marketing, consulting and support. If you require a computer science degree, you'll lose many strong candidates, so ask for evidence of shipped work instead.

Salary

The Bureau of Labor Statistics doesn't track product managers as a separate occupation, so there's no official U.S. median for this title. O*NET does list "Product Manager" among the reported job titles for Marketing Managers (11-2021.00). But that occupation is built around marketing programs, pricing and promotion, which is a poor match for most software product roles, so we don't think its wage figures are a fair guide here and we haven't quoted them.

To set a range, use your own pay bands, the salary ranges other employers post in your market for the same level, and what you pay engineers at the same level, since PM and engineering pay usually track each other. Then state the range in the post. A growing number of states and cities require pay ranges in job ads, and product candidates often skip posts without one.

Interview questions for product manager candidates

  • "Tell me about a product decision you made with incomplete data." Strong answers explain what they knew, what they didn't, how they reduced the risk (a small test, a staged rollout) and what happened.
  • "Activation dropped 8% after last week's release. What do you do?" Good candidates check the data first, look for a broken step or a tracking change, talk to engineering, and decide whether to roll back.
  • "Sales says a big customer needs a feature that isn't on the roadmap. How do you respond?" Listen for curiosity about the real need, weighing it against current goals, and a clear answer to sales either way.
  • "How would you measure success for a new onboarding flow?" The best answers name one primary metric, a guardrail metric and a time frame, set before launch.

Our full set of product manager interview questions includes product sense, execution and STAR questions, with what good looks like and a scoring rubric.

Writing tips for this role

  • Name the product area and the metric. "Owns self-serve onboarding, measured on week-one activation" draws people who've done that work.
  • Don't confuse product and project management. If the job is mostly schedules and status reports, use our project manager template instead. Mixing them confuses both groups of candidates.
  • Be honest about who decides. If a founder or GM sets the roadmap, say the PM "shapes and executes" it. Candidates will find out in the interview anyway.
  • Skip the long tools list. Jira and Figma skills take a week to learn. Spend the words on the problems instead.
  • Check the title variants. Candidates search for "product manager," "senior product manager" and "technical product manager." Pick the one that matches the level and scope.

Screening product manager candidates with AI

Product manager pipelines are often large and hard to sort by resume alone. NTRVSTA scores and ranks every resume against your job description, then runs a live first-round interview with an AI interviewer that candidates can take any time, on video or audio. The questions adapt to each answer, so a candidate who gives a shallow answer about metrics gets a sharper follow-up. STAR-based behavioral questions and soft-skill areas like communication and problem-solving are built in, and you can add your own product scenarios.

Your product lead gets a score breakdown, highlight clips and a shareable report, so the product case round goes to the right people. NTRVSTA has a published NYC Local Law 144 bias audit on our compliance page. For a wider look at tools, see the best AI interview software guide.

Questions

What's the difference between a product manager and a project manager?

A product manager decides what to build and why, and is judged on whether it helps customers and the business. A project manager makes sure a defined piece of work gets done on time and on budget. Product managers own the problem; project managers own the plan.

Should a product manager be technical?

It depends on the product. For APIs, developer tools or data platforms, a technical background is close to essential. For most customer-facing products, PMs need to understand trade-offs and talk with engineers comfortably, but they don't need to write code.

Should we give product manager candidates a take-home assignment?

A live case discussion usually works better. It shows how a candidate thinks and asks questions, and it respects their time. If you do use a take-home, keep it to about two hours, base it on a made-up problem, and tell candidates how it will be scored.

Want to see a live adaptive AI interview in action before your next PM search? Book a 20-minute demo or start a sample interview on your own. More templates are on our job descriptions page.

Sources

NTRVSTA
‍