Problem judgement
Defines user, context, behaviour, impact, evidence, assumptions, alternatives, and uncertainty before selecting a solution.
Starts with a requested feature and treats stakeholder volume as proof of value.
Software, Product, Data & AI
Product Manager Job Description
A Product Manager helps a team decide which customer and business problems to solve, why they matter, what evidence supports the choice, and whether the delivered change produced the intended outcome.
Define the product, users, lifecycle stage, decision authority, delivery model, and commercial context before adapting this template.
Candidate-facing template
Edit the description for your organisation
Replace bracketed details, remove anything that is not genuinely required, and obtain the appropriate internal approval before advertising.
Ready-to-edit job description
Copying excludes all recruiter notes below.
Product Manager
- Location
- [Location and working arrangement]
- Employment type
- [Full-time or contract]
- Reports to
- [Product leader title]
About the role
[Company name] is looking for a Product Manager to guide [product, platform, or customer journey]. You will develop a clear understanding of users and organisational goals, frame and prioritise problems, align a cross-functional team, support delivery decisions, and evaluate whether changes create the intended value.
What you will be responsible for
- Build a current understanding of users, workflows, unmet needs, product performance, market context, and organisational constraints.
- Frame opportunities with evidence, intended outcomes, assumptions, dependencies, risks, and what the team still needs to learn.
- Prioritise work transparently and explain the trade-offs between customer value, strategic fit, effort, risk, and timing.
- Partner with design and engineering through discovery, solution choices, delivery, release, measurement, and iteration.
- Define outcome measures and combine behavioural, qualitative, commercial, operational, and technical evidence appropriately.
- Communicate product direction, decisions, changes, and uncertainty to users, delivery teams, leaders, and customer-facing colleagues.
- Maintain an appropriate roadmap without presenting uncertain future work as a fixed customer commitment.
What success looks like
- The team understands the problem, intended outcome, boundaries, and evidence behind priority work.
- Product decisions are traceable and change when new evidence invalidates an assumption.
- Released changes are measured against user and organisational outcomes, not completion alone.
- Stakeholders receive honest direction and uncertainty without a misleading feature promise list.
Essential qualifications
- Experience owning product decisions for a digital product, service, platform, or complex customer journey.
- Strong discovery, problem-framing, prioritisation, and written decision communication.
- Ability to work deeply with design and engineering without prescribing every implementation detail.
- Experience defining outcomes and interpreting both qualitative and quantitative evidence.
- Commercial and organisational judgement across value, cost, risk, feasibility, and timing.
- Ability to manage disagreement and maintain clarity without relying on positional authority.
Preferred qualifications
- Experience with the relevant user group, domain, product lifecycle, or regulated setting.
- Working knowledge of experimentation, analytics, research, accessibility, or service design.
- Experience launching a new product, improving an established one, or retiring unsuitable functionality.
Tools and working knowledge
- Product planning, discovery, research, and documentation tools
- Analytics, experimentation, feedback, support, and customer evidence sources
- Delivery, design, communication, and roadmap platforms used by the team
Compensation and benefits: [Add the approved range and currency, bonus or equity if relevant, equipment, leave, development support, and local benefits.]
[Company name] is committed to accessible recruitment and product experiences and will consider reasonable adjustments in line with applicable local requirements.
How to apply
Apply through [application method] with examples that explain the product problem, evidence, your decisions, cross-functional contribution, trade-offs, and measured outcome.
Performance expectations
What good performance looks like
Use these outcomes to replace vague activity lists with the evidence the hiring manager expects to see after the person joins.
Priority decisions connect user evidence, organisational strategy, technical reality, risk, and an explicit outcome.
Discovery reduces important uncertainty before the team commits disproportionate delivery effort.
Roadmap communication distinguishes direction, committed work, hypotheses, dependencies, and unresolved choices.
Post-release review changes later decisions and does not stop at celebrating shipment.
Hiring-manager intake
Questions to settle before advertising
Record specific answers so sourcing, screening, and interview decisions use the same definition of the role.
- 1
Which product, users, markets, lifecycle stage, and business model will this person own?
- 2
What decisions can the Product Manager make and where do product, engineering, design, commercial, or executive leaders decide?
- 3
How are user research, analytics, product operations, and technical discovery supported?
- 4
Which outcomes matter and how dependable is the current product evidence?
- 5
What customer commitments, regulatory constraints, platform dependencies, or technical risks shape priorities?
- 6
What must be clearer or materially better after the first six months?
Evaluation criteria
Evidence to use in a Product Manager scorecard
Agree the criteria before interviews begin, then score examples against the same evidence standard.
Prioritisation
Makes trade-offs explicit across outcome, strategy, evidence, effort, risk, opportunity cost, and sequencing.
Uses a scoring formula mechanically or changes priority for the loudest stakeholder without explaining the decision.
Cross-functional leadership
Creates shared context, invites expertise, resolves decisions, protects team focus, and owns product choices without micromanaging craft.
Acts mainly as a requirements messenger or claims sole credit for a team outcome.
Outcome learning
Defines expected change, measurement and limitations before release, then uses the result to continue, adapt, or stop.
Reports output, adoption, or a favourable metric without checking whether the intended problem improved.
Structured interview
Product Manager interview questions and strong signals
Ask the same core questions in the same order, then use follow-ups to understand the candidate’s individual contribution.
1
Tell me about a product request you decided not to build.
Strong answer signal
Understands the underlying need, considers evidence and alternatives, communicates the trade-off, and shows the later outcome.
2
Describe a launch that did not create the outcome you expected.
Strong answer signal
Owns the assumption, checks measurement and execution, learns from evidence, and makes a proportionate next decision.
3
How do you work with engineering when feasibility changes?
Strong answer signal
Revisits the outcome and constraints, explores options with engineers, updates trade-offs, and communicates uncertainty honestly.
4
Walk me through a difficult prioritisation decision.
Strong answer signal
Names competing value, evidence, cost, risk, people affected, opportunity cost, decision owner, and what would trigger reconsideration.
Related titles
Check the scope behind the title
Product Owner — often focuses more on backlog clarity and delivery-team decisions, though some organisations use it as a Product Manager equivalent.
Technical Product Manager — usually requires deeper platform, API, data, infrastructure, or integration context.
Product Marketing Manager — focuses on market understanding, positioning, enablement, launch, and adoption rather than owning the product delivery decision.
Common hiring mistakes
Problems to remove before publishing
Writing the role as a backlog administrator while expecting strategic product leadership.
Holding the Product Manager accountable for outcomes without access to users, data, engineering capacity, or decision authority.
Requiring exact industry experience when the transferable product problem, user complexity, or regulatory context is more relevant.
Using one interview case to reward confident presentation while ignoring evidence, uncertainty, collaboration, and learning.
Continue the hiring workflow
Related roles and recruiter resources
Related job descriptions
Helpful recruiter resources
Source and review notes
How this template was prepared
- Language
- International English
- Prepared by
- ATZ CRM Editorial Team
- Review
- ATZ CRM Recruitment Editorial Review
- Last reviewed
- 2026-08-04
O*NET: Project Management Specialists
Reference for occupation tasks, knowledge, skills, abilities, and work activities.
ESCO: occupations and skills
Reference for internationally recognised occupation and skills terminology.
Qualifications, compensation, licences, working conditions, and equal-opportunity wording must be checked for the role and location before use.
Recruiter questions
Product Manager job description FAQs
What should a Product Manager job description include?
Explain the product and users, lifecycle stage, problems and outcomes owned, decision authority, cross-functional model, evidence available, constraints, and how success will be evaluated.
What is the difference between a Product Manager and a Project Manager?
A Product Manager usually owns problem, priority, value, and product-outcome decisions. A Project Manager usually coordinates scope, plan, dependencies, resources, risk, and delivery. Some work overlaps, so define the actual responsibility.
Should Product Manager candidates complete a case study?
A proportionate case can reveal problem framing and communication, but avoid unpaid work on a live company problem. State the evidence being assessed, provide equal preparation, and combine it with past-work examples.