Atlassian Hiring Process, From Code Design to Committee

The Atlassian interview process runs five stages: a recruiter screen, a technical phone screen, a virtual onsite of about four to five rounds, an independent Hiring Committee, then an offer. The onsite bundles two coding rounds, a system design round, a manager conversation, and a separately scored Values Interview. Recruiter call to decision commonly takes four to six weeks. Atlassian's own engineering interview guide lays out the loop: coding in two parts, Data Structures and Code Design, then systems design, a manager interview, a values interview and an independent Hiring Committee.

An Atlassian loop runs entirely over video, from the first recruiter call to the last round. There is no in-person onsite to fly out for, because Atlassian hires under a distributed model it calls Team Anywhere. The rounds are what you would mostly expect: a recruiter screen, a set of technical interviews across coding and system design, and a hiring-manager conversation. What sets the loop apart is one extra round most companies do not run at all, a dedicated Values Interview that is scored on its own rubric and weighted the same as any coding round. So two facts shape how you prepare: the loop is remote by default, and clearing the technical bar is only half of what gets you an offer.

Atlassian builds the software teams run on: Jira for issue tracking, Confluence for docs and wikis, Trello and Bitbucket, plus a Marketplace of third-party apps layered on the Cloud platform. The interview that gates those teams looks familiar at first glance, with medium-difficulty data-structure problems, a system design round, and a manager conversation. What bends it toward Atlassian is the coded Code Design round, where you get a business-framed prompt with function signatures already written, produce runnable code that passes tests, then defend and extend it under follow-ups. You bring your own IDE, pick your own language, and Googling syntax is fine. The people grading care more about how you reason than whether you remembered an exact API.

The Atlassian angle

Treat the Values Interview as a real gate: a weak values read is the likeliest reason a strong coder walks away with no offer. It is run by an impartial interviewer from outside the hiring team, scored on its own, and weighted equally with your technical rounds when the committee decides. The five values have been stable for well over a decade. Learn them verbatim, and quote the third one's profanity as written, since it is intentional and official: Open company, no bullshit; Build with heart and balance; Don't #@!% the customer; Play, as a team; Be the change you seek. Bring two concrete STAR stories per value, in the first person and landing on a specific result, because interviewers are trained to push past rehearsed answers until they hit real detail or a wall.

The Pipeline

The loop runs in five stages: a recruiter screen, a technical phone screen, the virtual onsite, an independent Hiring Committee, then an offer. Recruiter call to decision commonly spans four to six weeks. Two things flex by pipeline. The early technical screen splits by cohort, and the number of onsite rounds shifts with your level and craft. The anchor numbers sit below.

• 5 Core values. Scored in a standalone, impartial round.
• ~4 to 6 wks End to end. Recruiter call to decision, self-reported.
• ~4 to 5 Onsite rounds. Two coding, design, values, manager; varies by level.
• 100% Virtual. No default in-person onsite under Team Anywhere.

Where you enter decides your technical phone screen. Experienced and lateral hires often get a third-party-administered screen of about sixty minutes. It opens with rapid verbal reasoning on debugging and scaling a slow system, then moves to two must-run coding problems, usually one easy and one medium. New-grad, campus, and early-career candidates more often get a HackerRank assessment of two or three problems in about ninety minutes. It tilts toward string manipulation, parsing, greedy, and simple dynamic programming, and the lighter internship and new-grad loop is built around it. A retake is sometimes offered. Not everyone gets an online assessment, so confirm which path you are on with your recruiter rather than assuming a fixed cutoff.

Laid out in order, the path runs through five stages.

The Atlassian angle

No single interviewer can sink you or save you. Atlassian does not let the loudest voice in the room decide. An independent Hiring Committee reads the written feedback from every round, then sets both the hire call and your level holistically. The Values scorecard sits in that packet with full weight, right alongside your coding and design rounds. This structure has one friendly consequence. When a candidate is close but has one soft dimension, the committee can request an extra top-up round instead of rejecting outright. A single wobbly hour is not always fatal.

The P-Level Ladder

Atlassian ICs sit on a numbered P-scale. Public comp sites render it P30, P40, P50, P60, P70, while inside the company people say P3 through P7. It is the same ladder with a trailing zero. There is no separate Staff title, and managers sit on a parallel M track. The years below are directional floors rather than gates, because Atlassian levels on demonstrated scope more than time served, and promotion past the middle is reportedly slow.

The Atlassian angle

Confirm the level before you fall in love with the offer. Moving up a rung resets your pay far more than any in-band negotiation will, and because promotion past mid-level is slow, the level you are hired at tends to stick for a while. Atlassian pays in liquid public RSUs plus a company-performance bonus, and the equity grant is the real lever once the level is set. If your scope sits near a boundary, ask which level the loop is calibrated for. Make sure the offered rung matches the work you would own, whatever title you held before.

What Makes the Atlassian Loop Different

Strip away the familiar parts and a handful of things give the Atlassian loop its character. Most of them trace back to a company that sells collaboration software and hires people who can build it cleanly and work well with others.

The Code Design Round Is the One to Drill

One round deserves singling out before you plan your prep. The Code Design half of the coding loop is where senior candidates most often stall. It is not whiteboard object modeling. It is low-level design you actually run: a real-world prompt, a set of function signatures, and a clock working against you. A complete, tested implementation inside the hour is hard, and interviewers grade whether you got there. Practice by building small, extensible things end to end and writing your own tests, rather than by memorizing algorithm templates. The coding section of this guide is organized to drill both the tree-heavy data-structure spine and this Code Design muscle.

What This Guide Covers

The rest of the guide turns each stage into concrete preparation. Where a detail comes from candidates rather than from Atlassian's own material, the guide says so instead of stating it as policy.

Common questions