Atlassian Software Engineer Interview Questions
135+ questions from real Atlassian Software Engineer interviews, reported by candidates.
Round Types
Top Topics
Questions
Atlassian OA
given an array of n integers,make the array positive with following operation: in 1 opr select any i(0<=i<n) and x(-10e8 <=x<= 10e8) and change arr[i] to x. an array is...
ATLASSIAN OA
There is a row of two-position switches aligned in a row and numbered consecutively starting from 1. Each of the switches is initially in its "Off" position. Over some number...
Got question similar to https://leetcode.com/problems/rank-teams-by-votes/ with a different tie break condition. Another question was similar to https://leetcode.com/problems/design-file-system/. Follow up was on how will you handle wildcard char e.g ? For example, if...
Atlassian SWE-II Backend Interview Experience P40 5 YOE
**I'm sharing my detailed Atlassian interview experience for SWE-II P40 backend role.** **I'll share the questions if I remember for those rounds, but most of the questions were from interview experie
I had my Karrat interview a few weeks ago. The interview was a Snake game; these kinds of questions aren't difficult, but there are many corner cases to consider and handle well. VO: Coding 1: Likou57
**Candidate Profile** * **Experience:** 13 Years (B.Tech, CSE) * **Target Role:** Principal Engineer (Remote) * **Company:** Atlassian * **Date:** September 2025 * **Outcome:** Offer down-leveled to S
**Problem** Given a product catalog linking items to departments and an ordered shopping list, calculate the efficiency gained by grouping items by department rather than picking them up in the order
**Infection Sequences Count** **Problem Description** There are $n$ houses aligned in a straight line, numbered 1 to $n$. An integer array `infectedHouses` represents the houses initially infected wit
Atlassian Senior Engineering Manager System Design Interview
1st Round: System Design Recruiter copied a question, to design image fetcher (variant of web crawler) given list of URLs, crawl URLs for images (just copy src, not image(blob) itself) and recrawl chi
Atlassian P50 Interview Experience| Jan 2025
Giving back to the leetcode community. I gave 3 rounds of interview. DS/Algo - Given a company\'s hierarchy graph with Employees and departments, I had to find the closest department between a...
Unprofessional coding interview - Atlassian
I went through Atlassian’s coding design interview recently, and the experience was surprisingly poor for a company of this scale. The exercise itself was simple: implement a small rating system where
Year- 2023, Role-Product security enggSo when i got shortlisted for interview, i didn't get many experiences that could help me prepare and know what i may face.Preparatio...
Atlassian women recruitment drive for summer internship 2022Round 1(Online Coding Round): The first round was hosted on Hackerrank. It consisted of 4 coding questions to b...
Atlassian Interview Experience for Full Time Software Engineer, Bangalore (On-Campus)
Atlassian visited our campus for Full time software engineer role hiring. Interview process was divided into 4 rounds(including initial Computer based screening round) . A...
Round 1: The test was for 90 minutes and consisted of three questions ranging from easy to hard.The first one was a fairly easy simple array traversal problem(50 marks)The...
Round 1: Online Coding RoundThe first round was hosted on Hackerrank. It consisted of 3 coding questions to be done in 90 minutes. The questions were as follows :A number ...
Atlassian | Senior Engineer P5 | India | January 2024 Reject
Status: Tier 2 BTech, 10+ YoE all in product companies in India. Position: Staff Engineer at a product company Location: India Date: January 2024 Onsite (3 rounds): Coding design round 1: Interviewer background: Interviewer was...
Asked to implement following class: //implement class to return most popular content ID class MostPopular { void increasePopularity(int contentId); int mostPopular(); void decreasePopularity(int contentId); } I wrote following solution: Basically maintaining id_to_popularity and popularity_to_id maps....
Atlassian Interview Process
I interviwed for senior software engg position and got a verbal offer. Round 1: Input list of <file_name, int size of file>, output a dashboard containining total size of the files...
1. Merge two sorted array (https://leetcode.com/problems/merge-sorted-array/description/) ##### 2. Count Analogous Arrays A covert agent has some crucial information stored in the form of an array of integers. The array contains sensitive information...
What Atlassian Looks for in Software Engineer Interviews
Atlassian Software Engineer interviews are calibrated against the level and scope expected of the role. Across 135+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.
The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.
How To Use This Question Set
Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Atlassian Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Atlassian's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.
Round-by-Round Expectations
Atlassian Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.
Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.
Common Interview Mistakes At This Combination
Reports tagged "no hire" at Atlassian Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.
Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Atlassian Software Engineer interview retrospectives on LeakCode.
See All 135 Atlassian Software Engineer Questions
Full question text, answer context, and frequency data for subscribers.
Get Access