The interview process consists of four stages:
Unfortunately, I was rejected at the design stage. For those who progress beyond this point, there are two additional rounds:
The Karat round went well, conducted by an experienced interviewer. However, Coding Round 1 did not fare as smoothly. Despite completing the task nearly flawlessly, I was down-leveled. The explanation given was the time spent deciding on a data structure.
Coding Round 2, on the other hand, received positive feedback and was reasonable.
The Design Round proved challenging, leading to my rejection due to lack of preparation. I acknowledge this, but the interview itself was difficult to follow, and understanding the expected answer was even more elusive. Despite being advised to over-communicate by the recruiter, it did not align with the interviewer's preferences.
The overall process is both lengthy and confusing. Success is not solely dependent on one's work skills but also on practicing coding and design questions. It seems to hinge significantly on the interviewer's perspective, especially in system design. The recruiter has been supportive, and the interview process is well-structured with prompt feedback.
In conclusion, for those undergoing this process, be prepared to invest a significant amount of time, with the possibility of not achieving the desired outcome.
Snake game and ballot voting.
Design: Tagging system for Jira, Confluence, Bitbucket.
The following metrics were computed from 1 interview experience for the Atlassian Senior Software Engineer - Backend role in Melbourne, Australia.
Atlassian's interview process for their Senior Software Engineer - Backend roles in Melbourne, Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Atlassian's Senior Software Engineer - Backend interview process in Melbourne, Australia.