SWE Intern applicants have rated the interview process at Atlassian with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 78% positive. To compare, the company-average is 47% positive. This is according to Glassdoor user ratings.
Candidates applying for SWE Intern roles take an average of 12 days to get hired, when considering 9 user submitted interviews for this role. To compare, the hiring process at Atlassian overall takes an average of 29 days.
Common stages of the interview process at Atlassian as a SWE Intern according to 9 Glassdoor interviews include:
Phone interview: 22%
Personality test: 22%
One on one interview: 22%
Skills test: 22%
Background check: 11%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 3 weeks. I interviewed at Atlassian in Jul 2024
Interview
Firstly coding round was taken after that one coding interview and one hr round was taken all the process was preety smooth, I was able to solve all of them but in the hr round got rejected
Interview questions [1]
Question 1
Make class for making a database with product tags and prices and to create several functions to get result according to several queries in sql
first an online assessment, then a technical leetcode-like interview (look mainly for clarity of thought process and how you communicate; question itself isn't too hard), and then a behavorial interview (based on company values)
Interview questions [1]
Question 1
asked me questions for each of their company values
It was good, a technical round for 1 hour where they asked a question related to OOPs and LRU. and then an LNV round for 1 hour where questions on each value of atlassian's values were asked.
I applied with a referral then passed the oa. Then I was scheduled for the technical round. The interviewer kept asking for a better time complexity answer which ultimately involved using priority heaps. I did not make it past this round.
Interview questions [1]
Question 1
something that could’ve been done with basic array/hashmap but interviewer wanted me to use heaps and reduce the time complexity