Topic 20 — PM specializations

Goal: Understand the main flavors of PM so you can target the right fit and adapt your skills.

Lesson 20.1 — One craft, many flavors

Maya is at a meetup, nursing a lukewarm coffee, and a recruiter asks her: "Are you more of a growth PM or a core PM? B2B or B2C?" She freezes. She's been doing this job for six months at Lumi and nobody ever handed her a label.

She figures it out later, on the walk home. Those labels point at the same job. They just point it at different products.

The craft you've built across this whole course (discovery, prioritization, specs, metrics, communication) is the same in every one of them. What changes is the product you point it at and the context around it. That's what a specialization is. Knowing the flavors helps you read job ads accurately, target roles that actually fit you, and adapt your approach once you're in one.

Think of specializations as accents on the same language, not different languages.

You don't pick one and marry it. Plenty of PMs move between them, and the fundamentals carry over every time. This last topic walks you through the main flavors so you can recognize them and spot where your strengths fit.

Lesson 20.2 — B2B vs. B2C PM

The biggest fork in the road is one question: who's the customer?

Lumi sells to regular people who want to track their spending. That's B2C (consumer). Millions of potential users, and no single one of them is going to get on a call with Maya. So decisions get driven by data, design, and experiments run at scale. You watch what thousands of people do in the sign-up flow, you A/B test the budgeting screen, you sweat the funnel and the delight. It rewards people who love data, have a feel for design, and enjoy optimizing things at large scale.

Now imagine Lumi pivoted to selling a budgeting tool to finance teams inside big companies. That's B2B (business). Suddenly there aren't millions of customers. There are a few hundred, and a handful of them are huge. Decisions get driven by customer relationships and ROI. Maya would be on calls with actual clients, weighing one big account's demands against the whole market, and navigating buying committees and the sales team to close deals. The work leans toward workflows, integrations, and provable business value rather than mass-scale polish. It rewards people who are strong with stakeholders and like deep customer relationships.

Neither one is harder. They reward different muscles.

	B2C PM	B2B PM
Customer	Millions of consumers	Fewer, larger businesses
Decisions driven by	Data, design, experiments at scale	Customer relationships and ROI
Day-to-day	Funnels, growth, delight	Workflows, integrations, sales/buying committees
Fits people who	Love data, design sense, optimization	Are strong with stakeholders

If you're coming from sales or account management, B2B will feel like home. Maya's old café-managing instinct for reading people would serve her there too. People arriving from consumer, creative, or data backgrounds usually lean B2C.

Lesson 20.3 — Growth PM and core/feature PM

Same product, different question: which part of it do you own?

Lumi has a PM (call her the one Maya shadows) whose entire week is numbers. How many people signed up? How many stuck around past day three? How many upgraded to paid? She owns the metrics engine end to end: acquisition, activation, retention, monetization. She runs experiment after experiment to nudge those numbers up. That's a Growth PM — highly analytical, fast-iterating, happiest with a funnel on one screen and an A/B test on the other.

Maya's own job is different. She owns the actual budgeting experience: the weekly-budget feature, the thing customers keep asking for, the screen people open every morning. Longer build cycles, more discovery, more craft. That's a Core / Feature PM, and it's the default. Most PM jobs are this one. It suits people who love digging into a hard problem and understanding users deeply.

There's a third owner of a sort: the Platform / Technical PM, who owns the underpinnings other teams build on top of. More on that next.

Recognizing which kind a role is tells you what it'll actually ask of you, and whether that's a fit.

Lesson 20.4 — Technical PM and AI PM

One more question, and it's the one that scares career-changers most: how technical is the product itself?

A Technical PM works on products where the customers are basically engineers. APIs, data pipelines, internal platforms, developer tools. If Lumi ever built an API so other apps could pull budget data, the PM on that would need deeper technical literacy than Maya uses day to day. Note what that does not mean: coding. It means understanding the systems well enough to make good calls with an engineer like Sam. This is a more specialized path, and it's usually one you grow into after a few years rather than walk into cold.

Then there's the flavor everyone's asking about. Remember the CEO's vague pitch for an "AI assistant" in Lumi? The PM who owns something like that is an AI PM — same craft you've learned, plus a twist that changes everything.

Regular software is deterministic. Same input, same output, every time. AI built on LLMs is probabilistic: outputs vary, and sometimes they're just wrong. An AI assistant might give one user great budgeting advice and another user nonsense, from nearly identical questions. So the AI PM's job grows a few new edges. You design for uncertainty instead of assuming the thing always works. You define what "good enough" quality even means when there's no single right answer. You manage the data and the human-in-the-loop feedback that makes the system better over time. And you handle the ethics and risk that come with a product that can confidently mislead someone about their money.

It's one of the fastest-growing specializations right now, and the field is new enough that non-traditional backgrounds compete well. Clear thinking, good judgment, and the ability to look at an AI's answer and tell whether it's any good matter more here than an ML degree.

Lesson 20.5 — Choosing (and not over-committing to) a specialization

So back to that meetup. How should Maya actually answer the recruiter?

Start with the fundamentals and worry about the label later. Everything in this course applies to every flavor. Land a PM role first, then specialize as you learn what you actually enjoy.

Match the flavor to your strengths and your background. Came from sales? Lean B2B. Strong with data or creative work? B2C or growth. Deep expertise in some industry? A PM role inside that domain. Comfortable judging whether an AI's output is good? AI PM. Play to your edge instead of fighting it.

And breathe, because this is not a life sentence. PMs move between specializations all the time. The core craft transfers, and breadth makes you more valuable, not less. You do not need to find the one perfect niche before you begin.

When you read job ads, read them for the flavor. "PM, Growth" and "Technical PM" and "PM, Enterprise" are telling you the emphasis right there in the title. Apply where your strengths fit, and frame your story to match what they're after.

That's the note this bootcamp ends on. You've learned the one craft of product management from end to end. Now you also know its main flavors, so you can pick a smart entry point and keep growing. Whatever you land in, the fundamentals you built here are what make you good at it.

Worked example — Targeting the right PM role

Two people finish this bootcamp the same week.

Maya spent years in enterprise sales before Lumi. She's sharp with stakeholders and can run an ROI conversation in her sleep, but large-scale data optimization isn't where she lights up. So she aims at B2B / enterprise PM roles and frames her sales history as the asset it is: she already understands buying committees and how customers think about value. The fit is obvious once she stops apologizing for not being "technical enough."

Sam (a different Sam, from a data-analysis background) loves experiments. Funnels and A/B tests are his happy place. He targets growth PM roles and leans hard on exactly that comfort.

Neither one agonizes about choosing forever. Both know the craft transfers and that they can move later if they want. By matching the flavor to their strengths instead of chasing whichever title sounds most prestigious, each plays to their edge and lands a first PM job that actually suits them. That's the whole point of understanding specializations.