Atlassian Software Engineer Phone Screen Questions
27+ questions from real Atlassian Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Atlassian Phone Screen round test?
The Atlassian phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Atlassian Software Engineer Phone Screen Questions
**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
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...
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...
Atlassian Virtual Onsite 2 rounds P60 (cleared)
After phone screen https://leetcode.com/discuss/interview-question/5605423/atlassian-p60-phone-screen-cleared-and-moved-to-onsite/2565567 I had 2 virtual onsite rounds 1. System Design: Design a tagging service. There will be millions of tag that we need to support. Tags can be created by...
Atlassian (P40)
Coding Round 1 1. Similar to Group Anagrams (https://leetcode.com/problems/group-anagrams/) 2. SQL (medium) 3. Data Theory : difference between Snowflake/Stake , OLTP/OLAP. When to use what. Once you clear the 1st round, they...
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...
Atlassian Interview - November 2022
Round 1: Design Snakes Games. With every 5 steps, the snake will grow by 1 Round 2: Given files and their size and collection. Return the top 5 collections on the...
Atlassian | SDE-2 | P4 | Bangalore
\tRound 1 -\xA0 similar to\xA0https://leetcode.com/discuss/interview-question/2167390/Atlassian-or-OOD-or-Design-a-middelware-router \t\t\t\t\t And then follow up was\xA0that the path can have wildcard (*) in it. Need to do regex matching in that case.\xA0 \tRound 2 - Variations...
Atlassian | SSE | Accepted
Round 1: https://leetcode.com/problems/rank-teams-by-votes/ and some of its followups. Round 2: Design an api rate limiter and machine coding it. Also, multi threading scenarios related to it. Round 3: HLD. Design a tag management...
Atlassian | SDE-2 | Remote | India
Coding Round 1 - Write code for Rate Limiter, standard for Atlassian 2. Coding Round 2 - Rank Team by Votes, instead of characters, he asked me to keep a...
Atlassian | SDE-2 | Remote [ACCEPTED]
Coding Round 1 - LLD and Code for an API rate limiter). Here you are expected to write clean code in any ide of your choice and you are...
Atlassian | P4/SDE2 | Remote/Banaglore | June'22 [Offer]
Status: BTech IT Position: SDE2 at Fintech company. Location: Remote/Bangalore Date: Entire June\'22. YoE: 3 Round 1 - LLD/MC (60mins) Design an API rate limiter. We are supposed to use an IDE and get the code up...
Atlassian | P3 | SWE | US
Phone Interview: Design HTTP Job Scheduler Onsite: Code Design Round: Design API Rate Limiter DS/Algo Round: Given list of files with file size and corresponding collections, write function to get total file size...
Atlassian | P5 | US | Offer
Status: MS in CS, 10 YOE Position: P5 Location: US (Remote) Tech phone screen: Design job scheduler Onsite: Rate limiter - mostly coding, but a little bit of design System design - create a...
Atlassian phone screen
They asked me system design for phone screen. It was a 45 minute round. Design a scheduler, that takes in 10 scheduling requests at a time and can execute 100 jobs...
Atlassian | Senior Engineer (P5) | Bengaluru | May 2021 [Offer]
Status: 7+ year experience Position: SDE2 at leading ecommerce Location: Bengaluru, India Date: May 2021 Technical Round 1 This was a code pair round where the interviewer from Atlassian and i coded for a question...
Atlassian SDE 1| Bangalore | 2022 Grad | Offer
Round 1: Online Coding Round Question 1: Array Reduction There is an array of n integers called nums. The array can be reduced by one element by performing a move. Each move has...
Atlassian | SDE 2 | P4 | September 2021 | Bangalore | Offer
Hi All, Recently I had a really nice experience with Atlassian. The entire process took about 1.5 months. HR Discussion (40 mins) 1. Detailed discussion on current projects and current roles and responsibilities. 2. What...
Atlassian | SDE 3 | Bangalore
Round 1: coding round consisting of 2 questions of Medium Hard difficulty. Problem 1: Medium level - DP question Problem 2: Hard level find articulation point in graph - https://leetcode.com/problems/critical-connections-in-a-network/ Round 2 (Again coding...
Atlassian | India | July 2021 | Reject
Status: 7y experience in product development Position: SSE Location: India Date: July 2021 Round 1- Implement a rate limiter based on userId Discussed moving window vs. fixed window solution. Pros/cons, complexity etc. and then asked me...
What to Expect in the Atlassian Phone Screen Round
The Atlassian Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 27+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Atlassian show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Atlassian typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Atlassian Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 27 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access