Atlassian interview rounds
Pick your level above: the list shows only your rounds, with what interviewers score at that level.
-
Phone / recruiter screen · 30 min
A recruiter call about background, motivation, location and pay, where the target level gets set.
At : Usually one medium problem. Explain your idea before coding and test by hand at the end.
At : One or two problems, a little faster. Some companies mix in a design question.
At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.
At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.
-
Phone / recruiter screen · 60 min
An outsourced interviewer (Karat) runs it: about 20 minutes of quick-fire design or fundamentals questions, then one or two easy-to-medium coding problems.
At : Usually one medium problem. Explain your idea before coding and test by hand at the end.
At : One or two problems, a little faster. Some companies mix in a design question.
At : Often a coding problem plus questions about your past systems; some companies (Uber) use it to set your level.
At : Frequently a hiring-manager conversation about scope and impact instead of pure coding.
-
Online assessment · 90 min
Intern and graduate candidates report a timed test with two or three DSA problems before any live interview.
At : The main filter for new grads and campus drives. Expect two medium problems, sometimes one hard. Passing all test cases on both usually gets you to the next round.
At : Used by some companies for experienced hires (Amazon, Uber, Salesforce, Oracle). The bar is the same as for SDE 1 but the time is often shorter.
At : Rare. Most companies replace it with a live screen for senior candidates.
At : Almost never used.
-
Coding (DSA) · 60 min
The 'Data Structures' half of the coding interview: an algorithm problem with follow-ups, scored on clean code, naming and testing your own work without being asked.
At : The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.
At : Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.
At : Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.
At : One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.
-
Low-level design / machine coding · 60 min
The 'Code Design' half: build a small working component that can be extended, such as a popularity tracker, then handle new requirements, tie-breaks and concurrency.
At : Object-oriented design with clear classes and responsibilities. Working code matters more than patterns.
At : The core round at many product companies: working, modular, extensible code with validation, error handling and tests, finished on time.
At : Same as SDE 2 plus concurrency (two users booking the same seat) and a clean extension story.
At : Rare as a standalone round; folded into design discussions.
-
System design (HLD) · 60 min
A systems design discussion with no coding, where the interviewer adjusts the follow-ups to see how you adapt to new trade-offs.
At : Usually absent, or light design questions inside a coding round.
At : Present at most companies. A sound end-to-end design with sensible components and basic scaling is enough.
At : One or two rounds that set your level. Expected to lead, size the system and go deep on two or three hard parts.
At : Two rounds at many companies. Expected to handle ambiguity, cost, operations and cross-team trade-offs, and to change the design when the interviewer pushes.
-
Hiring manager · 60 min
One past project in depth, ownership, mentoring and how you collaborate.
At : Motivation, learning, a project walk-through and sometimes CS fundamentals.
At : Ownership of features, handling production issues, working with product and other teams.
At : Technical leadership, mentoring, and how you choose what to work on.
At : Strategy, influence without authority and the biggest bets you have made.
-
Behavioral · 45 min
The values interview, usually led by someone outside engineering, with roughly one question per value and probing follow-ups.
At : Stories from internships, projects or your first job are fine. Show learning, ownership and teamwork.
At : Stories should show you owning features end to end and handling conflict maturely.
At : Expected scope: projects across quarters, influencing other teams, mentoring.
At : Expected scope: org-wide impact, setting direction, hard trade-offs with leadership.
-
Hiring committee
An independent committee reviews all the feedback and the CV and makes the final call.
At : Mostly about whether the packet clears the bar; team match can take a few weeks.
At : Committees can down-level you instead of rejecting.
At : Down-leveling to SDE 2 is the most common surprise outcome.
At : Staff packets get extra scrutiny on design and behavioral scope.
-
Team match · 30 min
Approved candidates are sometimes placed on a team only afterwards, and some wait weeks for a match.
At : Mostly about whether the packet clears the bar; team match can take a few weeks.
At : Committees can down-level you instead of rejecting.
At : Down-leveling to SDE 2 is the most common surprise outcome.
At : Staff packets get extra scrutiny on design and behavioral scope.
What interviewers look for
- Readable, production-quality code rather than clever one-liners
- Testing your own code without being prompted
- Explaining trade-offs out loud
- Design that extends cleanly when new requirements arrive
- Owning a past project end to end and why it mattered
- Real examples, with humility, behind each value
Worth knowing
- The official guide splits the coding interview into 'Data Structures' and 'Code Design'.
- An outsourced interviewer runs the first technical screen for experienced hires; a redo is often offered.
- The values interviewer usually comes from outside engineering.
- Final decisions go to an independent hiring committee; some candidates wait weeks after it for a team match.
- Some 2026 candidates report AI-agent coding rounds; not yet universal.
Sources
Written in our own words from public candidate reports and Atlassian's careers pages, checked 2026-11. Company names and logos belong to their owners; AlgoRung is not affiliated with Atlassian.
- leetcode.com/discuss/post/8293408/atlassian-interview-experience-p50p40-by-21ky/
- leetcode.com/discuss/post/6807250/atlassian-software-engineer-2-may-2025-3-ayr9/
- leetcode.com/discuss/interview-experience/7196860
- leetcode.com/discuss/interview-experience/7099587
- leetcode.com/discuss/interview-experience/5757617/
- leetcode.com/discuss/interview-experience/5185865/
- talentd.in/fleetcode/companies/atlassian
- lets-code.co.in/previousyearcodingquestion/atlassian-previous-year-coding-questions
- prachub.com/companies/atlassian/categories/coding-and-algorithms
Questions people ask
How many interview rounds does Atlassian have for SDE 1 (P30 Graduate / entry Software Engineer)?
About 3 interviews after the screening: phone / recruiter screen, online assessment, coding (dsa), low-level design / machine coding, behavioral. Design is part of the loop at this level.
How many interview rounds does Atlassian have for SDE 2 (P40 Software Engineer)?
About 5 interviews after the screening: phone / recruiter screen, coding (dsa), low-level design / machine coding, system design (hld), hiring manager, behavioral, team match. Design is part of the loop at this level.
How many interview rounds does Atlassian have for SDE 3 (P50 Senior Software Engineer)?
About 5 interviews after the screening: phone / recruiter screen, coding (dsa), low-level design / machine coding, system design (hld), hiring manager, behavioral, team match. Design is part of the loop at this level.
How many interview rounds does Atlassian have for staff (P60 Principal, P70 and above)?
About 5 interviews after the screening: phone / recruiter screen, coding (dsa), low-level design / machine coding, system design (hld), hiring manager, behavioral. Design is part of the loop at this level.
What coding questions does Atlassian ask?
The most reported are Lowest Common Ancestor of a Binary Tree, Rank Teams by Votes, Design Snake Game, Merge Intervals, Two Sum, All O`one Data Structure. Candidates say Atlassian focuses on hash maps, heaps, trees, graphs, intervals.
What is the Atlassian behavioral interview based on?
Company values: Open company, no bullshit, Build with heart and balance, Don't #@!% the customer, Play, as a team, Be the change you seek. A dedicated values interview tests fit with all five values, usually one question per value, led by an interviewer from another department. Strong technical scores do not make up for a weak values result.