When are Atlassian performance reviews? (2026)
Atlassian evaluates on a values-plus-impact split, so how you worked with other teams counts alongside what you delivered. Cycle dates vary by org, and the preparation that always pays is a record of collaboration with named beneficiaries.
Twice a year
No specific review month is published for this company, because none could be sourced from the company's own material. What follows is the cycle shape, which is what is actually knowable. Your own manager is the authority on this year's dates.
How the cycle works
Atlassian sells collaboration software and evaluates its own people partly on collaboration, which is less circular than it sounds. The company publishes a large body of material on how teams should work together, and that vocabulary — team health, retrospectives, playbooks, ways of working — is the vocabulary reviews are conducted in. If you can describe your year in those terms, your manager does not have to translate for you.
The assessment tends to be a split rather than a single score: what you delivered, and how you delivered it against stated company values. That second half is not a formality. Someone who shipped a great deal while leaving a trail of frustrated partner teams is a genuinely complicated case here, and someone whose delivery was moderate but who visibly raised the effectiveness of everyone around them is a genuinely strong one.
Timing varies by organization and has changed across years, so confirm your own cycle dates with your manager rather than assuming.
What actually gets weighed
Cross-team enablement is the axis most people underweight in their own write-up. Atlassian's products are deeply interconnected and so are its teams, which means a meaningful share of high-value work is helping another group ship. Name the team, name what they could not do before, name what they did after.
Customer-facing quality is the second axis. This is enterprise software with long-lived installations, so a fix that removed a recurring support escalation or a migration that did not disrupt existing customers is valued more highly than the effort involved suggests.
The values half of the assessment rewards specificity. "Play as a team" is not a claim you assert; it is a claim you prove with a moment where you gave something up — scope, credit, a preferred design — so a wider outcome improved.
What to have ready
- Projects where another team was the beneficiary, with that team named and their before-and-after stated.
- Support escalations or customer issues you eliminated at the root, with volume before and after.
- A short list of moments that demonstrate a stated value in practice, each one a specific incident rather than a general disposition.
- Any process or ritual you introduced or fixed that outlived the project it came from.
- Migrations or upgrades you led for existing customers, including what did not break.
Because the values half is judged on evidence too, the moments that prove it need writing down when they happen. They are the first thing people forget.