Software Engineer P50 at Atlassian
- Difficulty
- Process took
- 2-3 Weeks
- Rounds
- 3
- Format
- Remote
- Applied via
- Company Website
How it went
- The ghosting after three comprehensive technical rounds was particularly disappointing, as it left no opportunity for learning or improvement. Future candidates should be prepared for this possibility and continue applying to other opportunities simultaneously.
What they would tell you
- The ghosting after three comprehensive technical rounds was particularly disappointing, as it left no opportunity for learning or improvement. Future candidates should be prepared for this possibility and continue applying to other opportunities simultaneously.
How to prepare
- Focus on system design fundamentals
- Data structures like trees, graphs, and hash maps thoroughly
Their background
I'm a software engineer. I've spent most of my time working with backend systems, getting my hands dirty with databases, APIs.
Round by round
- 1
Technical Coding 160 min
This was an engaging algorithmic challenge centered around Atlassian's internal employee directory system. The interviewer presented a well-structured problem that felt very relevant to real-world scenarios at Atlassian. Questions: Design and implement a system for the team that maintains the Atlassian employee directory. The core challenge: Given that Atlassian has multiple organizational groups (with nested sub-groups), and every employee belongs to at least one group, create an efficient algorithm to find the closest common parent group for any given set of target employees. This required understanding of tree structures, graph traversal, and optimization techniques.
- 2
Technical Coding 260 min
Building a movie ticket booking system, you know, the kind you'd use when booking seats online. The interviewer wanted me to think through how people actually book movie tickets, dealing with things like multiple people trying to grab the same seat at once, and figuring out the best seats for families or groups. It felt pretty real-world and relatable. Build a movie theater booking system from scratch. Think about how you'd handle situations where two people click on the same seat simultaneously, how to suggest the best available seats when someone wants 4 tickets together, what happens when someone cancels their booking, and how to manage different ticket prices for premium seats. Basically, all the messy real-world stuff that happens when people book movie tickets online.
- 3
System Design60 min
Most challenging and interesting round of the entire process.Design a comprehensive system for Confluence feeds that can handle popularity-based content ranking. Consider scalability, real-time updates, personalization, and performance optimization. Discuss database design, caching layers, recommendation algorithms, and how to handle millions of users accessing content simultaneously.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.