Atlassian software engineer candidates report an online assessment or Karat-style screen, timed coding, sometimes design rounds, and a values interview. Here is what they describe and how to prepare for each stage.
$161K
Avg. Base Comp
$230K
Avg. Total Comp
2-7 rounds
Typical Rounds
6-17 weeks
Process Length
Candidates describe the Atlassian software engineer interview as coding-heavy, with a values interview that carries real weight. Many start with an online assessment of two or three LeetCode-style questions, or with a Karat-style screen. Later coding rounds are usually described as medium difficulty. Reported topics include intervals, graphs, heaps, queues, binary search, group anagrams and ratings systems built on sorted structures. Several people say the interviewers cared about edge cases, optimization and complexity discussion as much as a working answer. Practice narrating your approach out loud.
Some candidates describe design work that looks more like code design than architecture. Reported prompts include a Snake game, a rate limiter, a voting system and a file report generator. One candidate describes an ambiguous system design round and another describes storing hierarchical data. The format varies by report, and a few recent candidates mention AI-assisted exercises, such as fixing a backend bug or building a MERN project with follow-up questions. Be ready to justify design choices and say where logic belongs in the code.
The final conversation is typically behavioral. Candidates mention STAR stories, Atlassian's values, a manager conversation and questions about past projects or conflict. Outcomes were mixed: some candidates received offers, and many were rejected, some after passing technical rounds with positive live feedback. Timelines also varied. Candidates describe anywhere from about six weeks to several months, with long gaps between steps.
Synthesized from 63 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Atlassian process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Atlassian
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Integer to Roman | |
| Dijkstra implementation | |
| Target Indices | |
| Target Value Search | |
| Concurrent LLM Serving | |
| Decreasing Subsequent Values | |
| Why Do You Want to Work With Us | |
| LRU Cache 1 | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Minimum Change | |
| Random SQL Sample | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Flight Records | |
| Prime to N | |
| The Brackets Problem | |
| Upsell Transactions | |
| Find the Missing Number |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call or CV screen covering background, motivation and sometimes a recent challenge. Some describe it as entirely behavioral. It is typically short, but prepare a clear answer on why you like software and why Atlassian.
Many candidates describe an online assessment of two or three medium-level DSA questions. Others describe a Karat-style screen that mixes short system design questions with coding. Reports mention edge cases, optimization and clear explanation, so practice solving under time pressure while talking through your reasoning.
Candidates report live or offline coding rounds with LeetCode-medium style problems. Topics named include intervals, graphs, heaps, queues, binary search and group anagrams. Interviewers may push for a faster or lower-space solution and ask about time and space complexity, so do not stop at the first working version.
Some candidates describe low-level or code design prompts such as a rate limiter, Snake game or voting system. Others report a system design round, which one candidate called ambiguous. One intern reported that system design was not part of their process. Expect it to vary by role and level, and ask clarifying questions.
Candidates consistently mention a final behavioral round with a manager, HR or values interviewer. Reported questions cover Atlassian's values, leadership, past projects and conflict. Prepare specific STAR stories tied to each value. Some candidates also report hearing nothing for weeks after finishing, so keep expectations flexible.
