Technology
The CEO of a product
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 decide how success will be measured, plan the order of new releases and explain why a promising request should wait. Their purpose is to focus the team’s limited time on improvements worth making, 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. Instead, they must show why the problem is worth solving and explain what each option would gain or give up. You may enjoy moving between customer evidence, business needs and the limits of the technology. You then have to choose without having every fact.
There is no single route in. Some graduates join product training schemes or start as associate product managers; others move from consulting, marketing, data analysis, design, engineering or operations. Employers value evidence that you can understand users, reason with data and win the support of specialists without pretending to share their expertise. A short example of your product work is strongest when it explains the decision and result, not just the screens or layout.
| 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 |
Lots of people help create a product, but the product manager 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.
Product work forces you to think about customers, technology, competitors, how the company earns money and how plans become real work. You must consider all of them at the same time. You learn how engineers build things, how designers think, how businesses set priorities and why customers actually buy something. Over time, you get a close view of how a company works. That makes product one of the more natural backgrounds for someone who wants to start a business later.
A product manager 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 important choices without having all the facts and then live with the result. That’s a useful skill far beyond product itself.
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.
Working across design, engineering, customers and business 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 specialist skill to perfect.
Sometimes the team will spend months building something and customers just won’t care. Other times you’ll choose the wrong problem or misread the evidence. People can clearly see the results of your judgement because the decisions eventually become real things that they can use. Good companies expect some ideas to fail; the skill is noticing mistakes quickly, learning and changing direction rather than pretending every decision was right.
Usually 3–4 years
Business, engineering and computer science are common, but associate product schemes recruit more widely because the job combines several disciplines rather than belonging to one. Use university to take responsibility for something with real users: improve a society’s booking process, run a service, test a small app or complete a product placement. Be ready to explain what people needed, what you chose not to do and what changed after release. That evidence can lead straight to the associate rung; otherwise, work in analysis, design, engineering, marketing or operations often becomes the bridge into product.
Usually 0–2 years’ experience
This is the most common dedicated entry-level product title. You’ll normally take responsibility for smaller features or a clearly defined part of a product while working closely with a more experienced product manager. The main goal is learning how a product team works and proving that you can be trusted to make increasingly important decisions.
Usually 2–4 years’ experience
You’re now expected to take responsibility for a meaningful area of the product. 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.
Usually 4–7 years’ experience
The problems get bigger, less defined and more important to the business. You might take responsibility for an important customer task, a whole product or a risky new direction. You also work much more closely with senior leaders. Individual features matter less at this stage. You are judged more on whether an important part of the business is moving in the right direction.
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 and coach other product managers. You also 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.
Usually 10+ years’ experience
This is the senior end of the product career path. You’re responsible for the direction of all the company’s product teams. You usually work closely with the chief executive, engineering leaders and other senior figures. At this level, product decisions and company strategy start to merge: you’re helping decide where the business itself goes next.
Covers the business side of the job - pricing, how a product is presented and how to read a company’s income and costs. You’ll still have to learn about the technology on the job.
Trains you to break a vague problem into solvable parts - this is much of what a product plan really does. Having studied applied sciences, engineering graduates tend to gain the trust of their technical teams relatively quickly.
Helps you understand engineers’ explanations, recognise dependencies and judge whether an estimate is reasonable. Its habits can also pull too quickly towards the solution. Product work requires testing whether the customer problem deserves engineering effort at all, then weighing that answer against the business case.
History, English and languages teach you to read a lot of messy evidence and turn it into a clear argument. A written product plan needs the same skill. Arts graduates also tend to write well, and writing is a large part of how a product manager gets things done.
Economics teaches you to ask what each choice gives up and which option adds most value. It also helps you see how rewards and pressures change behaviour. Psychology helps with the research side of the job. You learn to investigate why people behave as they do and what they really want.
No other single subject is common enough to list. Law sharpens attention to constraints, design to people’s experience, mathematics to evidence and the sciences to testing a hypothesis. Each supplies one useful lens, but the product manager must combine customer, technical and commercial reasoning rather than protect the habits of one discipline.
Hover a subject to see why it helpsTap a subject to see why it helps
08:45 – 09:30Check the signals
You start by looking at yesterday’s figures showing how people used the product 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.
09:30 – 10:00Quick engineering meeting
The engineers briefly explain what they’re working on and anything holding them up. 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.
10:00 – 11:30Customer interviews
You join a designer to speak with two customers about how they currently complete a particular task using your product. You have ideas about what might be happening, but try not to steer them towards confirming what you already believe. One customer describes a frustrating problem nobody on the team knew existed. That sentence ends up being more useful than most of yesterday’s meetings.
11:30 – 12:45Work out what it means
You compare the interview notes with figures showing how people use the product and messages sent to customer support. 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.
12:45 – 13:30Lunch
Pret salad.
13:30 – 14:30Design review
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. Your role is to represent the user and explain clearly what the business would gain or give up with each choice.
14:30 – 16:00Priorities meeting
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 what the team would gain and give up with each choice. After challenging a few assumptions, you decide what the team should do next. This is the part of product management where judgement matters most.
16:00 – 17:15Write the plan
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.
17:15 – 18:00Help the team move forward
An engineer messages with a question about an unusual situation nobody considered. You jump on a quick call, make a decision and update the release timetable.
+11 hours compared with the average UK job