12 weeks · intensive
For whoever has a deadline
About 8 hours a week, in 1 cycle focused on the gaps that weigh most.
Career in 2026 and 2027
Product Manager
Product managers decide what a team builds and why, based on what customers need and what the business can sustain. They connect discovery, strategy, delivery and measurement so that the work produces outcomes and not just shipped features.
Content reviewed on October 20, 2026
- Levels
- 3
- Skills mapped at Mid-level
- 6
What each level must prove
Mid-level
Owns a product area end to end, from continuous discovery and roadmap to specs and the metrics that show whether it worked.
You run your own discovery cadence, turn what you learn into a roadmap of bets and write specs that engineering and design can act on. Compared with junior, you no longer wait for direction on what to learn and you define how success will be measured before building.
Average score required: 60%
Customer Discovery Interviews
Why: Lets you keep a weekly interview habit and turn the transcripts into opportunities that shape the next sprint, not a one-off research project that is forgotten.
Jobs-to-Be-Done Framework
Why: Lets you use the job and the outcomes customers seek to decide between two competing features, instead of defaulting to whichever the loudest customer asked for.
Outcome-Driven Roadmaps
Why: Lets you present a roadmap as bets tied to outcomes and honest about delivery capacity, so a slipped date does not collapse trust with sales or leadership.
PRDs & Product Specifications
Why: Lets you write a spec that states the problem, scope and edge cases clearly enough that engineering stops asking the same questions mid-sprint.
Product Analytics & Instrumentation
Why: Lets you define the events a feature must emit before launch, so a week after release you can actually see where users drop off instead of guessing.
Metrics Frameworks
Why: Lets you pick a primary metric and a counter-metric for a launch, so a lift in sign-ups is not celebrated while retention quietly falls.
Study for Product Manager: trails and practice exams
Each level of this career maps to a study trail. Read the full topic map for free, then measure your level.
Two ways to move up one level
40 weeks · regular
Alongside work
About 4 hours a week, in 3 cycles. Each cycle carries what was left from the previous one.
Frequently asked questions
What is Product Manager?
Product managers decide what a team builds and why, based on what customers need and what the business can sustain. They connect discovery, strategy, delivery and measurement so that the work produces outcomes and not just shipped features.
What must each level of Product Manager prove?
Product Manager is mapped in 3 levels: Junior, Mid-level, and Senior. Open each level above to see the skills it must prove.
How long does the Product Manager plan take?
The plan has 2 paces: 12 weeks per level at about 8 hours a week (intensive) and 40 weeks per level at about 4 hours a week (regular).
How the plan works
AI tutor
A study session on each new topic, at your level.
AI school
Hands-on lessons on using AI in your career's daily work.
Assessments
Each requirement is proven by measurement, not by a checkbox.
Stage review
At the end of each cycle you see what moved and what carries over.
Find out which level you are at
A short diagnostic measures the skills you already have. The journey starts from there.