A product manager (PM) decides what a tech team should build next and why. They work out which problems users really have, which of those problems are worth solving, and how the team will know whether a solution worked. They do not usually write the code or create the designs. Instead, they connect users, the business, designers and engineers so the right thing gets built.
If you are asking "what does a product manager do?", the honest answer is: a lot of listening, deciding and explaining. A PM spends their days talking to customers, reading data, writing clear requirements, and saying "not now" to good ideas so the team can focus on better ones.
It is a popular target for career switchers, and for good reason. But it is also widely misunderstood, so let us look at what the job really involves.
The core of the job: the "why" and the "what"
A useful way to think about it:
- Product managers own the why (why this problem matters) and the what (what we should build to solve it).
- Designers own much of the how it looks and feels.
- Engineers own the how it is built.
These boundaries are blurry in real teams, and good PMs respect the expertise of the people around them. A PM who tells engineers how to write code, or designers which shade of blue to use, usually makes the team worse.
What does a product manager do day to day?
A PM's week is varied. It might include:
- Talking to users. Interviewing customers, watching them use the product, reading support tickets and app reviews.
- Looking at data. Checking how many people use a feature, where users drop off in a sign-up flow, or whether a recent change improved anything.
- Prioritising. Deciding which of dozens of requests goes into the next few weeks of work, and explaining that decision.
- Writing. Product requirement documents, user stories, release notes, and updates for leadership.
- Running or joining team rituals. Planning sessions, stand-ups, reviews and retrospectives.
- Answering questions. Engineers and designers hit questions every day ("what should happen if the user has no internet?"), and the PM helps resolve them quickly.
- Aligning stakeholders. Sales, marketing, compliance, customer support and leadership all have opinions. The PM keeps everyone pointed in the same direction.
Imagine a PM at a fintech whose savings app has many sign-ups but few people completing their first deposit. Their job is to find out why (through data and user interviews), propose options, agree on one with the team, and then measure whether deposits improve after it ships.
What skills does a product manager need?
Communication and empathy
This is the centre of the role. You need to understand users who are not like you, explain decisions clearly in writing and in meetings, and handle disagreement without damaging relationships.
Analytical thinking
PMs make decisions with incomplete information. You need to read basic data, spot when a number looks suspicious, and reason about trade-offs. Comfort with spreadsheets and simple SQL is a real advantage.
Prioritisation
There will always be more work than time. Frameworks help (you will hear about RICE, MoSCoW and others), but the real skill is judgement: understanding impact, effort and risk well enough to choose.
Enough technical understanding
You do not need to code, but you need to understand how software is built: what an API is, why some changes are risky, and what "technical debt" means. Engineers trust PMs who ask good technical questions and respect their estimates.
Business sense
How does the company make money? What do competitors offer? What regulations apply? In Nigeria, for example, products in finance or health often have regulatory requirements that shape what can be built.
If you want to know whether your natural strengths lean towards communication and structured decision-making, take the free TechDNA assessment. Product Manager is one of the nine roles it scores.
Is product management a good first tech job?
It can be, but it is harder to enter directly than many people expect. Companies want evidence that you can make good product decisions, and that evidence is hard to show without experience. Entry-level roles exist (titles like associate product manager or junior PM), but they are fewer than entry-level engineering or support roles.
Many PMs move in from neighbouring roles:
- Customer support or operations, where they already understand users' pain.
- Business analysis or data analysis.
- Engineering, design or QA.
- Domain expertise, such as banking, healthcare or education, joining a company that builds for that sector.
If you work in one of those areas now, your path into product may be shorter than you think. Our guide to moving from banking to tech explores one such route.
How to start moving towards product management
Learn the fundamentals
Read widely about product discovery, prioritisation, user research and metrics. Learn the basics of how software is developed, including agile ways of working. Free introductory material on these topics is easy to find, and roadmap.sh has a product manager roadmap.
Practise on real products
Pick an app you use, such as a ride-hailing app or a bank app, and write a short case study:
- Who are its users, and what problem does it solve for them?
- What is one frustrating part of the experience?
- What would you change, how would you test it, and how would you measure success?
Two or three thoughtful case studies make a strong portfolio for a PM role.
Build something small
You do not need to be an engineer to ship a product. Use no-code tools to launch a simple service, such as a booking form for a local business, and learn from real users. Having actually shipped something sets you apart.
Learn some data skills
Basic spreadsheet analysis and introductory SQL let you answer your own questions instead of always waiting for an analyst.
Volunteer for product-like work in your current job
Offer to gather customer feedback, improve an internal process, or coordinate a small project. These experiences translate directly into product stories in interviews.
Common mistakes aspiring PMs make
- Thinking it is a "boss" role. PMs rarely manage people directly. They lead through influence, not authority.
- Leading with solutions. Good PMs fall in love with the problem first. Starting with "we should build an app that…" before understanding users is a red flag in interviews.
- Collecting certificates instead of evidence. A certificate shows you studied. A case study or shipped project shows you can think like a PM.
- Avoiding anything technical. You do not need to code, but refusing to understand how things are built limits you.
Product management and the Nigerian market
Nigeria's tech sector, especially fintech, has created a lot of product roles, and many international companies hire remote PMs too. Remote product roles can be harder to land than remote engineering roles, because PMs need deep context about the users and market. Building products for local users is a genuine strength here: understanding how people actually pay, borrow, save and use their phones is valuable knowledge.
People often confuse product management with project management. If you are unsure which fits you, read our comparison of product manager vs project manager vs product owner. And if you want a broader view of roles that do not centre on code, see non-coding tech jobs.
Frequently asked questions
Do product managers need to know how to code?
No, most PM roles do not require coding. However, understanding how software is built, and being able to read basic data, makes you much more effective. Some technical products, like developer tools, do prefer PMs with engineering backgrounds.
What is the difference between a product manager and a project manager?
A product manager decides what to build and why, based on users and business goals. A project manager focuses on delivering a defined piece of work on time and within budget. The roles can overlap, especially in smaller companies, but their core questions differ.
Can I become a product manager without a tech background?
Yes. Many PMs come from business, operations, customer service and other fields. The key is showing that you understand users, can make reasoned decisions, and can work well with technical teams.
Is a product management certificate worth it?
A course can give you structure and vocabulary, but on its own it rarely gets you hired. Pair any learning with practical evidence: case studies, a small shipped product, or product-style work in your current role.
Product management suits people who love understanding others, enjoy structured decisions, and can stay calm while juggling competing demands. To see how your traits match the role, take the free TechDNA assessment. In about seven minutes, you will see your fit for Product Manager and eight other roles.