Sign in
PapaHR · Mike Pritula Academy · Roles

Product Manager: Role Profile, KPIs and Interview Questions

This page covers Product Manager responsibilities, key performance indicators (KPIs) and hiring tools. Use it to hire someone who turns customer problems into useful, profitable product improvements.

Build the profile for your company Open in PapaHR for free →

Job profiles, hiring, onboarding and reviews are in PapaHR. Free for up to 25 employees.

  1. Take the profile below or build your own with the builder.
  2. In PapaHR the profile turns into a job ad, an onboarding plan and probation goals.
  3. After 90 days, review the person against the same KPIs and competencies.

Job profile

Why the role exists

Develop a product that delivers customer value and makes money for the business.

Result in a year

The business understands its target customer and measures product value and gross profit. The team prioritizes changes by expected impact, checks results after launch and delivers the agreed product development plan.

Place in the structure

  1. Reports toHead of Product, or the owner in a small business.
  2. Direct reportsUsually none; the makeup of a dedicated product team varies.
  3. Works withOwner — product goals, budget and decision authority, Developers — solution options, effort and constraints, Designer — clear, usable customer journeys, Software tester — quality of core user journeys, Marketing — target audience, promises and acquisition, Sales — reasons customers buy or decline, Support — recurring customer difficulties, Accountant — product revenue and direct costs
Key result areas
  1. Product financial performance — Gross profit target attainment: revenue minus direct product costs100% of the quarterly product gross profit target.
  2. First value for new customers — Activation target attainment: share of new customers reaching first value100% of the new customer activation target.
  3. Customers returning to the product — Retention target attainment: share of customers repeating a valuable action100% of the customer retention target.
  4. Conversion to payment — Paid conversion target attainment: share of trial customers making their first payment100% of the first payment conversion target.
  5. Successful completion of the core task — Task success target attainment: share of started journeys delivering value100% of the core task success target.
Requirements

Experience: Experience developing products and measuring results after changes launch.

Formal: No specific degree required; demonstrate sound decisions and verified results.

Should know

  • Methods for researching customer problems and behavior.
  • The customer journey from discovery to payment.
  • Principles of measuring activation, retention and conversion.
  • Differences between revenue, gross profit and costs.
  • Limitations of experiments with small user numbers.
  • Core stages of development and product quality testing.

Should be able to

  • Ask about past behavior without leading the customer.
  • Check metric calculations in a spreadsheet.
  • Compare the value, cost and risks of possible solutions.
  • Define a testable assumption and a stopping condition.
  • Agree priorities within the team's available time.
  • Describe tasks and acceptance criteria clearly.
Competencies at three levels

Customer understanding

Finds problems customers are willing to pay to solve.

  1. Follows an interview plan and records customer actions and difficulties.basic
  2. Separates feature requests from underlying problems and checks multiple sources.solid
  3. Identifies promising customer segments and redirects the product based on their behavior.strong

Data reasoning

Distinguishes product improvements from random changes in numbers.

  1. Calculates metrics using agreed definitions and spots missing data.basic
  2. Compares equivalent groups, investigates changes and checks alternative explanations.solid
  3. Establishes outcome measurement, challenges false conclusions and guides evidence-based decisions.strong

Prioritization

Focuses limited team time on the most valuable changes.

  1. Compares ideas by goal, expected value and effort.basic
  2. Considers uncertainty, dependencies and the cost of deferring other work.solid
  3. Revises direction when evidence changes and builds agreement on difficult decisions to decline work.strong

Commercial judgment

Connects customer value with business revenue and costs.

  1. Distinguishes revenue from profit and gathers cost estimates for changes.basic
  2. Estimates payback and checks how pricing affects profit and retention.solid
  3. Chooses growth opportunities based on segment profitability and budget constraints.strong

Team alignment

Aligns development, sales and support around customer outcomes.

  1. Describes the problem and clarifies constraints with team members.basic
  2. Resolves disagreements through shared goals and records decisions and owners.solid
  3. Coordinates complex changes across teams and prevents conflicting customer promises.strong

Assumption testing

Reduces spending on solutions that will not deliver customer value.

  1. States an assumption, an expected signal and a way to test it.basic
  2. Chooses a low-cost test and sets success criteria and limitations upfront.solid
  3. Tests the riskiest assumptions first and stops investment when evidence disproves them.strong
Builder

Build the profile for your company

Tick what this person does at your company. On the right is the ready profile: copy it or open it in PapaHR.

Product Manager

Develop a product that delivers customer value and makes money for the business.

Duties
  1. Identify the task customers use the product to complete.
  2. Interview customers about actual purchases and product use.
  3. Find where users fail to get value.
  4. Agree product goals and ways to measure results.
  5. Estimate expected profit, costs and risks of changes.
  6. Set priorities and explain why ideas are declined.
  7. Test assumptions before investing in full development.
  8. Describe the problem, expected outcome and acceptance criteria.
  9. Coordinate releases with development, sales and support.
  10. Compare launch results with baseline measures and targets.
  11. Decide whether to expand, revise or disable a change.
  12. Test new prices and subscription plan options.
  13. Research demand before entering a new customer segment.
  14. Compare alternatives across different user groups.
  15. Arrange prototype testing with prospective users.
  16. Develop integrations with external services.
  17. Train sales on new product capabilities and limitations.
  18. Prepare decisions to retire features customers no longer need.
Open the profile in PapaHR

Product Manager KPIs

  1. Product gross profit target attainment — Actual product gross profit / target gross profit × 100%. Mistake: Treating revenue as profit and ignoring direct product costs.weight 30% · quarter
  2. Activation target attainment — Actual activation / activation target × 100%. Mistake: Counting a login as activation instead of the first valuable outcome.weight 20% · month
  3. Retention target attainment — Actual retention / retention target × 100%. Mistake: Counting a login as a return to a valuable action.weight 25% · month
  4. Paid conversion target attainment — Actual paid conversion / paid conversion target × 100%. Mistake: Counting unpaid invoices as first payments.weight 15% · month
  5. Core task success target attainment — Actual core task success / task success target × 100%. Mistake: Excluding failed attempts and inflating the success rate.weight 10% · month
Calculator

Work out the KPI bonus

Enter how much of each target was met, in percent, and the bonus at 100%. You can change the weights.

KPIWeight, %Achieved, %Share
Product gross profit target attainment
Activation target attainment
Retention target attainment
Paid conversion target attainment
Core task success target attainment
KPI total
Bonus
Sum of weights

The weights are an example. They should add up to 100%.

Interview questions

Scorecard

Run the interview and get the result

Score each answer from 1 to 5 and the total is worked out by competency. Keep this page open on your phone during the interview.

Customer understanding

Tell us how you discovered why customers stopped using a product. What did you ask, change and achieve?

✓ Listen for: A specific customer group, behavioral questions, a verified cause and the outcome.

⚑ Red flag: Invented the reason without speaking to customers who left.

Describe a feature request that concealed a different problem. How did you uncover it, and what happened next?

✓ Listen for: Recent usage explored, problem verified, a better solution and customer feedback.

⚑ Red flag: Sent every customer request straight to development.

Data reasoning

Describe a launch followed by metric growth. How did you check what caused it, and what did you decide?

✓ Listen for: A baseline, comparable groups, alternative causes checked and a cautious conclusion.

⚑ Red flag: Attributes every improvement after launch to their feature.

When did a data error affect your product decision? How did you find it, correct it and check the consequences?

✓ Listen for: Error source, recalculation, a revised decision and prevention of recurrence.

⚑ Red flag: Never checks source data and blames the analyst.

Prioritization

Describe choosing between a major customer's request and an improvement for most users. What did you compare, decide and achieve?

✓ Listen for: Revenue, reach, effort, risks and consequences of the chosen approach.

⚑ Red flag: Always chooses the loudest customer without assessing consequences.

Tell us when new evidence made you cancel a planned feature. How did you explain it and use the freed time?

✓ Listen for: New evidence, a clear explanation and a more valuable task.

⚑ Red flag: Continues solely because the feature was already promised.

Commercial judgment

Describe a feature whose payback you estimated. Which revenue and costs did you include, and what happened after launch?

✓ Listen for: Development and running costs, expected revenue, assumptions and comparison with actual results.

⚑ Red flag: Treats all additional revenue as profit and ignores running costs.

Describe a pricing or subscription plan change you worked on. How did you assess risks, test it and measure results?

✓ Listen for: Personal contribution, customer response and effects on payments, retention and profit.

⚑ Red flag: Judges success only by the price increase.

Team alignment

Describe a disagreement with a developer about solving a customer problem. How did you agree, and what changed for users?

✓ Listen for: Shared goal, technical constraints, alternatives considered and a verified outcome.

⚑ Red flag: Pushes a fixed solution without discussing constraints.

What did you do when sales promised an unapproved feature? How did the situation end for the customer and team?

✓ Listen for: Commitments clarified, an agreed customer response and rules for future promises.

⚑ Red flag: Quietly adds the promise to the workload, breaking other commitments.

Assumption testing

Tell us how you tested demand before developing a feature. What signal did you seek, find and act on?

✓ Listen for: A risky assumption, a low-cost test, success criteria and an evidence-based decision.

⚑ Red flag: Treats colleagues' approval of an idea as proven demand.

Describe a test that disproved your favorite idea. What did you measure, how did you react and what happened next?

✓ Listen for: Criteria set upfront, acceptance of negative results and stopping or revising the idea.

⚑ Red flag: Changes success criteria after failure to justify continuing.

Score at least one answer and the result shows up here. ·
Track candidates in PapaHR

Test task

Choose the next improvement for an appointment booking service · 2 hours

Practice exercise: all figures are fictional. A small business sells an appointment booking service. In the completed month, 200 businesses signed up; 120 created their first booking within seven days. The activation target is 75%. All 200 businesses have finished their trial; 40 made their first payment. The conversion target is 25%. In a separate group of 100 businesses from the previous month, 70 created a booking in week four. The retention target is 80%. Monthly revenue is $4,000, direct costs are $1,000 and the gross profit target is $3,500. Support received 24 requests about difficult schedule setup, 10 about reminders and 6 about report exports; a customer could submit multiple requests. Three ideas are available: simplify setup in 5 development days, add reminders in 8 days or build reports in 3 days. Estimates are preliminary; 8 development days are available. Prepare a memo of up to two pages: calculate the four metrics and their target attainment; choose a problem to investigate; identify missing data and customer interview questions; propose a low-cost test, success criterion and stopping condition; explain the next development priority and why you declined the other ideas. Label assumptions. No access to real customers or working product is required.

How to assess it

  • Correct activation, conversion, retention, gross profit and target attainment calculations.
  • Support request counts are not treated as affected customer counts.
  • Assumptions are separated from facts; missing data is identified.
  • Customer questions explore past actions and reasons for difficulties.
  • The test measures behavior and includes success and stopping criteria.
  • Priorities reflect value, cost, uncertainty and available development time.
  • The explanation is clear; additional profit is not presented as proven.

Ready job ad

Product Manager at [company]

We develop [product] for [customers]. We need someone who turns customer problems into measurable product improvements.

What you will do

  • Research why customers choose the product or leave.
  • Find obstacles to first value and payment.
  • Agree product goals with [manager].
  • Set priorities based on profit and team capacity.
  • Test ideas before full development.
  • Explain customer problems and expected outcomes to the team.
  • Measure impact after launch and adjust decisions.

What we need

  • Product development experience with results you can explain.
  • Ability to interview customers without pushing your idea.
  • Ability to calculate usage, payment and retention metrics.
  • Understanding of product development and running costs.
  • Ability to agree priorities with development, sales and support.
  • Willingness to stop ideas when evidence does not support them.

What we offer

  • Pay: $[salary]; review based on [conditions].
  • Working arrangement: [format], [city]; hours: [schedule].
  • Product team: [team composition]; reporting to: [manager].
  • Priority decisions: [decision authority].
  • Customer and data access: [access conditions].
  • Development support: [training and budget].

In PapaHR this text becomes a job opening with a careers page and a candidate pipeline.

90-day onboarding plan

Before day one

  1. Send a product overview and initial meeting schedule.HR
  2. Prepare product goals, metrics and unresolved problems.Manager
  3. Set up product, analytics and support request access.IT

Day one

  1. Discuss authority over priorities, budgets and customer promises.Manager
  2. Demonstrate the journey from signup to first value.Mentor
  3. Complete the core product journey and record difficulties.New hire

First week

  1. Review support requests, lost sales and current customer promises.New hire
  2. Arrange introductions to development, sales and support.Mentor
  3. Check data sources and core metric definitions.New hire
  4. Choose initial customer interviews and agree their purpose.Manager

30 days

  1. Conduct interviews and document verified problems in the chosen segment.New hire
  2. Record baseline product metrics and measurement gaps.New hire
  3. Agree the priority problem and next month's goals.Manager
  4. Assess how well the new hire collaborates with teammates.HR

60 days

  1. Test the priority assumption using an affordable method.New hire
  2. Agree the decision and development scope based on test results.Manager
  3. Prepare impact measurement and conditions for stopping the change.New hire
  4. Check that tasks and acceptance criteria are clear to everyone.Mentor

90 days

  1. Review the first change after the agreed observation period.New hire
  2. Prepare subsequent priorities with value and cost estimates.New hire
  3. Assess decisions, results and independence against probation period goals.Manager
  4. Document the probation period review and further development plan.HR

Probation period goals

  1. Understand target customer problems.Example target: by day 30, complete 6 interviews, identify 3 problems and attach supporting evidence.
  2. Make product outcomes measurable.Example target: by day 30, agree definitions, sources and baselines for all 5 role profile metrics.
  3. Test a risky assumption before major spending.Example target: by day 60, complete 1 test with predefined criteria and a justified decision.
  4. Take a small change from problem selection to impact assessment.Example target: by day 90, assess 1 change using an agreed metric; aim for 100% of the improvement target. Record no improvement or deterioration too.

Career path

Associate Product Manager

Researches a specific problem and manages small changes with a mentor's support.

To move up: Independently take a change from problem validation through to outcome measurement.

Product Manager

Owns outcomes for a product or distinct area and sets team priorities.

To move up: Demonstrate sustained improvement and sound allocation of resources across tasks.

Senior Product Manager

Handles greater uncertainty, leads a major product area and develops junior colleagues.

To move up: Align several areas, develop people and take responsibility for a shared budget.

Head of Product

Sets product direction, allocates budgets and manages Product Managers.

To move up: Expand responsibility to several products when profitability and team readiness support it.

Questions for a 1:1 meeting

  1. Which customer problem matters most now, and what evidence supports that?
  2. What stops new customers from getting their first value?
  3. Which metric changed, and which causes have we already checked?
  4. Which idea should we drop to free up team time?
  5. Which assumption could make the current plan unprofitable?
  6. Where do customer promises exceed the team's capacity?
  7. Which decision from the last launch would you revisit?
  8. What authority or data do you need for your next decision?

Mistakes in hiring and managing

  1. Hiring for terminology and an impressive list of shipped features.
    Better: Ask about the problem, personal decisions, measured impact and disproved assumptions.
  2. Assessing Product Managers only by completed task counts.
    Better: Agree customer value and profit metrics, then check results after launch.
  3. Demanding growth while blocking customer contact and changes to priorities.
    Better: Provide access to customers, data and decisions within agreed boundaries.
  4. Treating every major customer request as mandatory development work.
    Better: Check broader demand, support costs and effects on other priorities.
  5. Punishing tests that disprove an idea before development.
    Better: Assess test quality and resources saved; document learning for future decisions.
HR in money

What a bad hire costs: Product Manager

The same calculation as in PapaHR «HR in money»: the cost of hiring plus the salary for the months the new hire worked at half capacity.

One leaver
A year

In the first months a new hire delivers about half the result, so the company pays the other half of the salary for learning. In PapaHR the calculation uses your real leavers.

Questions and answers

What is the difference between a Product Manager and a Project Manager?

A Product Manager decides which customer problem to solve and what outcome the business needs. A Project Manager organizes agreed work, including timelines, people and dependencies. A small business can combine the roles if responsibilities are clear and customer research has dedicated time.

Does a small business need a Product Manager?

The role helps when a business regularly chooses how to develop its product and poor choices are expensive. The owner may handle this work initially. A dedicated role makes sense when customer research, priorities and outcome measurement need ongoing attention.

Does a Product Manager need to code?

For many products, understanding development constraints and discussing options with the technical team is enough. Defining problems, checking data and assessing outcomes matter more. For a technically complex product, specify the depth of knowledge required.

How do you assess a Product Manager when user numbers are low?

Review interview quality, evidence of customer problems and decisions from small tests. Percentages can fluctuate sharply with few users, so examine individual usage cases too. Avoid demanding firm proof of growth before enough data exists.

Which KPIs suit a Product Manager?

Choose measures suited to the product's stage: first value, retention, paid conversion and gross profit. Agree the employee's decision authority and how long impact should take to appear. Feature counts help track work but do not demonstrate customer value on their own.

Hire, onboard and review in one system

PapaHR is free for up to 25 employees: job profiles, openings, onboarding, goals, 1:1 meetings and reviews.

Open the profile in PapaHR I have an account

Similar roles