The process is quite lengthy, with three coding interviews, one system design, one management, and then one values interview.
The first coding interview is simple enough but lacks nuance, as it is outsourced and is a simple pass if you know how to code.
The next two coding interviews are internal and are supposed to focus more on process than outcome. However, since the evaluation lacks standards, it is largely up to the interviewer to decide the difficulty of the challenge and the flexibility of the evaluation.
Next up is the system design interview. Unfortunately for me, I had an interviewer who was not good at communicating (which I will justify in the next sentences).
When it came time to receive feedback, it was clear to me that the interviewer had not listened to multiple of the key features I had described, despite one of them even being drawn in a diagram.
Furthermore, one of the key reasons for failure was due to not enough depth. However, I had made sure to ask the interviewer every step of the way if he would like more details or any clarifications.
Regardless, the interviewer was satisfied with the amount of detail during the interview but criticized it afterwards, so there was not much I could do.
If you happen to have an interviewer that does not communicate, there is a very slim chance you will pass, making this lengthy process largely wasted.
(system design) design a web crawler
The following metrics were computed from 32 interview experiences for the Atlassian Senior Software Engineer role in Sydney, Australia.
Atlassian's interview process for their Senior Software Engineer roles in Sydney, Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Atlassian's Senior Software Engineer interview process in Sydney, Australia.