Everything you need to know about moving into Product in 2026

The PM role has changed more in the last 2 years than the previous 10.

Here's what that actually means if you're trying to break in or level up.

A lot of the advice floating around about getting into Product is outdated. The leveling, the entry points, the skills that matter have all shifted.

Some of what I believed about this role doesn't hold anymore. The fundamentals are still there. But the edges have moved significantly.

Breaking in is harder and more specific than it used to be:

Associate PM roles: the traditional entry point for career changers are now almost exclusively reserved for new grads. If you're transitioning from another field, that path is mostly closed.

What's open instead:

Product Owner roles at companies running agile delivery: closer to execution, great for people coming from BA, ops, or project management backgrounds
Vertical entry: coming in as a PM in a domain you already know deeply. Finance background? Fintech PM. CS background? Technical PM. Your domain expertise is the credential now, not a PM certification.
Founding team / early stage: smaller companies will take a bet on someone with strong instincts and relevant domain knowledge over a polished resume. This is genuinely one of the best ways in right now.

The leveling conversation nobody is having

Most PM career ladders were designed for one path: IC → Senior → Lead → Director → VP. That's not how it works anymore, and pretending it does is setting a lot of people up for confusion.

There are now two distinct paths, and you should know which one you're on early:

The Leadership Path Group PM → Director → VP → CPO

This is about influence at scale. You're building teams, shaping org strategy, managing up and across. The further you go, the less you're doing the hands-on product work and the more you're creating the conditions for others to do it well.

Skills that compound here: stakeholder management, cross-functional influence, hiring, coaching, executive communication.

The IC Builder Path Senior PM → Principal PM → Staff PM

This path keeps you close to the product and the craft. You're the person with the deepest product instincts in the room, who can hold the full complexity of a product domain and make hard calls without a team under them.

This path is undervalued and undertalked about. A lot of PMs feel like staying IC means they're not progressing. That's wrong. The best product companies need both.

Knowing which path fits you earlier means you stop optimizing for the wrong things.

What AI actually changes

AI hasn't made the PM role smaller. It's made the gap between good and great PMs wider.

Here's what's different:

Prototyping is now free and fast. You can get a working version of an idea in front of users in hours, not sprints. This means the PM who waits for engineering to validate a direction is already behind. Get comfortable building rough prototypes yourself — Cursor, v0, Framer. You don't need to code. You need to be able to move fast enough to get real feedback before a single line of production code is written.

The research loop is compressed. AI can synthesise transcripts, surface themes, and identify patterns across hundreds of pieces of feedback faster than any process you had two years ago. The PMs who win are the ones using this to get closer to customer insight, not the ones ignoring it because "that's the researcher's job."

Execution is being automated. PRD drafts, ticket writing, competitive analysis. AI is eating this work. Here's the uncomfortable part: a lot of PMs built their entire value proposition on being the person who wrote the clearest spec. That's not enough anymore. The PM who wins is the one who uses the time that just got freed up to get closer to the problem. More customer calls, faster validation, sharper prioritization. The ones who just use AI to write faster tickets are optimizing the wrong thing.

The skills that don't compress with AI: knowing which problem is worth solving, building trust with your team, making the call when the data is ambiguous.

Those have always mattered. They matter more now.

The honest state of the market

It's tough. the competition is higher, and companies are expecting more from smaller product teams.

What's working for the people I see breaking through: