Microsoft SDE Intern Interview Experience
💼 LTIMindtree Interview Experience (On-Campus) | Fresher | 2026
Salesforce SMTS | Interview Experience | Rejected
JPMC | SDE2 (Associate) - Java Backend - Interview Experience + Compensation
Microsoft - SDE2 - Coding Round
Atlassian P40 | Accepted
Summary
I recently interviewed at Atlassian for a P40 role, which involved 5 rounds covering DSA, LLD, HLD, Values, and Managerial. I received an offer after approximately two weeks, even though I didn't fully complete all follow-ups, as Atlassian focused on my thought process.
Full Experience
I recently interviewed at Atlassian for a P40 role. The process consisted of 5 rounds:
YOE ~ 4
Recruiter reached out through Linkedin.
- Round 1: DSA
Variant of all O(1). There was a followup as well but don't remember that right now. - Round 2: Rating System (LLD)
The task involved designing a system to rate and calculate a list of customer care reps sorted by their avg rating.
Followup -
Different tie breaker conditions.
How to handle in case of concurrent env. - Round 3: System Design (HLD)
This round revolved around designing a tagging system, and extension was creating a dashboard for top k tags by popularity.
I was grilled on API endpoints (http methods used, what and why for params/request body, pagination etc), kafka vs sqs vs rabbitmq, cassandra/dynamodb vs postgres for storing tags data.
Was using flink + redis sorted set as the latency requirements for top k tags was < 5 mins, so had to explain those choices over alternatives. - Round 4: Values
Atlassian has 5 values, 1 question from each. - Round 5: Managerial
This went for 70 mins, non-technical but in depth questions on the work you do. Should highlight impact. Amazon LPs are a great resource to prep for these kind of rounds.
Outcome
Got an offer after ~2 weeks, team match took 2 days.
Atlassian's evaluation is different as they look for red flags even if solution might be correct. I was not able to complete followups for round 2 and discussed orally (concurrency), but they were looking a lot more at thought process and conceptual understanding instead of correctness of solution.
Interview Questions (2)
The task involved designing a system to rate and calculate a list of customer care reps sorted by their average rating. Follow-up questions included handling different tie-breaker conditions and concurrent environments.
This round revolved around designing a tagging system, and an extension was creating a dashboard for top k tags by popularity. I was grilled on API endpoints (http methods used, what and why for params/request body, pagination etc), kafka vs sqs vs rabbitmq, cassandra/dynamodb vs postgres for storing tags data.
Preparation Tips
Amazon LPs are a great resource to prep for the managerial rounds.