The first stage of the interview process was to complete a series of programming challenges on HackerRank over 90 minutes. Five questions were given; however, you only had to complete a minimum of two to progress to the next stage.
After this, there was a short 30-minute phone interview to gauge your interest in Atlassian and level of technical experience.
Finally, there was a 3-hour face-to-face interview, broken up into three different sections.
The first section was a technical interview, used for the interviewer to understand the breadth of your knowledge in software development. A range of questions were asked, from the security of web applications to object-oriented design principles.
The second section asked you to explain a project you'd worked on in detail, where you had to describe and reflect on the different decisions you made completing it.
The final stage was a Java coding test, where you had to implement a class while explaining your thought process to the interviewer.
The process was very smooth, and HR did a great job communicating with me in an understanding and timely manner. I ended up declining the (very generous) offer, as I had a competing one that suited me better at the time. I would definitely recommend applying to Atlassian; however, they were very hard to turn down!
What are the differences between a list, dictionary, and set?
For a hash map implementation of a dictionary, what are the different techniques used for resolving hash conflicts between keys?
The following metrics were computed from 6 interview experiences for the Atlassian Graduate Developer role in Sydney, Australia.
Atlassian's interview process for their Graduate Developer roles in Sydney, Australia is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Atlassian's Graduate Developer interview process in Sydney, Australia.