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
Amazon | SDE 2 | Bangalore
Summary
I interviewed for an SDE 2 role at Amazon in Bangalore, going through an OA, multiple DSA, LLD, HLD, and LP rounds over five stages. Despite a poor initial LLD round, I performed strongly in other rounds and ultimately secured an offer after a follow-up LLD round.
Full Experience
Recruiter reached out on LinkedIn. This was my first time interviewing with Amazon.
The initial screen was an HackerRank OA, don't remember the exact questions. There were two questions in 90 mins and then there were general Software Engineering questions. I was able to solve both the questions and moved on to onsite
Round 1 Two DSA questions were asked.
Two LP questions. Don't remeber the exact questions but I had good stories prepared for all the varieties of LPs, was able to answer them satisfactorily
Recruiter reached out and informed this round was a
Round 2 This was a LLD round. The round started with two standard LP questions
- Tell me about a time when you improved upon a process and how it impacted a customer
- Tell me about a time when you had to do an in depth analysis of a system/project
LPs went well
The LLD question was to design a ATM system.
I was not able to do this properly or at least how the interviewer wanted it. The expectation was to list down the requirements, list down core entities with attributes and behaviour and then write code for one or two features. Proper data type for attributes is important
I fumbled the requirements and the core entities so could not perform in this round properly.
Feedback for this round was poor
Round 3 This was an HLD round The round started with two LPs. Do not remember the exact questions.
HLD question was design a chat application.
The expectation was to list down requirements (functional and non functional), core entities , simple API endpoint definitons and then the design. I tackled the functional parts and then one by one addressed the scaling issues and non functional parts.
The feedback for this round was strong
Round 4 - Bar Raiser This round had two DSA questions
- Print level order traversal of a binary tree
- Print zig zag order traversal of binary
The interview happened on a Saturday, maybe they wanted to take it easy.
- Tell me about a time when you saw a process/system not living upto the standards and what did you do
- Tell me about a time when you had a disagreement with a senior and how did you handle it
This round went well, feedback was strong hire
After the hiring committee discussion the recruiter reached out to inform me that since all the rounds were strong hire except LLD , so they wanted to move forward with one more LLD round.
Round 5 First 30 minutes went into LP discussion. I do not rememeber the questions. The interviewer pretty much bombarded with multiple LPs. I was able to answer them satisfactorily.
LLD - design an issue management system
Pretty much followed the pattern used for HLD -> list down requirements , core entities with attributes and behaviour and then code Design pattern used is state pattern , strategy pattern and factory pattern.
Recruiter reached out in 15 minutes to inform it was a strong hire and they are moving onto the offer stage.
Waiting for the offer.
My advice would be really focus on the LPs and keep 10-15 stories prepared. Usually folks tend to miss out on the LP. Amazon places a big emphasis on the LPs
EDIT: Offer : https://leetcode.com/discuss/post/6829780/amazon-sde-2-bangalore-offer-by-anonymou-k3d1/
Interview Questions (11)
You are given a network of n nodes, labeled from 1 to n. You are also given times, a list of travel times as directed edges (u, v, w), where u is the source node, v is the target node, and w is the time it takes for a signal to travel from u to v. We will send a signal from a given node k. Return the minimum time it takes for all the n nodes to receive the signal. If it is impossible for all the n nodes to receive the signal, return -1.
Tell me about a time when you improved upon a process and how it impacted a customer.
Tell me about a time when you had to do an in depth analysis of a system/project.
Design an ATM system. The expectation was to list down the requirements, list down core entities with attributes and behaviour and then write code for one or two features. Proper data type for attributes is important.
Design a chat application. The expectation was to list down requirements (functional and non functional), core entities, simple API endpoint definitons and then the design.
Print the level order traversal of a binary tree. This typically involves using a queue to visit nodes level by level.
Print the zig-zag level order traversal of a binary tree. This involves traversing levels alternating between left-to-right and right-to-left.
Tell me about a time when you saw a process/system not living up to the standards and what did you do about it.
Tell me about a time when you had a disagreement with a senior and how did you handle it.
Design an issue management system. The expected pattern was to list down requirements, core entities with attributes and behaviour and then code.
Preparation Tips
My advice would be to really focus on the LPs and keep 10-15 stories prepared. Usually, folks tend to miss out on the LP. Amazon places a big emphasis on the LPs.