What does a product manager do?
By the Compass Careers team · Updated 6 November 2026
A product manager decides what a team builds next, and why. They talk to users, weigh what the business needs against what the team can build, and write the plan down clearly enough for designers and engineers to act on it. They rarely build the product themselves.
A typical week
- Talking to users: interviews, support messages and usage data, to find out what people actually struggle with.
- Choosing what to build: ranking ideas when there’s room for only a few, and saying no to the rest.
- Writing clear specs: turning a decision into a document designers and engineers can build from, then answering their questions as they go.
One real decision from the job
Product · sample decision
You’re the product manager for a budgeting app built for college students. Engineering has room for exactly one piece of work this month.
Your team can only build one feature this month. What would you prioritize?
The four options: fix onboarding, build bank sync, fix the login bug, or build the partner dashboard. Each one is reasonable, and the one you reach for first says something about how you think.
Try this decision free on Compass. It takes a few minutes, and nobody scores you.
How people in the role see it: Product managers make calls like this every week, usually with incomplete information. There’s rarely one right answer. What matters is how clearly you can explain the trade-off.
Signs you might enjoy it
- You like talking to people and turning what they say into decisions.
- You can choose without having every fact, and explain why you chose.
- Saying no to good ideas doesn’t bother you for long.
Signs it might drain you
- You want a clear right answer before you act.
- You’d rather build things yourself than persuade others to.
- Long back-and-forth with many people tires you out.
How to test it in a week
- Pick an app you use daily and write a one-page plan for one feature it’s missing: the problem, who has it, what you’d build first, and what you’d leave out.
- Ask a senior or alumnus in a product role to walk you through one recent decision and what they gave up for it.
- Try the product decision on Compass and note how making the call felt: energizing, fine, or draining.
Common questions
Do product managers need to code?
Many product roles don’t ask you to write code, but you’ll work closely with engineers every day, so understanding how software gets built helps. Read the job descriptions for the roles you’re targeting; they say what’s expected.
Can you become a product manager from a non-engineering background?
Yes. Product managers come from engineering, business, design and other backgrounds. Interviews tend to test how you think about users and trade-offs, which you can practise whatever your degree.
Try the work before you choose it
Compass lets you try a realistic decision from each path you’re weighing, notice how it felt, and choose your next step with evidence. The preview on our home page is free.
Weighing two or three paths seriously? See our packages, each prepared and reviewed by a person.