How to Get Promoted from PM to Senior PM at Atlassian

You shipped a strong quarter. Your squad's metrics are up. You got positive feedback in your last review. Your manager said "keep doing what you're doing."

Then you watched a peer with similar tenure get promoted to P50, and nobody told you what they did differently.

At Atlassian, the jump from PM (P40) to Senior PM (P50) is where the job description changes. P40 is about owning your squad's roadmap. P50 is about owning a product area's strategy and influencing teams you don't directly work with. The work looks different, the expectations are different, and the compensation reflects it: median total comp jumps from $209K to $321K, a 54% increase driven mostly by stock.

How Atlassian promotes product managers

Atlassian runs a structured, manager-led promotion process. There is no self-nomination system. Your manager submits a promotion case through a Jira Service Management (JSM) platform that connects to Workday, the company's HR system.

After submission, a global promotion panel reviews the case for consistency across teams and geographies. Engineering panels have 80+ members; the PM panel is smaller but follows the same structure. After the panel signs off, finance approves the compensation change, and the promotion lands.

Four things to understand about how this works in practice:

• Your manager is the gatekeeper. They write and submit the case. If your manager doesn't see P50-level work, the conversation never starts.
• Panels enforce consistency. A strong manager recommendation is necessary but not sufficient. The panel checks that your case meets the same bar as promotions across other teams and offices.
• Comp changes route through finance. The P40-to-P50 jump more than doubles your stock grant (from ~$43K to ~$99K annually). Finance reviews every case at this level.
• The system is transparent for managers. Managers can track promotion rates and outcomes in the JSM system, which means your manager knows exactly where your case stands in the pipeline.

What changes between P40 and P50

Senior PMs at Atlassian operate at a different altitude. The four pillars of Atlassian's PM framework (lead and inspire, craft mastery, communication, outcome delivery) stay the same, but the expected scope expands on every dimension.

Dimension	PM (P40)	Senior PM (P50)
Roadmap ownership	Your squad's roadmap	Product area strategy across multiple squads
Problem identification	Scoping solutions for problems leadership defines	Identifying which problems the product area should solve next
Influence	Aligning your squad (eng, design, data)	Aligning across squads, with leadership, with adjacent product areas
Decision making	Following established frameworks; escalating ambiguity	Building decision frameworks for your area; resolving ambiguity for others
People development	Not expected	Mentoring junior PMs; shaping how your area's PMs think about problems
Impact measurement	Squad metrics (feature adoption, engagement)	Business-level outcomes (revenue, retention, platform health)
Stakeholder communication	Reporting progress to your manager	Presenting strategy and trade-offs to senior leadership

"The biggest shift is going from 'I own my squad's roadmap' to 'I own the strategy for this product area and the roadmap is one output of that strategy.'"

The criteria that matter for P50 at Atlassian

Outcome delivery at the product-area level

P40 PMs deliver outcomes for their squad. P50 PMs deliver outcomes that move the needle for a product area or business unit. The difference is the type of thinking required, not the volume of work.

At P40, you might measure success by feature adoption or engagement within your surface. At P50, you connect those metrics to revenue, retention, or ecosystem health. When your manager writes the promotion case, they need to point to business-level impact that affected more than one squad. Give them the data to make that argument.

Cross-functional leadership without authority

Atlassian's PM framework calls this "lead and inspire." At P50, it means influencing engineers, designers, data scientists, and other PMs who don't report to you. You build consensus across squads. You deal with competing priorities. You translate between technical and business language.

In practice, this shows up in how you handle disagreement. P40 PMs escalate cross-squad conflicts. P50 PMs resolve them. If other PMs come to you to help untangle competing priorities, that is P50 evidence.

Strategic ownership

P50 PMs own the "why" for their product area. You should be the person who can explain why your area is working on what it's working on, what the 12-month vision looks like, and what you would cut if resources shrank by 30%.

Atlassian's job postings for Senior PM roles mention "annual plans," "business case development," and "product-led growth." That is business-level thinking expressed through product decisions, not feature-level execution.

Team empowerment

Atlassian values PMs who build shared decision criteria and empower teams rather than controlling decisions from the top. At P50, you're expected to create the conditions for good product decisions across your area, not make every decision yourself.

This includes mentoring junior PMs, building frameworks that help engineers and designers make product calls on their own, and establishing processes that survive when you're on vacation.

Building your case for P50

Have the specific conversation with your manager

Not "how am I doing?" but "what does P50 readiness look like for me, and what evidence is missing from my case?" Ask which of the four PM pillars they see at P50 level and which ones still read as P40. Ask what the promotion panel would want to see.

Because your manager writes the JSM case, this conversation is not optional. They need to know you're aiming for P50, and you need to know what they'd write if the case were submitted today.

Find product-area problems to own

Look for problems that span multiple squads or require coordination across teams. These are often visible but unowned: inconsistent user experiences across product surfaces, data pipelines that three squads depend on but nobody owns at a strategic level, or growth opportunities that sit in the gap between two squads' mandates.

At Atlassian, where products like Jira, Confluence, and Trello have deep integration points, these cross-squad problems are everywhere. If you wait for someone to assign you product-area-level work, you'll wait a long time. P50 PMs identify these problems and propose a plan.

Use Atlassian's built-in growth rituals

Atlassian's senior PMs recommend four specific practices for building your case:

• Skip-level meetings with leadership. These give you visibility with the people who sit on promotion panels and allocate resources. They also force you to practice communicating at a strategic level.
• Quarterly product/design reviews. Present your area's strategy to leadership. This builds the muscle of compressing complex product areas into clear narratives.
• Biannual demo trusts. Demonstrate impact in a structured setting. These are direct evidence-building opportunities for your promotion case.
• Regular 1:1s with other PMs. Cross-PM feedback loops help you calibrate your work against P50 expectations and build the influence network you need.

Document impact at the business level

Stop measuring success only in feature launches and adoption numbers. Start connecting your work to the metrics your product area is accountable for. When possible, run experiments that quantify the revenue or retention impact of your decisions.

Atlassian's PM framework is built around data-driven decision making and OKRs. Your promotion case is stronger when you can show a chain from your product decisions to measurable business outcomes.

Mistakes that keep PMs stuck at P40

Optimizing squad metrics in isolation. You hit every squad-level target, but your work doesn't connect to product-area or business outcomes. P50 cases require evidence of cross-squad impact. Move up the metric stack.

Waiting for your manager to bring up promotion. Atlassian's JSM system gives managers visibility into promotion rates, but it doesn't create urgency for any specific case. If you don't initiate the conversation, your manager may assume you're content at P40. Own the timing.

Staying in execution mode. You ship features, run sprints, hit deadlines. All of that is P40 work, and it's necessary. But it is not what separates P40 from P50. The gap is strategy. If you spend all your time in delivery, you have no time for direction-setting.

Avoiding cross-squad complexity. Product-area influence means dealing with competing priorities between squads. Some PMs avoid this because it creates friction. P50 PMs walk toward it because that's where the highest-leverage decisions happen.

Treating the PM pillars as a checklist. Atlassian evaluates PMs on four pillars: lead and inspire, craft mastery, communication, and outcome delivery. P40 PMs sometimes try to "check the box" on each. P50 PMs show how the pillars reinforce each other. Your leadership enables outcomes. Your communication shapes strategy. The pillars are connected, not independent.

Timeline and expectations

Path	What it looks like	How common
2 years at P40	Strong performers who find product-area problems early and build influence fast	Uncommon
2-3 years at P40	Solid path. Consistent P50-level work across two or more review periods.	Most common
3-4 years at P40	Includes a slow start, a team change, or rebuilding after a reorg	Common
4+ years or stays at P40	P40 is a viable long-term level. Some PMs stay by choice or circumstance.	Not unusual

The compensation increase is hard to ignore. Median total comp goes from $209K at P40 to $321K at P50, with the stock component more than doubling (from ~$43K to ~$99K annually). Base salary increases from $153K to $198K. Bonus grows from $13K to $24K.

At P50/P60, the career ladder splits. You can continue on the IC track toward Principal PM (P60) or move into people management. This split makes P40-to-P50 a decision point about your career direction, not only a promotion. Think about which track you want before you get there.

Frequently asked questions

How long does it take to get promoted from PM to Senior PM at Atlassian?

Most PMs who reach P50 spend 2-4 years at P40, with 2-3 years being the most common path for strong performers. Atlassian expects 4-7 years of total PM experience at the P50 level. P40 is a viable long-term level, so there is no automatic progression or pressure to advance.

How does Atlassian's promotion panel work?

Your manager submits a promotion case through a JSM platform integrated with Workday. A global panel reviews the case for consistency across teams and geographies. Finance then approves the compensation change. The process prevents inconsistency between teams or offices, but it also means a strong manager recommendation alone is not enough.

What if my manager agrees I'm P50-level but the promotion doesn't happen?

The blocker is likely at the panel level. Ask your manager directly: "Has the case been submitted? If so, what feedback came back from the panel?" It is also possible your manager agrees in conversation but hasn't formally initiated the JSM submission. Ask whether the case is in the system.

Does Atlassian have fixed promotion cycles?

Atlassian's promotion process is ongoing, but promotion panels typically review cases in batches. The exact cadence varies by organization. Ask your manager when the next panel review is scheduled so you can align your evidence-building timeline.

Should I switch teams to get promoted faster?

Switching teams resets your context and relationships. If your current team has no product-area-level problems to solve (small team, limited scope), moving could help. But if you're switching because you think a new manager will advocate harder, the reset cost is usually not worth it. Build the case where you are first.

---

CareerClimb helps you build your promotion case week by week. Track your wins, map them to what Atlassian's PM framework evaluates, and know where your case is strong before your manager writes the JSM submission. Download CareerClimb