Atlassian · Primly Community

Atlassian new grad / entry level interview, how to prep (and what I wish I knew)

jp_newgrad · 4 replies

i'm three weeks out from my Atlassian new grad interview loop and genuinely have no idea if i'm prepping for the right things. posting what i've figured out so far in case it helps anyone else.

the process seems to be: recruiter call, then a technical phone screen (one coding round, 45 min), then a virtual onsite with 4 rounds. from what i've seen the onsite breaks down roughly as: two coding rounds (data structures, algorithms, typically LC medium level) one system design (lighter than big tech for new grads, more like a design discussion) one behavioral/values round (this is the one i was NOT expecting to matter this much)

atlassian has these five core values they actually screen against. i thought it was fluff until i read a few reports from people who aced the coding rounds but got dinged in values. the values aren't obscure, it's things like "open company no bullshit" and "play as a team" but they want concrete stories with actual conflict or ambiguity, not generic team-player answers.

for the coding side: i've been doing LC mediums, priority on arrays, graphs, and string manipulation. nothing too exotic from what i can tell. they use coderpad so practice typing in a real editor, not on paper or a whiteboard.

also saw someone mention the system design for new grads was more "design a URL shortener" level, not "design YouTube at scale." so probably worth having 2-3 classic designs solid rather than depth on distributed systems.

if anyone's been through this recently, especially for a software engineer new grad role in 2026, would love to know: how many leetcode hards did they throw at you? and did the values round feel like a real conversation or a checklist?

4 replies

bootcamp_bri

went through the atlassian new grad loop in jan 2026. the coding rounds were 100% LC medium, both of them. i got a sliding window problem and a modified BFS. no hards. the values round was the one that surprised me, it was a real conversation not a checklist, the interviewer pushed back on my stories to get more specifics. like "ok but what did YOU personally do vs the team." practice narrating your actual role in projects not just "we did x."

jp_newgrad

this is so helpful, thank you. so you actually got the offer? and was the system design just one round or were there two? the JD was vague about structure.

recruiter_rita

the values piece at atlassian is legitimately screened, not just a box. i've placed candidates there and the behavioral feedback from debrief is weighted. for new grads: pick 3-4 stories from school projects or internships and make sure each one has a real conflict or decision point. "we worked well together" is not a story. something going sideways and how you handled it, that's a story.

newgrad_neil

also prepping for atlassian right now, class of 2025. the coderpad thing caught me off guard when i practiced. typing code without auto-complete in an interview is a different muscle. seriously just do a few sessions in an actual browser-based editor before the real thing.