Principal Software Engineer 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 29% positive. To compare, the company-average is 47% positive. This is according to Glassdoor user ratings.
Candidates applying for Principal Software Engineer roles take an average of 32 days to get hired, when considering 17 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 Principal Software Engineer according to 17 Glassdoor interviews include:
Skills test: 33%
Phone interview: 27%
One on one interview: 24%
Group panel interview: 3%
IQ intelligence test: 3%
Other: 3%
Background check: 3%
Personality test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Atlassian in Nov 2023
Interview
The process was straightforward: coding interview 1, coding interview two and then system design (which should be called API design as it's not at all a system design interview; saying this from an experience with various other companies)
The recruiters are good and responsive.
The coding interviews were terrific. The engineers were very collaborative, professional and responsive to all questions, with rapid and straightforward answers.
The API design (again, not a system design) interviewer was irritated from the beginning, totally unprofessional (was increasing the stress rather than eliminating it by making unnecessary comments), and did not answer the requirements inquiry or provided half answers.
For instance, some of what I asked:
- How many users will be using the system (which is an obvious question in SysDesign)
-- Response: It can be any
- Are there any limitations on the input from length POV?
-- Response: It can be anything.
- Is the system going to be read or write heavy?
-- Response: What do you think?
- Will the API allow writing in bulk?
-- Response: Hmmm, lets say it could be.
Advise: don't waste your time with them as they do not know how to assess talents.
Interview questions [1]
Question 1
The questions were easy for a principal position, mostly from leet code easy/medium questions.
You can find the questions in other reviews.
Standard process for a platform engineer (SRR) role, around what you have completed. Completing a coding exam on data structures for this role is unusual though. Role seemed more for application development than SRE.
Interview questions [1]
Question 1
Coding exam around structures. Example of where you have encountered difficulties in role.
Coding task, algorithms. It was not very difficult, all worked. But probably was not as good as it should be. Interviewer was polite and professional, task was described, we had a chat about solution steps.
Interview questions [1]
Question 1
What is the computational complexity of solutions algorithm's?
I applied through a recruiter. The process took 2 months. I interviewed at Atlassian (Bengaluru) in Sep 2025
Interview
Had a great interview experience at Atlassian. The HR of company are friendly and responsive, interviewers are knowledgeable and positive during interview. I had a total of 6 rounds of interview
1. HR - HR just asks about your experience and check skills based fitment.
2. System Design - Question - Design a Url Scarping System. I was able to solve this. However the expectation is go deep and design the core Scrapping API. Which I was able to do after the interviewer insisted. So be ready to show case your API design skills, URL, Request, Response, Data Model etc. Also be ready to provide the tech stack along with tradeoffs.
3. Leadership and Craft - Lot of questions around delivery, project management, stakeholder management, mentoring etc. I did pretty well in this.
4. Values - This is about atlassian values, HR will tell you how to prepare for this. I did pretty well.
5. Data Structure - Last Hero Problem. In an F1 race find the person who has done fastest lap in all of race. I solved it using HashMap of racer and max lap time. Later on I sorted the map and gave the last lap hero. I made a silly mistake and my test cases were failing. Hence I did not make it.
5. LLD - I dont remember the question. It was around Most Popular content. I used HashMap for storing content and frequency (thumbs up/thumbs Down)
Interview questions [1]
Question 1
Design a Url Scrapping System for scrapping photos from urls. You are given a list of seed urls and then you need to expand to other sites from there