Atlassian P50 to P60 Promotions (Career Criteria)

Moving from P50 to P60 at Atlassian means showing sustained performance at the next level, as defined by your role’s current internal career framework. Build a case with clear outcomes, broader scope, and relevant influence. There is no verified public checklist or universal numerical threshold, so confirm expectations with your manager and People partner.

Preparing for promotion can save time and effort when you focus on evidence your role actually requires. It can also help you spot a gap early, before you spend months on work that does not show P60-level scope. The goal is not to collect impressive projects. It is to show, with clear examples, that your work meets the next-level expectations for your discipline.

I use a practical test: Can a reviewer see what changed because of your work, how you shaped the result, and why that work reflects the P60 rubric? A strong case answers all three. It also separates your contribution from the work of the wider team.

P50-to-P60 promotion framework and role-specific expectations

P50 and P60 are internal levels, not public certifications with one standard checklist. The expectations may vary by job family, discipline, and organization. Your first task is to obtain the current rubric that applies to your role, then agree with your manager on how to interpret it.

Do not rely on a public job title, another company’s ladder, or a third-party level chart as proof of Atlassian’s internal criteria. Public sources do not establish a universal P50-to-P60 promotion standard. The internal career framework and your manager or People partner are the right sources for current expectations.

Ask for the P50 and P60 guidance for your specific discipline and organization. Check that you have the current version, and clarify any terms that could be read in different ways. For example, “broader scope” might mean work across teams in one role, while another role may define breadth differently.

Use a short alignment meeting to answer these questions:

• Which P60 expectations matter most for my role?
• What evidence would show each expectation in practice?
• What is the review and nomination timeline?
• Who will assess the case, and what is the current process?
• Which gaps should I address before the next review?

Write down the answers and share your understanding with your manager. That creates a useful reference point as priorities change. Do not assume there is a fixed time-in-level rule, GPA-like score, or company-wide numerical bar unless your current internal guidance confirms one.

Scope, impact, leadership, and evidence

A promotion case should show how your work matches P60 expectations, not just that you completed a difficult assignment. Scope, impact, and influence may all matter, but their weight depends on your role’s rubric. Map each example to a specific expectation and support it with evidence.

Scope describes the size and nature of the problem you own. It may include ambiguity, responsibility for decisions, or work that affects more than one project. Confirm what P60 scope means for your job family rather than treating “cross-team” as a universal requirement.

Impact describes the result of the work. Use a baseline, a measured outcome, and a timeframe where available. State how you contributed, and distinguish your actions from team results. Outcomes may relate to customer experience, reliability, delivery, or risk, if those measures fit your work and rubric.

Influence means helping others move toward a sound decision or result. Depending on your role, evidence may include setting direction, aligning partner teams, sharing expertise, or mentoring colleagues. Do not add leadership claims just to fill a category. Show how the behavior connects to an expectation in your framework.

Keep a working evidence log. For each example, record the expectation, problem, your decision or action, partners involved, result, timeframe, and any feedback. Add links to suitable project records or outcome reports if your internal process allows it. A concise record is more useful than a long list of accomplishments without context.

Performance planning, feedback, and promotion-cycle execution

Treat promotion readiness as a planned process, not a surprise request at review time. Align on the rubric first, choose work that can demonstrate relevant expectations, and check progress with your manager. Follow Atlassian’s current internal nomination and calibration process; do not assume that every team uses the same steps or dates.

Stage 1: Align. Ask your manager for the applicable P50 and P60 expectations and confirm the likely cycle timing. Discuss your strongest evidence and the gaps that matter most. Turn the conversation into a short development plan with specific outcomes to check.

Stage 2: Select scope. Choose an initiative that addresses a meaningful customer or organizational need and fits your role. Before starting, agree on the problem, your decision ownership, key partners, and how success will be measured. A smaller, well-scoped effort can be more useful than a large project where your contribution is unclear.

Stage 3: Deliver and record. Track decisions and results as work progresses. Ask partners for feedback on your contribution and influence, not just the final output. If the scope or success measures change, note why and update your evidence. This makes it easier to explain what you owned and what the team achieved.

Stage 4: Calibrate and submit. Review your evidence with your manager against each relevant P60 expectation before the cycle. Ask where the case is strong and what remains unproven. If it is not ready, agree on the evidence needed, who can assess it, and a date to review progress.

A promotion case scenario

The following is an illustrative scenario, not a claim about a specific Atlassian employee or team. Imagine a P50 employee who leads a project with a positive result. The result alone may not establish readiness if the rubric also expects wider ownership, sustained performance, or influence beyond that project.

The employee and manager map the work to the internal criteria. They identify which decisions the employee owned, what changed from the baseline, and which partners can confirm the contribution. If the case lacks evidence of sustained scope, they choose a follow-up opportunity that can test that expectation. This approach avoids treating one strong project as automatic proof.

Before submitting, check that each example is relevant, specific, and supported. Remove claims that depend on visibility, effort, or a title rather than demonstrated work. The aim is a fair assessment, not the longest possible promotion packet.

Promotion is not the only useful outcome of this process. A manager’s review may confirm readiness, identify missing evidence, or show that another path better fits your interests. If the case is not supported, ask for specific examples of the gap and what would demonstrate progress. A useful answer names an expectation, an action, and a review point.

After promotion, revisit the rubric with your manager. Clarify what strong performance at P60 looks like in your role and how priorities may change. Keep tracking outcomes and feedback so you can make informed decisions about future growth, rather than assuming each next step follows automatically from a level change.

Frequently asked questions

These answers focus on what can be stated without treating internal guidance as a public, fixed checklist. Your role’s current Atlassian career framework and the guidance of your manager or People partner should settle questions about exact expectations and process.

What does it take to move from P50 to P60 at Atlassian?
Show sustained evidence that meets the P60 expectations for your specific role, using examples of relevant scope, impact, and influence. Confirm the rubric and process with your manager.

Is there a public P60 promotion checklist?
Public sources do not establish one universal P60 checklist for every Atlassian role. Request the current internal career framework for your discipline and organization.

How long must I stay at P50 before promotion?
There is no verified universal time-in-level requirement. Ask your manager or People partner whether current internal guidance sets a timing rule for your role or cycle.

Does one successful project prove P60 readiness?
Not necessarily. A project can provide useful evidence, but it may not show sustained performance, the required breadth, or influence. Compare it with the full role-specific rubric.

Which metrics should I include in a promotion case?
Use measures that fit the work and rubric. Where possible, include a baseline, outcome, timeframe, and clear account of your contribution. Do not claim team results as solely your own.

Do I need to lead work across multiple teams?
Only if that matches the expectations for your role. Cross-team influence may be relevant in some cases, but it is not safe to assume it is a universal requirement.

What if my manager says I am not ready?
Ask which expectation lacks evidence, what would demonstrate it, and when you will review progress. Agree on a specific follow-up plan rather than relying on a general instruction to “do more.”

Does working longer hours improve my promotion case?
Hours worked are not a substitute for documented next-level evidence. Focus on the scope, results, and behaviors described in your current internal framework.

Can I use another company’s level guide to judge my readiness?
You can use it for general context, but not as Atlassian’s official standard. Internal P50 and P60 expectations are the basis for your promotion case.

What should I do first?
Request the current P50 and P60 rubric for your role. Then meet with your manager to identify the most important gaps, agree on suitable work, and confirm the review timeline.

(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)