The hiring process was split into multiple parts.

The first involved an online HackerRank test to be completed in 2 hours. Five questions were provided, with a minimum of two needing to be completed to advance to the next round.

These questions involved filling out function signatures (no I/O handling requirements) and were either common or similar to common problems, ranging from graphs and regular expressions to recursion.

The next stage involved a brief, approximately 40-minute conversation with a recruiter. This felt less like an interview and more like a general conversation, covering experience listed on the resume in some depth. Questions included:

• Languages used, and what was liked and disliked about them.
• General strengths and weaknesses in software development skills.

The recruiter also inquired about the company's values and which ones resonated most, advising to read about them beforehand for a prepared answer. Familiarity with Atlassian products was also discussed. Details about the role, such as the graduate program format, company culture, and office amenities, were also covered.

The final round involved three back-to-back 50-minute interviews in one day, totaling a 3-hour block with about 10 minutes between interviews. These were Skype interviews with three different engineers, each with their own format.

One interview was a general knowledge test covering data structures, systems programming, networks, and software engineering practices (e.g., Agile, Git workflows, team development). Each question started simply, with opportunities to delve deeper based on the provided detail or ability to answer.

Another interview involved screensharing for pair programming an implementation of various Java functions. This felt closest to a classic programming interview, with a similar flow and format. JUnit tests were provided in the skeleton code, with the goal to pass as many as possible within the time limit.

The third interview involved explaining a previous project. This began with a general overview, then moved into technical details about challenges faced and how they were overcome, and design choices that were particularly satisfying. An intimate knowledge and memory of the project were expected, as technical explanations were valued over high-level generalizations.

Up until that point, the turnaround time for receiving feedback and being invited to the next stage was 1-2 days. After completing the final round, it took about a week and a half to receive a phone call extending an offer.

Data structures, networks, systems programming, graphs, regular expressions