Atlassian Senior Front End Developer interview questions
based on 8 ratings - Updated Jun 12, 2025
Averageinterview difficulty
Mixedinterview experience
How others got an interview
71%
Applied online
Applied online
14%
Recruiter
Recruiter
14%
In Person
In Person
Interview search
8 interviews
Viewing 6 - 8 of 8 Interviews
Atlassian interviews FAQs
Candidates applying for Senior Front End Developer roles take an average of 2 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Atlassian overall takes an average of 29 days.
Here are the most commonly searched roles for interview reports -
The interviewers here are most dishonest with their feedback,even you solve problems and align with the process and values that recruiter shares in prep doc,its waste of your time and effort when you get the feedback that is not at all honest with what happened with that 1 hour of your time with the interviewer
I applied online. I interviewed at Atlassian (Sydney) in May 2021
Interview
While only a pre-screen interview, the questioning was thorough and clear on the process ahead if I was successful.
Even though it ran over time, I was only encouraged to move along. I was not forced nor cut off.
I applied through a recruiter. The process took 2 days. I interviewed at Atlassian in Feb 2019
Interview
Painful. Started with bumpy introductions (from the interviewer) then on to the coding challenge. I interview candidates regularly at my job and introductions are usually the easiest part but I figured maybe this was the interviewer's first time.
The coding starts and I explain my thought process and the code as I write it. During this I pointed out that I almost never have the optimal solution on the first go. Generally I find a solution then optimize it but as things progressed it seemed the interviewer expected a minimal complexity- character-for-character solution on the first try.
By the end what started as "find the intersections" became "count the occurrences" while finding the intersections but also reducing complexity and use a literal object but not as a hash map like you mentioned in the beginning. The hints became so misleading I wasn't even sure of the problem I was solving anymore and the interruptions to my solution completely fried my ability to think through the problem.
Needless to say I did not pass the interview but towards the end I frankly didn't want to. I was stuck trying to understand the requirements and their expected solution but when I asked for clarification I received the equivalent of "google it".
At the end of a failed interview there is no reason the interviewer can't explain the solution he or she was looking for... unless they can't explain it.