The specialisation question
GuidePlatform, growth, AI, data, B2B. When specialising raises your ceiling and when it traps you.
What changes at each level, what gets you promoted, and the lateral moves that are worth more than a title bump.
Judged on execution. Ship what's agreed, on time, with the details right. The skill to build here is writing clearly enough that nobody has to ask you what you meant.
Judged on outcomes for one area. You own the problem, not the backlog. Discovery becomes real work, not a phase.
Judged on ambiguity handled. You get given a business problem, not a feature. Influence without authority becomes the whole job.
The fork: depth (Principal — hardest technical problems) or breadth (Group — people and portfolio). Both are senior; only one has direct reports.
Judged on the system: hiring, operating cadence, portfolio bets. You stop making product decisions and start deciding who makes them.
Platform, growth, AI, data, B2B. When specialising raises your ceiling and when it traps you.
What transfers from your current domain, and the four gaps hiring managers actually probe.
A plan that earns trust instead of announcing a reorg in week three.
The evidence pack, the sponsor conversation, and why "do the next level's job first" is only half true.
Visa reality, where the PM roles actually are, and how European hiring differs from US processes.
What to do in the first 72 hours, and how to talk about it in interviews without flinching.
Three artefacts, one page each, and the order a hiring manager opens them in.
Where the public data is honest, where it isn't, and how to anchor a level conversation.