My interview process was as follows:
What I observed was that the interviewer judgments were too subjective, although those subjective feedbacks weren't totally wrong.
The system design interview was my last interview before I received the rejection phone call. I believe I performed reasonably well in the interview. However, the interviewer asked multiple questions, as she should, but also tried to dictate her preferences, which is wrong even if she was right. As a result of changing my approach based on her ideas, I had to adjust the solution, specifically the database schema, which she considered confusing in her feedback!
So, this was the end, and they didn't even send a rejection email, only calling me, which is kind of weird. They should have officially sent a rejection email if I hadn't performed well.
In my opinion, it was a waste of time as the judgments were too subjective (yes, I understand judgments are always subjective to some extent) and I also didn't find the interviewers (except one of them) well-trained for conducting the interview.
Online coding: medium-level HackerRank problems (exact difficulty not recalled)
Code design: Design a router for setting and getting URLs.
Data Structures: A function that takes a list of lists of votes and returns the top 3 candidates.
System design: Design a product-agnostic tagging system for the Atlassian ecosystem. Requirements include:
The following metrics were computed from 3 interview experiences for the Atlassian Backend Software Engineer role in Sydney, Australia.
Atlassian's interview process for their Backend Software Engineer roles in Sydney, Australia is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Atlassian's Backend Software Engineer interview process in Sydney, Australia.