P40 at Atlassian

How it went

What they would tell you

How to prepare

Their background

Round by round

1. 1

   HR Call10 min

   I applied directly on their portal, first call was related clarified my expectations, experience, and why Atlassian.

2. 2

   Karat Technical Screening60 min

   A rapid-fire system design chat mixed with a coding challenge. Question 1: Facebook Clone

   • The problem focused on adding a numeric count of friends to every post in a Facebook clone. The database schema was given, and I had to explain how I would implement this feature, considering scalability, caching, and performance. Question 2: Google Docs Clone

   • This one asked me to design the collaborative editing and version control system for Google Docs. The interviewer was looking for solutions that would scale, so I had to focus on horizontal scalability and redundancy strategies. Question 3: Bug Investigation

   • There was a scenario-based question about debugging where I had to find out how to detect missing IDs from a large set of failed API requests.

3. 3

   Data Structures Interview60 min

   Question: We were given a set of services with latencies between them, and the task was to find the minimum latency between a pair of services using efficient graph traversal techniques. I explained why DFS and BFS weren’t optimal for this and then discussed using Dijkstra's Algorithm to solve the problem efficiently. The interviewer seemed happy with my understanding of graph traversal algorithms.

4. 4

   Code Design Interview60 min

   Question: Customer Satisfaction System We had to design a system where users could rate customer support agents. The system had to calculate the average ratings and rank agents based on this data. We also discussed how to handle data persistence, scaling, and optimizing for quick lookups.

5. 5

   System Design Interview60 min

   Question: Tagging Management Service The interviewer wanted me to design a tagging system that would allow users to tag content across different Atlassian products (Jira, Confluence, etc.) and search/filter by tags. The system needed to be flexible, allowing new products to be added seamlessly in the future I covered the database schema design, use of indexes, and caching strategies for optimal search performance. We also talked about API specifications and rate limiting.

6. 6

   Managerial60 min

   This was behavioral interview where simple question related to leadership qualities, conflict resolution, and how I handled situations where team members disagreed with my approach. We also discussed my past projects and how I made engineering decisions.

7. 7

   Round 760 min

   The values interview focused on understanding how I align with Atlassian’s culture

   • Sharing an example of when I was able to improve the performance of an individual or a team.
   • Describing a situation where I had to reach a compromise with someone to move a project forward.
   • Talking about a time I accidentally shipped a bug or mistake to a customer or stakeholder and how I handled it.
   • Explaining a project where I built a solution end-to-end, from planning to delivery.
   • Discussing an instance where I had to provide constructive feedback to a colleague.

What came up