Atlassian | P4/SDE2 | Remote/Banaglore | June'22 [Offer]
Anonymous User
9606

Status: BTech IT
Position: SDE2 at Fintech company.
Location: Remote/Bangalore
Date: Entire June'22.
YoE: 3

Round 1 - LLD/MC (60mins)
Design an API rate limiter.
We are supposed to use an IDE and get the code up and running. Asked a few clarifying questions. Took me about 45-50 mins to get the code running. The interviewer then tested it on a few test cases. After being satisfied he modified the question so that we any usused requests quota in a given time interval are moved to the next interval. I made the code changes but we were running out of time and I was getting wrong o/p. The interviewer was nice enoough to give me anouther 5-10 mins. I was able to find the bug and resolve it. He then tested it with more test cases and the code gave the correct output. Overall, this round went very well.

Round 2 - DSA
https://leetcode.com/problems/rank-teams-by-votes/
Initially, I didn't have to worry about tie breaking which made the question a LC easy. I was then asked to write all the test cases that I would have used to make this code production ready. Then the tie breaking condition was added. There were a few tweaks to the wordings but the crux was the same. I was using separate classes for the modelling instead of just using maps like we normally do in DSA questions so that the code looks more mature. We were kind of left with only 15ish mins now because explaining the tests I had come up with itself took like 10 mins. I quickly came up with the algo and coded it up. The algorithm was correct but there were probably a few bugs in the implementation coz of which the code gave incorrect output. However, this time, I was not given any extra time and the interview was over. This interview was just okay-ish as I couldn't get the code completely running correctly for the followup.

Round 3 - HLD
Desgin a common tagging system for all atlassian products and find k popular tags.
Asked a lot of clarifying questions. Started off with BOE calculations, APIs, DB, HLD diagram, sharding, fault tolerance and then finally optimizations. There was a decent amount of cross-questioning in between by the interviewer so be prepared to have a good reason backing your design choices and know the trade offs. Overall, this round went well.

Round 4 - Values
It was all about "Tell me a about a time" types of questions. Just go through all the 5-6 Atlassian values and make up stories around them and you will be good. I think this round is just to highlight any red flags which might be a problem in a collaborative enviornment.

Round 5 - Management
This round has some overlap with the values round. Here, you will also be asked about your previous experience, your current duties, time when you had planned for a project end to end etc.

Once you clear all the above rounds, you will be matched with different teams. You will have calls with the HMs from different teams but they are not interviews. Its a 2-way street where you can also ask a lot of questions regarding the team to judge the fittment.

Compensation: https://leetcode.com/discuss/compensation/2228927/Atlassian-or-SDE2-or-BengaluruRemote

Comments (13)