I received a quick phone call from a recruiter. They then signed me up for a coding challenge, which was fairly simple. After passing the coding challenge, we set up another technical phone interview with two members of the potential team.
Following that, there was an on-site interview. The interview was pretty disorganized in general. They definitely thought I was a different candidate, and the process itself was kind of a mess. The people were lovely to talk to. It was definitely one of the tougher on-site interviews I've done.
Coding Challenge: How to convert numbers from one base to another.
Phone Technical: A question about fruit baskets. Essentially, calculating frequencies of powersets of many sets.
Technical Onsite #1: Find the area of the shade a skyline casts (Think of it as a 2D plot).
Technical Onsite #2: Lots of theoretical CS and math-y questions. It was hard to understand the goal of this interview at times.
System Design: Designing a microservice within the Atlassian architecture. Nothing too difficult. Microservice should be able to calculate time-based metrics.
The following metrics were computed from 6 interview experiences for the Atlassian Software Engineer role in Mountain View, California.
Atlassian's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Atlassian's Software Engineer interview process in Mountain View, California.