Atlassian · Software engineer · P40-P50 IC
A 60-minute spoken conversation with no coding
The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.
Atlassian’s published process. Lime marks the stage this round runs.
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.
Warm, conversational phone call with a Talent Acquisition partner
Structured, somewhat scripted third-party screen over video with a shared editor
Live coding with an Atlassian engineer in your language of choice
Second live coding session that leans toward clean structure, readability, OOP and extensibility over raw algorithm tricks
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
Relaxed, conversational, purely behavioral round usually with someone from outside the hiring team