PM career ladder, by level

Scope at this level

Owns a specific feature or component within a larger product. Works closely with a senior PM mentor. Expected to learn the craft: writing PRDs, running sprints, interpreting metrics, partnering with engineering. Success measured by shipping features on time and demonstrating a growing understanding of user needs.

Promotion criteria

Promoted by consistently delivering high-quality features, showing initiative on cross-functional problems, and demonstrating the ability to independently define and prioritise work. Strong APMs start driving their own roadmap items and influencing team direction.

Scope at this level

Owns a product area with a dedicated engineering team (typically 5-12 engineers). Defines roadmap, sets priorities based on user research and data, makes trade-off decisions. Responsible for product metrics. Works independently but reports into a Senior PM, Group PM, or Director.

Promotion criteria

Move to Senior PM by demonstrating strategic thinking beyond your immediate product area, influencing adjacent teams, and showing measurable business impact. Senior PM requires evidence that you can define product strategy (not just execute it), mentor other PMs, and handle ambiguity at the multi-quarter planning level.

Scope at this level

Owns a significant product area that may span multiple engineering teams. Sets product strategy and drives cross-functional alignment. Expected to independently identify new opportunities, not just execute against a predefined strategy. Mentors junior PMs and represents the product org in leadership meetings. Terminal level for many PMs and the sweet spot of high comp and hands-on product work.

Promotion criteria

Group PM or Director promotion requires demonstrating org-wide impact, owning a portfolio of products rather than a single area, and showing leadership in setting the product vision. At many employers this is a significant gate: only 20-30 percent of Senior PMs advance.

Scope at this level

Owns a portfolio of products or a major product line. Manages product strategy for an area with multiple PM teams. At some employers Group PMs directly manage other PMs; at others it is an IC role with significant scope. Drives multi-quarter, multi-team initiatives and represents product in executive reviews. The IC and management tracks diverge here.

Promotion criteria

Advancing to Director or VP requires demonstrating the ability to build and lead product teams, define company-level strategy, and influence executive decisions. Many excellent Group PMs stay at this level because it offers the best balance of impact, comp, and hands-on product work.

Scope at this level

Leads a product organisation with multiple teams and Group PMs reporting in. Responsible for a major business unit or product line. Sets strategic direction, accountable for business outcomes. Frequently presents to executive team and may participate in company-wide strategy sessions. Spends more time on org health, hiring, and team development than on individual product decisions.

Promotion criteria

VP requires building a track record of scaling product organisations and delivering transformative business results. VPs typically own P&L-level outcomes and are expected to shape company strategy. The jump from Director to VP is one of the most competitive in any company.

Scope at this level

Owns an entire product organisation or division. Reports directly to CEO or CPO. Responsible for product strategy at the company level: resource allocation, team structure, long-term vision. Expected to drive business transformation and is evaluated on revenue, user growth, and market position. As much about leadership and business strategy as it is about product management.

Promotion criteria

The next step is CPO at a larger company or transition to CEO. Many VPs become CPOs at smaller companies or transition to founder roles.