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 | Software Engineer P40 | Aug 2025 [Hold]
Summary
I applied for a P40 Software Engineer role at Atlassian. After completing six rounds, including Karat, DSA, Code Design, System Design, Management, and Values, my application was put on hold due to filled openings, despite receiving high confidence feedback in most technical rounds.
Full Experience
Status: B.Tech (Tier-3) Position: SDE-2 in FAANG+ Experience: 4 years
APPLICATION
Applied on careers portal for P40 role without any referral. Recruiter reached out in few days to discuss preliminary details like compensation expectation, reason to switch, etc.
ROUND-1 Karat
This was a screening round by 3rd party which involved 5 rapid fire system design questions and 2 easy-medium DSA questions.
Feedback: Cleared
ROUND-2 DSA
Write following methods - increasePopularity(content id), decreasePopularity(content id), getMostPopular(). Follow-ups included increasing/decreasing popularity by 'x' not by 1 and tie-breaker strategies.
Feedback: High Confidence, P40
ROUND-3 Code Design
Write following methods - addAgentRating(agent id), getSortedAgentRatingsList(). Follow-ups included adding agent rating for a given month, getting sorted agent list for a month, tie-breaker strategies, and concurrency.
Feedback: High Confidence, P40
ROUND-4 System Design
Design popular K feeds in confluence. Follow-ups included popularity score calculation strategies, support for querying in windows and updating dashboards of users in real-time.
Feedback: High Confidence, P50
ROUND-5 Management
Situation based questions like when you owned a project end-to-end, when you improved efficiency, when project scope increased, when you pushed back someone, etc.
Feedback: High Confidence, P40
ROUND-6 Values
Situation based questions like when you mentored someone, conflict with someone, shipped any bug to customer, project deprioritized, etc.
Feedback: No Hire
Conclusion
Recruiter reached out after Round-4 that openings are already filled but you can still give remaining two rounds and we will consider your application in 2-3 weeks when new positions come.
After all the rounds finished, recruiter provided feedback. I told the recruiter that my values round went even better than management round; their interviewer had 10 years of experience, still sitting on P40 role and joined Atlassian less than a year ago which is a big question on the credibility of their feedback. The feedback isn't even consistent with rest of the rounds. The interviewer asked me to answer either question A or question B and in the feedback I could see the negative points were that question B's response were missing and question A's response was good - I was given an OR condition and evaulation was for AND.
This can very well be a tactic to reject applications since positions were already filled.
Interview Questions (5)
Design a system with the following methods: increasePopularity(content id), decreasePopularity(content id), and getMostPopular(). Follow-up considerations include supporting increases/decreases by an arbitrary value 'x' (not just 1) and strategies for handling tie-breakers when multiple items have the same popularity.
Design a system that includes the methods addAgentRating(agent id) to add a rating for a specific agent and getSortedAgentRatingsList() to retrieve a list of agents sorted by their ratings. Follow-up requirements include supporting agent ratings for a given month, retrieving a sorted agent list for a specific month, implementing tie-breaker strategies, and addressing concurrency issues.
Design a system for displaying 'popular K feeds' within Confluence. Considerations include strategies for calculating popularity scores, supporting queries for feeds within specific time windows, and updating user dashboards in real-time.
Situation-based questions focusing on experiences such as owning a project end-to-end, improving efficiency, managing increased project scope, and pushing back when necessary.
Situation-based questions covering topics like mentoring someone, resolving conflicts, shipping a bug to a customer, and handling project deprioritization.