How to Become a Product Manager

What Does a Product Manager Actually Do?

A product manager owns the direction of a product: what gets built, why it matters, and how success is measured. That sounds clean on paper, but in practice, the day-to-day is messier and more varied than most people expect. You might spend your morning reviewing usage data to understand why a feature is underperforming, your afternoon in back-to-back meetings with engineering, design, and marketing, and your evening writing a product requirements document that needs to go out by tomorrow. You talk to users to understand their problems, translate those problems into a roadmap, prioritise ruthlessly because there is never enough time or resources to do everything, and then work with your team to ship solutions. The tools vary by company but usually include Jira or Linear for tracking work, Figma for reviewing designs, analytics platforms like Amplitude or Mixpanel, and whatever combination of Slack, Notion, and Google Docs keeps the wheels turning. One thing that surprises people: product managers rarely have direct authority over anyone on their team. Engineers do not report to you. Designers do not report to you. You lead through influence, not hierarchy. As one experienced PM put it on Reddit, a lot of product management comes down to common sense, pragmatism, and being nice to people. That undersells the strategic thinking involved, but it captures something true about the role: your ability to work with people matters as much as your ability to think about products.

Why Does Product Management Matter?

Companies can have talented engineers, brilliant designers, and a massive marketing budget, but without someone connecting customer problems to business goals and deciding what to actually build, teams end up shipping features nobody asked for, missing deadlines on things that matter, and wasting resources on work that does not move the needle. Product managers exist to prevent that. They make sure the team is solving the right problems, not just solving problems quickly. They translate across departments that often speak different languages: engineering focuses on technical feasibility, design on user experience, sales on closing deals, and leadership on revenue. The PM is the person who holds all of those perspectives together and makes trade-offs that serve the product and the business. In subscription-based and SaaS companies, where most UK product roles are concentrated, the product is the business. If the product does not deliver value, customers leave. That is why product managers have become central to how modern companies operate, and why the role continues to grow across sectors.

Is Product Management a Good Career?

The short answer is yes, but with some honest caveats about the current market. Here is what makes it worth considering.

• The pay is strong. Product management is one of the better-paid disciplines in the digital and tech space. In the UK, junior and associate product managers typically earn between £35,000 and £45,000. Mid-level PMs with a few years of experience earn between £50,000 and £70,000. Senior product managers can earn between £75,000 and £95,000, and head of product roles average around £110,000. London pays a premium, with Glassdoor putting the average PM salary there at around £69,000. Fintech and large tech companies pay at the top end of these ranges.
• Demand remains solid, but the market has shifted. During the pandemic, product management hiring surged. Since then, the market has cooled and become more selective. Junior roles are harder to come by than they were in 2021, and competition for entry-level positions is fierce. However, experienced PMs with strong track records remain in demand, particularly in areas like AI, payments, and platform products. The role is not going anywhere; companies still need people who can decide what to build and why.
• Remote work is genuinely common. Product management is one of those careers where remote work actually works. Your day is spent on video calls, in collaboration tools, and writing documents. Most tech companies adopted remote or hybrid arrangements during the pandemic and have maintained them. Fully remote PM roles are widespread, and some UK-based PMs work for US companies remotely, which can mean significantly higher compensation.
• You can work across industries. Tech, fintech, healthcare, media, government, e-commerce, education: product managers are needed wherever digital products are built. The core skills transfer between sectors. If you want to move from a SaaS startup to a health tech company, your product thinking carries over, even if you need to pick up domain knowledge along the way.
• Clear progression paths. The ladder is fairly well-defined: associate product manager to PM, to senior PM, to lead or principal PM, to head of product, to director, and eventually VP of product or chief product officer. Not everyone wants to manage people, though, and increasingly, companies offer strong individual contributor tracks for PMs who prefer to stay hands-on. From there, some people branch into product design, engineering management, or consulting. Others start their own companies, and the experience lends itself well to that.
• A word of honesty. Product management is often sold as a glamorous role where you get to be the 'CEO of the product.' The reality is messier: a lot of ambiguity, a lot of meetings, and plenty of situations where there is no clear right answer. You are accountable for outcomes, but rarely have direct control over the people doing the work. PMs on Reddit are pretty candid about this. Many describe the role as rewarding but emotionally taxing, with long hours, rare praise, and heavy responsibility. One veteran PM put it bluntly: if you are here for the glory, look elsewhere. But if you want hard problems that genuinely matter, it can be one of the most satisfying careers out there.

How Do I Become a Product Manager? A Step-by-Step Guide

There is no single path into product management. People come from engineering, design, marketing, consulting, customer support, and many other backgrounds. What matters is proving you can think about products, work with teams, and deliver results. Here is how to build that proof.

1. 1
   Understand what the role actually involves. Before committing, make sure you understand what product management really looks like day to day. It is not about having great product ideas, though that helps. Most of your time goes into communication, stakeholder management, prioritisation, and making difficult calls with only incomplete information. Job descriptions vary more than you might expect, so read them across different companies to get a sense of the range. Some PM roles are deeply technical, sitting alongside engineering and weighing in on architecture decisions. Others are more commercial, focusing on pricing, go-to-market, and business metrics. Follow communities like r/ProductManagement on Reddit and Mind the Product to hear from people actually doing the job. One Reddit user studying to become a creative director noted that the soft skills needed for PM, such as managing teams, communicating vision, and coordinating across functions, are remarkably similar to those of creative direction. That observation is spot on: product management draws on skills from many disciplines.
2. 2
   Get experience in an adjacent role. Almost nobody walks straight into a product manager position. Most employers want to see at least a couple of years of relevant experience before they will consider you, and many prefer more. The most common entry points are engineering, design, data analysis, project management, marketing, customer success, sales, and business analysis. Each brings transferable skills: engineers understand technical feasibility; designers understand users; analysts understand data; and salespeople understand the market. If you are still early in your career, pick a role that puts you close to how products are built and shipped. Internal transfers are among the most common ways people enter product management. Work at a company that builds products, get close to the product team, volunteer for cross-functional projects, and gradually take on more product-oriented work.
3. 3
   Learn the core skills and frameworks. Product management lives where business, technology, and user experience overlap, so you need to be comfortable in all three. On the business side, that means understanding how companies make money, how to put together a business case, and how to track whether something is working through metrics like retention, conversion, and revenue. You do not need to code, but you should know enough about how software gets built to have useful conversations with engineers: what APIs do, how databases work, what is realistic to ship and what is not. On the user side, get good at running research interviews, reading between the lines of feedback, and using data to figure out what people actually do rather than what they say they do. Pick up product frameworks along the way, too. Jobs-to-be-done, opportunity solution trees, and impact mapping all come up regularly. Most product teams run some version of Agile, usually Scrum or Kanban, so getting your head around iterative development early will save you time later.
4. 4
   Get comfortable with data. Product managers make decisions with data every day. You need to be able to define key metrics, read analytics dashboards, run basic queries, and use data to support or challenge a hypothesis. You do not need to be a data scientist, but you should be able to navigate tools such as Google Analytics, Amplitude, or Mixpanel, and understand concepts such as cohort analysis, funnel conversion, and A/B testing. SQL is increasingly expected, especially at more technical companies. Even a basic working knowledge puts you ahead of many candidates. The ability to tell a story with data, to show stakeholders why a particular direction makes sense, and to back it up with evidence is one of the most valuable skills a PM can have.
5. 5
   Build something or contribute to a product. Theory only gets you so far. The candidates who stand out are the ones who can point to something they actually built or shaped. That does not mean you need to launch a startup, though that would count. You could build a small side project, contribute to an open-source product, or run a meaningful initiative within your current company. Document what you did, why you made the decisions you made, and what happened as a result. If you are in a non-PM role, look for opportunities to take on product-adjacent work, such as running a user research project, writing feature requirements, or leading a cross-functional initiative. Anything that shows you can think through a problem, align a team, and deliver an outcome is relevant evidence.
6. 6
   Consider formal education, but know it is not required. A degree helps get your CV past the initial screening, especially at bigger companies. Business, marketing, computer science, and engineering are the backgrounds you see most often, but most employers are not fussy about the subject. There is no dedicated degree for product management, although a handful of universities now offer product-focused modules or short courses. A master's is rarely necessary, though it can be useful at the senior end or if you are switching careers from a completely different field. At the end of the day, what actually lands people the job is hands-on experience and a track record of shipping products that worked, not the name on a diploma.
7. 7
   Explore apprenticeships. If university is not for you, the Digital Product Manager Level 4 Apprenticeship is a genuine alternative. It covers the full product lifecycle, user research, Agile delivery, stakeholder management, and data-driven decision-making. The programme typically lasts around 15 to 24 months and combines on-the-job training with structured learning. You earn a salary, your employer covers the costs, and you finish with a recognised qualification and practical experience. Training providers include QA, Cambridge Spark, and BCS. It is a relatively new apprenticeship standard, but it is growing quickly as more companies recognise the need for structured product training.
8. 8
   Pick up relevant certifications (optional). Certifications will not get you hired on their own, but they can help round out a CV, particularly if your background is not in tech or business. The Google Project Management Certificate is a decent starting point for Agile and project fundamentals. Scrum Master certifications like CSM or PSM are worth considering if you want to understand how engineering teams actually run. On the product side, Mind the Product, Product School, and General Assembly all offer their own programmes. The AIPMM offers product management certifications, though they appear less often in UK job ads. None of these is a shortcut into the role, but they show you have put in the effort, and that counts for something when you are competing against candidates with more direct experience.
9. 9
   Prepare for product management interviews. PM interviews are different from most job interviews. You will likely face product sense questions (design a product for a given user), analytical questions (how would you measure the success of a feature), strategy questions (should this company enter a new market), and behavioural questions (tell me about a time you influenced without authority). Practice structuring your answers clearly. Read Cracking the PM Interview by Jackie Bavaro for a solid overview of what to expect. Do mock interviews with other aspiring PMs, whether through Slack communities, LinkedIn groups, or platforms like Exponent and PM Exercises. One consistent piece of advice from Reddit: be honest about what you do not know. Interviewers respect candour far more than rehearsed corporate answers.
10. 10
    Start applying before you feel completely ready. Job descriptions in product management can look intimidating, and at the junior end, they are often unrealistic, listing five years of experience for what is clearly an entry-level role. Do not let that put you off. If you tick most of the boxes, send the application. Look for titles like associate product manager, junior product manager, or product analyst as entry points. Smaller, growing companies tend to be more flexible on requirements and more willing to take a chance on someone with strong potential but limited PM experience. Tailor your CV to each role: emphasise product-relevant projects, metrics you influenced, and any evidence of cross-functional work.

Resources and Further Reading

• Mind the Product – The largest product management community globally. They run ProductTank meetups in cities across the UK, publish articles and salary reports, and host an annual conference. Their content covers everything from career advice to strategic frameworks. A good starting point if you want to understand what the profession looks like from the inside.
• Product School – Offers certifications, free webinars, and a community of product managers. Their Product Management Certificate is one of the better-known credentials in the field. They also publish useful content on career development and interview preparation.
• Inspired by Marty Cagan – If you read one book about product management, make it this one. It explains how the best product teams work and why many companies get it wrong. Recommended constantly on Reddit and by working PMs. Not a how-to guide, but it shapes how you think about the role.
• Cracking the PM Interview – Written by Jackie Bavaro and Gayle Laakmann McDowell. Walks you through the main types of PM interview questions, from product design and analytical problems to behavioural questions, and shows you how to structure your answers so you do not ramble. If you are actively interviewing, this is probably the single most useful book to have on your desk.
• Lenny's Newsletter – Lenny Rachitsky, a former Airbnb PM, writes about product strategy, growth, hiring, and career advice. It has become one of those newsletters that working PMs actually read rather than let pile up in their inbox. Worth subscribing to early, even before you land your first role.
• Scrum.org – If you are going into tech product management, you need to understand how Scrum works. Offers the Professional Scrum Master certification and free resources, including the Scrum Guide. Understanding Agile delivery is expected in most PM roles.
• General Assembly – Runs product management courses both online and in person, with a London campus. Their programmes range from short introductory workshops to longer immersive courses. Useful if you want structured learning with real instructors rather than self-paced video courses.
• r/ProductManagement – Over 100,000 members discussing everything from how to break into PM and interview prep to strategy debates and venting about stakeholders who will not stop requesting features. People are blunt in a way you won't find on polished career sites, which is exactly why it is useful.