Taro Logo

Software Engineer Intern Interview Experience - Sydney, Australia

April 1, 2022
Positive ExperienceGot Offer

Process

  1. Coding Test (took about 2 weeks from resume submission to test link) - It was a HackerRank test with 5 questions. From memory, the first three were quite easy, and the last two were about graphs and much harder.

  2. Phone Interview (took about 3 weeks from finishing the test to receiving an invitation for an interview) - A 30-minute phone call with the recruiter to see if I was a good fit for the company. It was a good opportunity to learn more about Atlassian. It's very easy to pass if you read up on the values and stick to them during the interview. The recruiter tells you if you pass during this interview and then schedules the coding interview.

  3. Coding Interview (this was about a week after the phone interview) - The interviewer was very nice and helpful in guiding me in the right direction. The question was initially about a list of files where each file had a collection name and size associated with it. I was required to calculate the total size of all the files and the total size of each collection. The question was then scaled up, where I had to find the top N largest collection sizes, and then scaled again to each file having multiple collection names.

  4. Values Interview (this was about 2 weeks after the coding interview) - The interviewer was also very nice, and the interview was very straightforward. The interviewer talked about each value and asked situational questions about each value, extending the questions occasionally. Using the STAR method helped a lot in answering most of the questions.

  5. Systems Design Interview (done in the same day as the values interview) - The interviewer was very polite and helpful in guiding me in the right direction. The question was about designing a system where a user could tag their Atlassian products (e.g., a Jira issue or a Confluence page) and also update/remove the tag. The user must also be able to view the most popular tags of all time, and it was scaled up to viewing the most popular tags in the last 24 hours. The interviewer prefers people who are upfront about what they don't know, so it was really important to be honest about it. We went through the API used and the important endpoints, then moved on to data storage and some basic flowcharts of how the client can update/remove/add tags and how the server responds.

The final offer was made 2 days after my last interview.

Overall, the recruiter and everyone who I was interviewed by were very nice and friendly and had great attitudes.

Questions

Values:

Tell me about a project you did in the past. Were there any challenges you and the team faced? If you could go back, what is one thing you would change?

Tell me about a time you couldn't meet the stakeholder's deadlines or expectations. What was their reaction? How did you respond? (Scaled up depending on my response)

Did you ever have a time where you and a group member/coworker disagreed on a solution to a problem? How did you go about solving the disagreement?

Just stick to the Atlassian values and use the STAR method to respond to each question.

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the Atlassian Software Engineer Intern role in Sydney, Australia.

Success Rate

40%
Pass Rate

Atlassian's interview process for their Software Engineer Intern roles in Sydney, Australia is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive80%
Neutral0%
Negative20%

Candidates reported having very good feelings for Atlassian's Software Engineer Intern interview process in Sydney, Australia.

Atlassian Work Experiences