Branxl Academy

Career Hub

Product Management

Overview

Product managers decide what gets built and why. They are the connective tissue between customer problems, business goals, and engineering delivery. A PM does not manage developers; they align developers, designers, data analysts, and stakeholders around a shared understanding of the problem worth solving. In smaller companies a PM owns the full product lifecycle. In larger organisations they specialise into growth, platform, or core product.

What does the Product Management role involve?

  1. Running customer discovery interviews and synthesising insights into opportunity areas.
  2. Writing product briefs, requirements documents, and user stories.
  3. Prioritising the backlog using frameworks like RICE or ICE.
  4. Facilitating sprint planning, backlog refinement, and retrospectives.
  5. Defining success metrics and running experiments.
  6. Presenting roadmaps to senior stakeholders and managing scope trade-offs.
  7. Unblocking engineering through timely decisions on ambiguous requirements.

Skills Required

  1. Discovery and research: user interviews, survey design, usability testing.
  2. Prioritisation frameworks: RICE, ICE, MoSCoW, opportunity scoring.
  3. Metrics thinking: defining leading and lagging indicators, setting up dashboards, reading A/B test results.
  4. Communication: writing clear briefs, running focused meetings, giving feedback on design and engineering work.
  5. Stakeholder management: navigating competing priorities from sales, marketing, engineering, and leadership.
  6. Basic data literacy: SQL to self-serve simple queries, understanding statistical significance in experiments.

UK Salary Range

  • Entry level APM / junior PM (0-2 years): £28,000 to £40,000. Structured APM programmes at large tech companies pay at the higher end and include comprehensive training. Smaller scale-up junior PM roles may pay less but give faster autonomy.

  • Mid-level PM (2-5 years): £50,000 to £75,000. Ownership of a product area with cross-functional team. London salaries skew higher.

  • Senior PM (5+ years): £75,000 to £110,000. Principal PM and Group PM at larger companies reach £120,000 to £150,000 with equity.

  • Note: PM salaries in London's fintech sector (Revolut, Monzo, Wise) are among the highest in the UK market outside US-headquartered companies. Equity can represent a significant component of total compensation at growth-stage companies.

UK Job Market

  1. The UK PM market is concentrated in London and major tech hubs (Manchester, Bristol, Edinburgh).
  2. Large tech companies run structured APM programmes (Google, Meta, Microsoft, Amazon, Monzo, Deliveroo).
  3. These are highly competitive but provide the best training.
  4. Outside of APMs, many junior PMs come from adjacent roles: business analyst, data analyst, UX designer, or customer success.
  5. A strong narrative about why you are transitioning and evidence of product thinking matters more than a formal PM background.

Who This Career Path Is For

  1. People who enjoy understanding problems more than building solutions.
  2. Those who can hold ambiguity without needing certainty before making decisions.
  3. Communicators who can translate between technical and non-technical teams.
  4. People moving from BA, UX, data, or customer success roles who want to own outcomes, not just deliverables.

How to Get Started

Phase 1: Product fundamentals (weeks 1-4)

  • Read Inspired by Marty Cagan and The Mom Test by Rob Fitzpatrick.
  • Understand the difference between outputs (features shipped) and outcomes (behaviour changed).
  • Study three products you use daily: what problems do they solve, who are they for, and what would you change?.

Phase 2: Discovery and validation (weeks 5-8)

  • Run five informal customer discovery interviews on a problem you find interesting.
  • Write up the synthesis: what patterns emerged, what surprised you, what question you would ask next.
  • Practice writing a problem statement and a hypothesis.

Phase 3: Prioritisation and delivery (weeks 9-14)

  • Shadow an agile team if possible (many companies have open days).
  • Build a mock backlog for a real product you are improving.
  • Apply RICE scoring.
  • Write five user stories with acceptance criteria.
  • Learn how to read a basic analytics dashboard.

Phase 4: Execution and communication (weeks 15-20)

  • Build a complete product case study: problem statement, research summary, solution hypothesis, metrics plan, and a retrospective of what you would do differently.
  • This becomes your primary portfolio artefact.

Deep guidance

Build Your Portfolio

The product case study

  • One strong case study is the PM portfolio.
  • It should answer: what problem did you find, how did you validate it, what did you decide to build, how did you measure success, and what did you learn?.
  • Structure of a strong case study: 1.
  • Context: the product, the users, the business goal 2.
  • Discovery: how you identified the problem (interviews, data, observation) 3.
  • Synthesis: the key insight that informed your decision 4.
  • Solution: what you decided to build and what you explicitly decided not to build 5.
  • Success metrics: how you would know if it worked 6.
  • Outcome: what actually happened (or what you predict would happen for hypothetical projects) 7.
  • Retrospective: what you would do differently.
  • Strong version: Real user quotes from your research.
  • A clear "we chose this over that because..." decision rationale.
  • A metric that moved (or a prediction with a basis).

Weak version: "I identified a problem and built a feature." No evidence of discovery, no explanation of trade-offs, no measurement plan.

Where to publish

  • Notion public page, Medium article, or a personal portfolio site.
  • Keep it under 1,500 words plus images.
  • Hiring managers read quickly.
  • Make the insight visible in the first two paragraphs.
How to Apply

Getting your first PM role

  • Most junior PMs come from adjacent roles.
  • If you are in BA, data analysis, customer success, or UX, frame your experience as product thinking in disguise.
  • Describe moments where you influenced what got built, not just how.

APM programmes

  • Google, Microsoft, Monzo, Deliveroo, and several other companies run structured APM cohorts.
  • Applications typically open in September for roles starting the following year.
  • They are competitive but well worth applying to.
  • Research what each company values in PMs.

Cover letters

  • PM cover letters should demonstrate product thinking, not job enthusiasm.
  • Write a brief observation about one thing you would improve in their product and why.
  • Show you have used it and thought critically about it.

Typical process

  • Application screening.
  • Product case study (take-home: analyse a product and recommend an improvement).
  • Interview: walkthrough of your case study with live questions.
  • Final round: a metrics or prioritisation exercise and culture fit.
Interview Preparation

Common PM interview questions

  • "Tell me about a product you love and what you would improve." Do not choose the company's own product unless you have a strong specific take.
  • Choose something you have thought deeply about.
  • Structure: what problem it solves, for whom, what the current limitation is, your proposed improvement, how you would measure success.
  • "How would you prioritise a backlog with five competing features?" Walk through a framework: first clarify the strategic goal this quarter.
  • Then score each feature using RICE (Reach, Impact, Confidence, Effort).
  • Acknowledge that frameworks are inputs to judgment, not replacements for it.
  • **"A metric dropped 20 percent.
  • Walk me through your response."** First validate the data.
  • Then segment by user type, platform, geography.
  • Check for coincident changes.
  • Form a hypothesis.
  • Design an experiment or a qualitative investigation.
  • "How do you handle disagreement with an engineer about scope?" Listen first.
  • Understand the constraint.
  • Look for a smaller iteration that proves the hypothesis before committing to full scope.
  • Escalate only if the disagreement blocks delivery and cannot be resolved at team level.

Frameworks to know

  • Jobs-to-be-done.
  • Opportunity solution tree.
  • North star metric framework.
  • RICE prioritisation.
  • Product-market fit survey.
Common Mistakes to Avoid

Mistake 1: Talking about features instead of problems

  • The most common failure in PM interviews and case studies.
  • A PM who leads with "I built a search feature" rather than "users could not find what they needed, which cost the business 12 percent of sessions" has not demonstrated PM thinking.

Mistake 2: No metrics

  • Every product decision should have a measurable expected outcome.
  • If your case study has no metrics and no measurement plan, it looks like a design exercise rather than a product exercise.

Mistake 3: Trying to learn PM from books alone

  • Product thinking is learnt by doing.
  • Build something, even a small side project.
  • Run real customer interviews.
  • The frameworks are context for interpreting practice, not substitutes for it.

Mistake 4: Skipping discovery in case studies

Candidates often skip from "I saw a problem" to "I built a solution." The discovery section — how you validated the problem was real and worth solving — is what separates strong PM candidates.

Mistake 5: Not preparing for metrics and analytical questions

  • Modern PM interviews consistently include a data interpretation question.
  • Practise interpreting funnel metrics, cohort retention charts, and A/B test results.