Product Manager
What the work looks like, the products behind the title, what each level means and the training that helps, then how interviews run and how to prepare for each step.
What a product manager actually does
A product manager decides what the team builds and why, from the users and their problems to the results the product brings.
A product manager is responsible for what a product team builds and why. They talk to users, study the data, frame the problems worth solving and decide the order in which the team works on them, together with engineering and design.
The role sits between the users, the product team and the rest of the company. Product managers share the roadmap with sales, marketing and leadership, and explain the trade‑offs behind each priority.
Once a feature is live, they measure its impact with product analytics and A/B tests, and use what they learn to plan the next steps.
- User interviews or a review of user feedback
- Sprint planning and refinement with engineering and design
- Writing or updating the spec of the next feature
- A review of product metrics and A/B test results
- A roadmap update with sales, marketing or leadership
The same title, very different products
Most product manager searches are defined first by the type of product the company builds, then by the ground every product manager shares.
What each level means in practice
Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.
- Works on a part of the product with a senior product manager
- Learns the users, the data and the way the team works
- Writes specs and runs user interviews with guidance
- Owns a feature area or a small product end to end
- Sets priorities with engineering and design
- Measures the results of what the team ships
- Owns a product with several teams or a complex scope
- Sets the strategy and the roadmap for their area
- Mentors other product managers
- Group product managers lead a team of product managers
- Principal product managers own the most complex products
- Sets the product strategy across several teams
The paths into the role, and what really counts
Companies look first at the products you have shipped and the results they brought. Education and certifications help most early in a career, or to change field.
- Engineering school or master's in computer scienceA common path in France, often valued for technical products.
- Business school or MBAA common path in France and in the US, at master's level.
- Engineering, design or data firstMany product managers start as engineers, designers or data analysts before moving to product.
- Product Owner or consulting backgroundProduct owners and consultants often move into the role after a few years.
Our view: for this role, a product you shipped and can walk through, from the user problem to the measured result, often says more than any certificate.
A conversation with a senior tech recruiter
Your first interview is with one of our senior tech recruiters, who knows the role, the products and the levels in this guide. The conversation covers your own work through real examples, and the product cases come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.
- What you owned yourselfThe products, features or areas you were responsible for, and your own part in the team's decisions.
- Your environment and its constraintsYour users, your market, the size of the team, deadlines or technical limits: what shaped your choices.
- The decisions you madeWhat to build first and what to leave for later, the options you compared and the reasons for your choice.
- The impact of your workWhat changed thanks to your work, with numbers when you have them: adoption, retention, revenue or time saved.
- How you work with other teamsYour work with engineering, design, sales and leadership, and how you settle a disagreement.
- What you want nextThe kind of product, users and scope you are looking for in your next role.
- Products shipped and measured impact
- Decisions with users and data
- Work with engineering
- Scope and complexity owned
The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.
Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.
What the company will assess, step by step
Each company runs its own process, and we walk you through its steps before you start. Product manager processes often combine the steps below, and the depth expected at each step grows with your level.
- A product caseA product to design or improve, live or as a take-home you present to the team, and how you frame the users, the problem and the priorities.
- A metrics caseA metric that drops, or a new feature to measure, and how you read the data and decide what to do next.
- A deep dive on a product you shippedOne product or feature you owned, discussed in depth: the users, your decisions, the trade‑offs and the result.
- Meeting engineering, design and the managerHow you work with the team day to day, how you take decisions with others and what the team expects in your first months.
- Product ManagerYou frame the problem clearly, ask the right questions about the users and explain each priority in simple words.
- SeniorYou lead the discussion, connect your choices to the company's goals and point out risks and trade‑offs before you are asked.
- Group and PrincipalYou run most of the interview as a peer, link the case to the product strategy and show how you bring several teams with you.
How to prepare as a product manager
Practical advice for each step of a product manager process, from the way you introduce yourself to the questions you ask at the end of each interview.
Start with the products you worked on, their users and your part in them. Mention your type of product in one sentence, then close with what you want next.
For each one, prepare the user problem, the constraints, your decision, the options you set aside, the result and what you would change today. Say "we" for the team and "I" for your own part.
In a product case, ask who the users are, what problem they have and what success looks like before you propose anything. Then explain each priority in plain words.
Interviewers often ask how you knew a feature worked. Prepare the metrics you followed, the tests you ran and one decision you changed because of the data.
Prepare one example of a trade‑off you made with engineers, on scope, quality or deadlines, and explain how you reached the decision together.
Rules on AI tools differ from one company to the next, especially for take-home cases. Ask before each step, and when they are allowed, explain what you asked the tool and how you checked its output.
- Tell us about a product launch that went wrong, and what you learned.
- How do you decide what goes on the roadmap first?
- A key metric drops by 10% this week. What do you do?
- Tell us about a disagreement with engineering, and how you settled it.
- How does the team decide what goes on the roadmap?
- Who are the users, and how often do product managers talk to them?
- How does the team measure the success of a feature?
- How do product, engineering and design work together day to day?
- How much freedom does a product manager have on the roadmap?
- How does the team use AI tools in product work?
Where product managers come from, and where they go
The roles people most often hold before this one, and the ones they most often move to.