Skip to content

Product Manager: what the role asks for

Owns the problem space and outcomes for a product or area, deciding what to build and why. Combines customer research, data and business goals into priorities and a roadmap, and works with engineering and design through delivery. Communicates trade-offs to stakeholders.

Skill profile: Karnamo curated v1 (original, not ESCO-derived). It describes a typical role; individual employers differ, so always check the job description in front of you.

Core skills

Expected from day one. Gaps here usually decide whether you get to the interview.

  • Product Discovery

    target: deep / can teach others

    Finding out which problems are worth solving through research and validation.

    • Run five customer interviews about a real problem and write up the opportunities and what remains unproven (practice, free)
  • Product Roadmapping

    target: deep / can teach others

    Communicating product direction and sequencing around outcomes.

    • Turn a feature list into an outcome-based roadmap with goals, assumptions and what you would deliberately not do (practice, free)
  • Prioritization

    target: deep / can teach others

    Deciding what to do first using value, effort, risk and strategy.

    • Prioritise a real backlog with two different frameworks and explain where they disagree (practice, free)
  • Product Analytics

    target: deep / can teach others

    Measuring product usage and outcomes with metrics, funnels and cohorts.

    • Define a metric tree for a product you use: one north-star metric, inputs and guardrails (practice, free)
  • Stakeholder Management

    target: deep / can teach others

    Aligning expectations and communication with people who influence or are affected by your work.

    • Map the stakeholders of a current project by influence and interest and plan how to communicate with each (practice, free)
  • Communication

    target: deep / can teach others

    Conveying information clearly and listening effectively, in writing and speech.

    • Write a one-page memo of a complex topic for a non-expert and have someone summarise it back to you (practice, free)

Important skills

Expected within the first year; strong candidates show some already.

  • Requirements & User Stories

    target: solid, independent

    Capturing needs as clear, testable user stories and acceptance criteria.

    • Rewrite five vague requirements as user stories with testable acceptance criteria (practice, free)
  • UX Research

    target: solid, independent

    Planning and running qualitative and quantitative research with users.

  • A/B Testing & Experimentation

    target: solid, independent

    Designing and interpreting controlled experiments for product decisions.

    • Design an experiment on paper: hypothesis, primary metric, sample size, guardrails and decision rule (practice, free)
  • Go-to-Market

    target: solid, independent

    Planning how a product reaches and wins its target customers.

    • Draft a one-page launch plan for a product: segment, positioning, channels, success measures (practice, free)
  • Agile Delivery

    target: solid, independent

    Delivering iteratively with Scrum, Kanban and related practices.

Nice to have

Differentiators that help but rarely block.

  • Negotiation

    target: solid, independent

    Reaching agreements that work for both sides on price, scope and terms.

    • Getting to Yes (Fisher, Ury and Patton) (book)

Sample interview questions

  1. Behavioral

    Describe a time customer research contradicted your assumptions.

    Shows intellectual honesty: what you believed, what you learned and what you changed.

  2. Hiring manager

    How do you decide when to rely on data and when to rely on judgement?

    Shows understanding of what data can and cannot tell you, especially for new products with little data.

  3. Leadership

    How do you lead a team when you have responsibility for outcomes but no authority over the people?

    Shows influence through clarity of goals, evidence, trust and respect for others' expertise.

  4. Hiring manager

    How would you decide whether our product should say no to a large customer's feature request?

    A good answer reasons from strategy, the broader customer base and cost, and describes how to communicate a no respectfully.

  5. Technical / domain

    How would you define success metrics for a new onboarding flow?

    Link metrics to user outcomes, with leading and lagging indicators and guardrails, and say how you would avoid vanity metrics.

  6. Coding or case study

    Our subscription app has rising churn. Walk me through how you would diagnose it and what you would propose.

    Structure the problem: define churn, segment, combine quantitative and qualitative evidence, then propose testable actions.

All Product interview questions · Pick your own round and seniority

Related career moves

Roles whose skill profiles overlap most with this one. Overlap is a starting point for a conversation, not a recommendation.

Compare your own CV against Product Manager job postings with a transparent rubric.

Try the job-fit analyzer