Types of Product Managers
"Product manager" is one title covering jobs so different that practitioners often cannot do each other's work. A growth PM optimizing a checkout funnel and a platform PM designing an internal API share a competency model and almost nothing else day-to-day. I think the single biggest mistake early-career PMs make is assuming there is one PM job to master. There is not. There is a core craft, the twelve competencies, expressed through wildly different specializations. Knowing which one you are in, and which one a job posting is actually for, saves you years.
#The major specializations
- Core or feature PM. Owns a product area in a customer-facing app, the default mental image of the job. Broadest competency demand.
- Growth PM. Owns a metric (activation, retention, conversion) rather than a feature area. Lives in funnels, experiments, and analytics. Heaviest data demand of any type.
- Platform or technical PM. Customers are internal teams or external developers, and deliverables are APIs, SDKs, and infrastructure. Heaviest feasibility and architecture fluency, lightest on consumer UX.
- 0-to-1 PM. Finds product-market fit from nothing. All discovery and judgment, little optimization. Tolerance for ambiguity is the whole job.
- Scaling or 1-to-n PM. Takes a product that works and makes it work at 100x. Optimization, reliability, and org design over invention.
- AI PM. Builds products on probabilistic models. A genuinely different craft, and it gets its own treatment in The AI Product Manager.
These are not mutually exclusive. A growth PM on an AI product at a scaleup is all three at once. They are lenses, not boxes.
#The B2C vs B2B split
Cutting across all of the above is the axis I know best, having spent my career in B2C mobile (sports, media, betting):
| B2C | B2B | |
|---|---|---|
| User = buyer? | Usually yes | Usually no; buyer, user, and admin differ |
| Decision driver | Emotion, habit, delight | ROI, workflow fit, procurement |
| Volume | Millions of low-touch users | Fewer, higher-value accounts |
| Discovery | Analytics plus broad research | Deep interviews, sales calls, advisory boards |
| Killer competency | UX and retention instinct | Stakeholder and viability management |
Here is why this matters. A B2C PM who is brilliant at funnel optimization can flounder in B2B, because the user cannot tell you what they need over an analytics dashboard. You have to go talk to them, and the person who pays is not the person who clicks. Neither is harder. They are different. Do not assume your instincts transfer.
#What stays constant
Underneath every type, the four risks and the trade-off act are invariant. Every PM, in every specialization, is managing value, usability, feasibility, and viability. Only the weights change. A platform PM weights feasibility heavily and usability lightly. A growth PM weights value, measured as conversion, above all. The competencies are the same alphabet. The specializations are different words.
Job descriptions love "we need a strong generalist PM." Real teams need a specific shape for a specific problem (see The T-Shaped PM and Knowing Your Shape). When you interview, figure out which type the role actually is, because the title will not tell you. Ask what the one metric or outcome is that this PM owns. The answer reveals the type faster than any job description.
#Continue Reading
- The T-Shaped PM and Knowing Your Shape for matching your spike to the type the role needs.
- The AI Product Manager for why AI PM is a distinct specialization, not just core PM with models.
- The Four Big Product Risks for the invariant under every specialization.
- Product Management Across Company Stages for how stage interacts with type (0-to-1 vs scaling).
- The PM Competency Model for the shared alphabet all the types are written in.