A values round that genuinely counts, and design questions about multi-tenant SaaS rather than consumer scale.
Atlassian is unusual in that its values interview is a real round with a real ability to sink an otherwise strong loop. It is not a culture chat. Interviewers probe for concrete evidence against each value, and answers that stay abstract - "I believe in collaboration" - score poorly next to a specific story with a decision and an outcome.
The technical rounds are shaped by the product: multi-tenant SaaS, not consumer social scale. Expect design questions about tenant isolation, permissions models that stay correct across nested projects, webhook and integration reliability, and migrating a schema without downtime for customers who cannot all be upgraded at once.
45-60 min
Practical problem solving, often extending existing code rather than a blank file.
60 min
Multi-tenant SaaS: isolation, permissions, integrations, migration safety.
60 min
Structure, testability and maintainability of the code you write.
45-60 min
Specific stories mapped to Atlassian values. A genuinely weighted round.
Yes - candidates are rejected on it. Prepare it like a technical round: pick concrete stories, map each to a value, and make sure every story contains a decision you made and an outcome you can state.
B2B SaaS problems rather than consumer scale. Tenant isolation, a permissions model that holds up across nested projects, third-party integration reliability, and migrating customers safely without a synchronised cutover.
It scores structure rather than speed. Naming, separation of concerns, testability and handling of error paths matter more than reaching the optimal algorithm, and you are often extending existing code rather than starting from empty.
Practise the rounds Atlassian actually runs, and get scored on where you stand.