Atlassian

I went through the Atlassian SWE internship process through the campus drive. The first stage was an online coding assessment, and this was probably the stage where speed mattered the most. There were three DSA questions with a 90-minute limit. The difficulty increased across the questions, so I did not spend too much time trying to completely finish the hardest one before securing the easier marks. Candidate reports from the same campus hiring process also describe three questions in 90 minutes, ranging from easy to hard. I managed to get enough of the assessment done to be shortlisted for the interview. The technical round was quite interactive. Instead of giving me several unrelated coding problems, the interviewer spent a significant amount of time on one problem and kept extending it with follow-ups. The initial problem involved a prefix-sum type idea. I first explained the straightforward approach and then discussed how the repeated calculations could be avoided. Once I identified the prefix-sum observation, I wrote the solution and walked through it using a couple of examples. The interviewer then changed one condition of the problem and asked whether my approach would still work. This was actually more challenging than the original question because I had to reconsider the assumptions behind my solution. We also discussed time and space complexity and possible edge cases. I was asked why I preferred one data structure over another and what would happen if the input became significantly larger. A recent India-based Atlassian candidate similarly reported one DSA question with several follow-ups lasting around an hour and twenty minutes. After clearing the technical round, I had the values/HR discussion. This round was not another coding test. Instead, the interviewer asked about situations involving teamwork, disagreement, ownership and handling pressure. I was also asked about my projects and what exactly I had contributed to them. I tried to avoid giving theoretical answers and used specific examples from my project and team experiences. One question involved a situation where a teammate disagreed with my approach. I explained how we compared the alternatives rather than making the discussion personal. There were also follow-up questions asking what I would do differently if the same situation happened again. The values round was important because the interviewer kept asking for details rather than accepting short answers. Reports from selected Atlassian candidates similarly describe the second round as being focused on projects and company values. After completing the final round, I waited for the result. I eventually received the selection confirmation for the SWE internship. For me, the most important part of the process was realizing that Atlassian was not evaluating only whether I could solve a DSA problem. The technical round tested how I handled changing requirements, while the final round tested how I worked with people and explained my past experiences.