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
Microsoft SDE2 (L61) Interview Experience | 4 YoE
Summary
I interviewed for an SDE2 (L61) position at Microsoft, which included rounds on Data Structures & Algorithms and Low-Level Design. I was ultimately rejected after presenting my approaches for the design problems.
Full Experience
R1 (DSA):
Q1. Shortest dis betweeen two nodes.
Q2. Probable celebrity
R2 (LLD):
Q1. Design a Logger System. ==> Type of Msg: INFO, DEBUG, WARNING, ERROR. ==> User should be able to decide which type of msg to be displayed, msg should be either be displayed in a log file or console.
R3 (LLD):
Q1. Design a circular buffer. Implement a Circular buffer, where the size of the buffer is given as input by user, say size of buffer=10.
I write, HE, Then write, LLO, buffer will be HELLO. Post that I read(2), i.e. first two letters, HE will be returned.
Then if I write SAMELEVEL it will override some char from HELLO, but the HELLO isn't even read yet, then it is wrong.
I did added some handling that keep on writing in buffer until we encounter where our read pointer is. If we encounter the read pointer the write operations should fail completely. But then interviewer pointed that you are writing the partial string to the buffer and if exit condition is true you are exiting.
Although I felt interviewer should have probably presented all these scenarios during the question breifing only. But that's what life is.
Result: Rejected
Interview Questions (3)
Probable celebrity
Design a Logger System. Type of Msg: INFO, DEBUG, WARNING, ERROR. User should be able to decide which type of msg to be displayed, msg should be either be displayed in a log file or console.
Implement a Circular buffer, where the size of the buffer is given as input by user, say size of buffer=10. I write, HE, Then write, LLO, buffer will be HELLO. Post that I read(2), i.e. first two letters, HE will be returned. Then if I write SAMELEVEL it will override some char from HELLO, but the HELLO isn't even read yet, then it is wrong. I did added some handling that keep on writing in buffer until we encounter where our read pointer is. If we encounter the read pointer the write operations should fail completely. But then interviewer pointed that you are writing the partial string to the buffer and if exit condition is true you are exiting.