Technology
Product Manager
The CEO of a product
What does a product manager do?
A product manager decides what a technology team should build and why. Working with engineers and designers, they study how customers behave, define the problem, compare possible improvements and choose what deserves attention. They may set success measures, sequence releases and explain why a promising request should wait. Their purpose is to direct limited development effort towards a worthwhile outcome, not to invent every feature themselves.
Product managers are responsible for a decision but rarely control the people needed to carry it out. They cannot order an engineer to meet an impossible deadline or ask a designer to disguise a confused idea; they must make the problem worth solving and its trade-offs explicit. You may enjoy moving between customer evidence, commercial priorities and technical constraints, then choosing despite incomplete information.
There is no single route in. Some graduates join product schemes or start as associate product managers; others move from consulting, marketing, analytics, design, engineering or operations. Employers value evidence that you can understand users, reason with data and influence specialists without claiming expertise you do not have. A small product case study is strongest when it explains the decision and result, not just the interface.
- Starting pay£30,000
- Ten years in£80,000
- IntensityDemanding
- CompetitionFierce
- Postgraduate trainingNone needed
Product manager salary in the UK
- A typical earner
- Bottom 10% up to top 10%
| When | Lowest 10% earn under | A typical earner | Top 10% earn over |
|---|---|---|---|
| On graduating | £24,000 | £30,000 | £45,000 |
| 1 year in | £25,000 | £33,000 | £50,000 |
| 2 years in | £27,000 | £38,000 | £58,000 |
| 3 years in | £30,000 | £45,000 | £66,000 |
| 4 years in | £33,000 | £52,000 | £75,000 |
| 5 years in | £36,000 | £58,000 | £84,000 |
| 6 years in | £39,000 | £64,000 | £93,000 |
| 7 years in | £42,000 | £70,000 | £101,000 |
| 8 years in | £44,000 | £74,000 | £108,000 |
| 9 years in | £46,000 | £77,000 | £114,000 |
| 10 years in | £48,000 | £80,000 | £120,000 |
The good and the bad of being a product manager
The good
You decide what gets built
Lots of people help create a product, but the PM is usually closest to the question of what should exist in the first place. You might spot a problem, convince the team it matters and then watch the solution become something real people use. There’s a particular satisfaction in seeing an idea move from a rough thought to a live product. Your fingerprints are all over the outcome, even if you didn’t personally design or code it.
It’s great training for founding a company
Product forces you to think about customers, technology, competition, revenue and execution at the same time. You learn how engineers build things, how designers think, how businesses prioritise and why customers actually buy something. Over time, you’ve effectively had a front-row seat observing how a company works. That makes product one of the more natural backgrounds for someone who wants to start a business later.
You decide where the team spends its next month
A PM rarely gets presented with one obviously correct option. You’ll constantly choose between improving a feature that already exists, building something new, fixing technical problems or saying no altogether. The job teaches you to make consequential decisions with imperfect information and then live with the result. That’s a useful skill far beyond product itself.
The bad
You’re responsible, but not in charge
You’re expected to get the right product built, but the designers and engineers doing the work usually don’t report to you. You can’t simply tell everyone what to do. You have to persuade people that a problem matters and build enough trust that they want to solve it with you. When the team disagrees strongly, that can be frustrating.
Jack of everything, master of nothing
Working across design, engineering, customers and commercial decisions gives you breadth, but it can come at the expense of depth. The engineer gets better at coding; the designer gets better at creating user experiences and interfaces. You’re often the person who knows a useful amount about almost everything but isn’t the expert in the room. That suits generalists, but it can feel unsatisfying if you want a hard craft to perfect.
You’ll make calls that turn out wrong
Sometimes the team will spend months building something and customers just won’t care. Other times you’ll prioritise the wrong problem or interpret the evidence badly. Product makes your judgement unusually visible because the decisions eventually become real things that people can see and use. The reassuring part is that good companies expect this; the skill is noticing mistakes quickly, learning and changing direction rather than pretending every decision was right.
Product manager career path
Associate Product Manager
Usually 0–2 years’ experience
This is the most common dedicated entry-level product title. You’ll normally own smaller features or a clearly defined part of a product while working closely with a more experienced PM. The main goal is learning how a product team works and proving that you can be trusted to make increasingly important decisions.
Product Manager
Usually 2–4 years’ experience
You’re now expected to own a meaningful area of the product yourself. You’ll work out which customer problems matter most, set priorities and guide a design and engineering team towards a solution. The biggest change is that fewer people are telling you what to do; you’re increasingly expected to work that out for yourself.
Senior Product Manager
Usually 4–7 years’ experience
The problems get bigger, less defined and more commercially important. You might own a major customer journey, product line or strategic bet and work much more closely with senior leadership. You’re judged less on the individual features you ship and more on whether you’ve moved an important part of the business in the right direction.
Director / Head of Product
Usually 7–10 years’ experience
At this point, you’re often managing product managers as well as products. You’ll help decide where whole teams should focus, coach other PMs and shape the product strategy for a large part of the company. Your job gradually shifts from making good product decisions yourself to creating a team that makes good product decisions without you.
VP Product / Chief Product Officer
Usually 10+ years’ experience
This is the senior end of the product career path. You’re responsible for the direction of the company’s product organisation and usually work closely with the CEO, engineering leadership and other executives. At this level, product decisions and company strategy start to merge: you’re helping decide where the business itself goes next.
What degree do you need to be a product manager?
Covers the commercial half of the job - pricing, positioning and reading a profit and loss account. You’ll still have to learn the technical half on the job.
Trains you to break a vague problem into solvable parts - this is most of what a roadmap really is. Having studied applied sciences, engineering graduates tend to gain the trust of their technical teams relatively quickly.
You can argue with engineers on their own terms and judge whether an estimate is reasonable. It also makes the sideways move from engineering available to you.
History, English and languages teach you to read a lot of messy evidence and turn it into a clear argument, which is most of what a product brief is. Arts graduates also tend to write well, and writing is large part of how a PM gets things done.
Economics gives you the habit of thinking in trade-offs, incentives and marginal value, crucial for prioritising. Psychology gives you the research half of the job - understanding why people behave as they do and hearing what they really want rather than what they claim.
No other single subject is common enough to list. Product management takes people from law, design, maths and the sciences alike.
Hover a subject to see why it helpsTap a subject to see why it helps
A day in the life of a product manager
08:45 – 09:30Check the signals
You start by looking at yesterday’s product data and scanning messages from the team. A newly launched feature is being used less than expected, so you make a note to investigate. You check the day’s meetings and move one that doesn’t really need to happen.
The engineers quickly run through what they’re working on and anything blocking them. One discovers that a feature is considerably harder to build than the team expected. You ask a few questions and agree to look at whether a simpler version would still solve the customer problem. Product management often means changing the solution without losing sight of the goal.
You join a designer to speak with two customers about how they currently complete a particular task using your product. You’ve got hypotheses, but try not to steer them towards confirming what you already believe. One customer describes a pain point nobody on the team knew existed. That sentence ends up being more useful than most of yesterday’s meetings.
You compare the interview notes with usage data and support tickets. The problem you thought customers had turns out to be slightly different from the real one. You write a short summary explaining what the team has learned and what you think should change. Good product work often looks like changing your mind for sensible reasons.
Pret salad.
The designer walks through an early version of a new feature. You discuss what users should understand immediately, which choices are unnecessary and whether the design actually solves the problem. You’re not there to tell the designer where every button should go but to serve as the voice of the user and make the commercial trade-offs clear.
Sales wants one feature, customers are asking for another and the engineering team wants time to fix some ageing technology. All three requests are reasonable. You explain the trade-offs, challenge a few assumptions and decide what the team should do next. This is the part of product management where judgement matters most.
You finally get a stretch without meetings. You turn today’s conversations into a short proposal covering the problem, the evidence, a possible solution and how the team would know whether it worked. Writing forces vague thinking to become precise. You delete almost as much as you write.
An engineer messages with a question about an edge case nobody considered. You jump on a quick call, make a decision and update the release timeline.
What skills does a product manager need?
How many hours does a product manager work?
+9 hours compared with the average graduate profession