Atlassian · Software engineer · P40-P50 IC
Coding Interview, Data Structures
Live coding with an Atlassian engineer in your language of choice
What this round is judged on
- Problem-solving · how you think, not just your output
- Learning agility · adapting when constraints change
- Edge cases · e.g. 'what if the employee doesn't exist'
- Complexity · correct time/space reasoning
- Collaboration · treating it like pairing
Where this round sits
Atlassian’s published process. Lime marks the stage this round runs.
- 01Recruiter / TA Screen
- 02Online Coding Assessment
- 03Coding Interview, Data Structuresthis round
- 04Coding Interview, Code Design
- 05Systems Design Interview
- 06Manager Interview
- 07Values Interview
- 08Hiring Committee
What happens in each stage›
- Recruiter / TA Screen
- ~25-30 min phone call on background, recent projects, why Atlassian, and level fit. Not a technical grill.
- Online Coding Assessment
- Required online coding test before the loop (community reports it is run through third-party vendor HackerRank). Roughly two coding problems plus short verbal scaling/situational questions.
- Coding Interview, Data Structures
- Live coding with an Atlassian engineer, candidate's choice of language. Practically-themed algorithm/data-structure problem, often with a base-case-then-scale-up twist.
- Coding Interview, Code Design
- Second live coding session leaning toward clean structure, OOP, and extensibility rather than pure algorithm tricks. Officially the coding interview is 'two parts: Data Structures and Code Design'; candidates often experience it as two separate rounds.
- Systems Design Interview
- 60-min spoken conversation, no code. Questions 'ladder' to your performance and 'there's no one right answer'; often narrows into concrete API design.
- Manager Interview
- ~45-60 min behavioral/career conversation about who you are, your hardest projects, collaboration, and growth.
- Values Interview
- ~45 min behavioral round mapped to Atlassian's five values, usually with someone outside the hiring team (Sales, HR/People, Customer Support).
- Hiring Committee
- Internal decision stage: a committee reviews consolidated debrief feedback and makes the final objective call. Not candidate-facing / not simulate-able.
Sources
Built from what Atlassian publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.
Coding interview is two parts (Data Structures + Code Design), any language, 'how you think' rubric; 60-min laddering systems design with no one right answer; Manager interview; Values interview with an outside-team interviewer; Hiring Committee.
'3 to 4 interviews' for early-career SWE; required online coding test before the loop; leadership and values interviews.
Verbatim five values and their taglines used in the Values interview.
Company background and products (Jira, Confluence, Bitbucket, Trello, Loom) for the blurb.
Atlassian IC ladder: P30 (entry), P40 (Engineer), P50 (Senior), P60 (Principal).
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.
Other Atlassian rounds
- Recruiter / TA Screen
Warm, conversational phone call with a Talent Acquisition partner
- Online Coding Assessment (HackerRank screen)
Structured, somewhat scripted third-party screen over video with a shared editor
- Coding Interview, Code Design
Second live coding session that leans toward clean structure, readability, OOP and extensibility over raw algorithm tricks
- Systems Design Interview
A 60-minute spoken conversation with no coding
- Manager Interview
Conversational, lower-pressure round with a hiring manager framed around 'who you are today and who you want to be at Atlassian.' Covers past projects, hardest technical challenges, the business
- Values Interview
Relaxed, conversational, purely behavioral round usually with someone from outside the hiring team