Product manager

Product managers decide what a team builds next and, more often, what it does not. They sit between the people who use the thing, the engineers and designers who build it, and the part of the business paying for all of it, and those three rarely want the same thing in the same month. The job is not designing or coding. It is choosing, explaining the choice in words other people can repeat, and being the one who is wrong in public when it was the wrong call.

What the job actually involves

• Talk to people who use the product, including the ones who quietly gave up on it.
• Decide what the team works on over the next few weeks, and write down the reason.
• Turn a vague request into something an engineer can genuinely start on Monday morning.
• Say no to someone senior, with a reason they can repeat to their own boss without you there.
• Check whether what shipped last month changed anything, using numbers rather than opinions.
• Tell support, sales and marketing about a change before customers meet it, not after.
• Cut scope when the date will not move, and be specific about what is being dropped.
• Keep a written record of decisions, because the same argument comes back in four months.

On a normal day

• You watch someone use the thing you built and they never once find the button you spent a fortnight on.
• Sales promise a feature to a customer in a meeting you were not invited to, and you decide what happens next.
• You rewrite a three-sentence request full of jargon into one sentence about what the user is trying to do.
• You open last week's numbers and find the change you were proud of made no measurable difference.
• You spend an hour with an engineer working out why the simple version is not actually simple.

Pay and hours

Starting

£39,000 a year

Typical

£57,000 a year

Experienced

£75,000 a year

Source: National Careers Service digital product owner profile, the nearest published band; median is its midpoint, checked 2026-07-29.

Usually 37 to 40 hours a week, regular pattern. Evenings are common.

Skills that matter

• Prioritising. Everything on the list is somebody's genuine need, and the whole job is picking the order and living with what waits.
• Writing plainly. Most of your influence travels as text into rooms you are not in, so a woolly sentence becomes a fortnight of the wrong work.
• Listening to users. People describe the solution they imagined rather than the problem they have, and the gap between the two is where good products come from.
• Reading data honestly. It is easy to find a chart that agrees with you, and the useful skill is noticing when the numbers say the idea did not work.
• Working without authority. Nobody on the team reports to you, so nothing happens unless people are actually persuaded, which rules out simply insisting.
• Enough technical literacy. You do not need to write the code, but you need to follow why a change is a week rather than a day, or you cannot argue about the trade.
• Handling disagreement. Two senior people want opposite things and both are being reasonable, and the decision is still yours to make and defend.

How people get in

• Apprenticeship (Level 4). The digital product manager apprenticeship covers the product lifecycle, user research and working with engineering teams, and pays you while you learn it. Usually 18 months to 2 years.
• Degree apprenticeship (Level 6). The digital and technology solutions professional standard leads to a degree and suits people who want the technical grounding alongside the product work. Usually 3 to 4 years.
• University (Degree). No subject is required. Computing, business, psychology and design all appear, and a placement year on a real product team matters more than the title of the course. Usually 3 to 4 years.
• Work (No formal qualification). Moving across from support, quality assurance, business analysis or operations is the most common route, because you already know the product and the customers. Usually 2 to 4 years.

Experience that helps

A surprising number of product managers arrive from customer support, testing, marketing, teaching or operations, because those jobs teach you what users actually struggle with. Anything where you had to explain a technical thing to a non-technical person, or decide what to fix first with limited time, is directly relevant. Running a club, a shop rota or a small side project counts as evidence you can prioritise and ship.

Who employs product managers

• Software companies and technology startups
• Banks, insurers and retailers with in-house digital teams
• Government and NHS digital services
• Digital agencies and consultancies
• Media and subscription businesses
• Charities running their own apps and platforms

Where the work happens

Hybrid is the norm, split between home and an office with the engineering and design team in it. The week is heavy on conversation: standups, reviews, customer calls and a lot of writing in between. Deadlines are self-imposed more often than external, which sounds relaxing and is not, because the pressure arrives as everybody's expectations at once. Occasional evening work around a launch.

Where it leads

• Senior product manager, owning a larger area and mentoring newer managers.
• Product lead or head of product, responsible for several teams and the strategy behind them.
• Specialise in growth, platform, data or a regulated area such as payments.
• Move sideways into user research, design or engineering management.
• Consult independently, which is common once you have shipped in more than one industry.

Common questions

Related jobs

All jobs in Business and beyond