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 | Interview Experience (REJECTED) | 4 Months Journey | My Resources
Summary
I went through a 4-month interview journey for an Amazon SDE 2 position, which included an OA, LLD, DSA, and HLD rounds. Despite solving DSA problems with hints and discussing HLD, I was ultimately rejected due to a perceived lack of design depth in LLD and HLD.
Full Experience
Hi Everyone,
I am in my final loop from past 2 months. Here’s my interview experience so far:
A recruiter reached out to me on LinkedIn and asked me to apply for a position he shared. On the same day, he also sent me the OA link via email
OA:
- Sorry, I don’t remember the exact question. But I solved it using pre-computation and hash maps. All test cases passed. (LC Medium)
- It was similar to the standard DP problem Longest Increasing Subsequence, but applying that directly doesn’t give the optimal solution but I was able pass 11/15 test cases. (LC Hard)
I passed the OA and moved to the final loop of 4 rounds
Round 1 (LLD - F2F):
Experience:
The expectation was to write all classes and code with extensibility in mind. It went ok according to me. No negative signs from the interviewer (I later got to know they are trained to remain neutral). Since it was face-to-face, I struggled a bit to represent things clearly on paper.
The interviewer was not very interactive. Just stated the problem and asked if I had any doubts, then told me to write everything and show it to him. I asked a few questions during the process, which he answered. At the end, he took the papers, asked two minor questions about my code (which I answered), and then said he was good with the interview and closed it.
I was expecting to explain my classes and code.
Feedback from HR: NEGATIVE (No idea why)
Round 2 (DSA - F2F):
- https://leetcode.com/problems/max-consecutive-ones-iii/
- https://leetcode.com/problems/maximum-profit-in-job-scheduling/
Experience:
Question 1: I felt I had seen this question in a previous contest and started solving it based on that, but I was going in the wrong direction. The interviewer was very good. She gave me a hint to "think in a window way." That helped, and I solved it easily. Half the time went here.
Question 2: Only 10–15 mins were left. This is LC Hard. I had solved it just 10 days earlier. That helped me write the solution quickly. It’s a DP + Binary Search problem. Just DP gives TLE. BS is needed to optimize it. In the interview, I wrote the DP solution but didn’t have time to recall and explain the BS optimization. But the interviewer was okay with that.
Feedback from HR: Just POSITIVE
(Reasonable. I solved Q1 with a hint, and Q2 missed BS optimization but given the time, I think that’s acceptable.)
They proceed to the HLD round only based on feedback from Round 1 and Round 2.
Due to the negative feedback in LLD, I thought I was out. But they still scheduled HLD for me. Initially, I thought it might be just a formality. But a few candidates I met during F2F were rejected after 2 rounds due to both being negative. So I kept some hope and continued preparing for HLD.
Round 3 (HLD - Virtual):
Design: URL Shortener
Experience:
I was confident about this round since I had ample time to prepare. Did mock interviews with friends and covered most commonly asked HLD problems. But I was asked a relatively simple one. I fumbled a bit but overall feel it went well. The interviewer seemed okay with my design.
Feedback from HR:
Before the round, HR mentioned that only if the HLD round goes well then only I will move to the final round.
I called HR after the interview, he told me that feedback will take time. Later, I learned from a friend that all rounds will be evaluated during a debrief, and then the final decision will be made to proceed the application or not.
LPs (Leadership Principles):
In all 3 rounds, two LP questions were asked (for around 15 mins).
I didn’t mention this above, but DON’T IGNORE LPs — they carry more weight than you might expect.
You can ask your HR for the specific LPs expected in each round and prepare accordingly.
And you can find questions online from respective LP. Prepare your stories before the interview.
Conclusion:
I will wait for my next update to know if there is a bar raiser for me or not. I will keep my hope, but I feel the chances are 50-50. Also, please let me know below in the comments what you think.
This Amazon journey has been going on for the past 4 months for me, where I am learning and giving interviews. Not sure about the result, but what I can say is this learning journey will help me a lot. Even if I don’t pass this Amazon interview, it will still be useful for other company interviews. If anyone is starting his/her grind for top tech companies, all the best to you! You can check out my preparation resources below, they may help you. Keep grinding. Thank you for reading this far!
UPDATE:
- REJECTED! I talked to HR. He mentioned I lacked design depth in LLD and HLD, which is required for SDE 2. As I mentioned above, no idea what happened with my LLD interview. Maybe I was not able to represent things correctly on paper. At least the interviewer should have asked some questions about my classes/code to see if I was writing them correctly or not.
Now, coming to HLD which was a very easy one. I don’t know what made it an unacceptable design. I think my mistake was not defending my statements at 2-3 places.
6-character alias generation with alphabets and numbers gives 62^6 combinations, which goes into billions, whereas the interviewer thought it was in lakhs. 100^6 is 10^12. Since he told me it is less, I thought it was 10^7 (my bad) and then I suggested a hashing solution, which was accepted by him.
It’s OK. A 4-month journey came to an end — on to the next one.
Interview Questions (3)
The problem is Max Consecutive Ones III, linked here. The candidate initially struggled but solved it with a hint to 'think in a window way.'
The problem is Maximum Profit in Job Scheduling, linked here. This is an LC Hard problem, solvable with DP + Binary Search. Just DP gives TLE.
Design a URL Shortener system. The discussion included alias generation, where a 6-character alias using alphabets and numbers gives 62^6 combinations (billions), which was initially misunderstood by the interviewer and candidate to be a smaller scale. A hashing solution was suggested and accepted.
Preparation Tips
My Preparation Resources and Suggestions:
DSA:
- I took premium last year in December. I started my preparation with the topics I hadn’t done before. Learned and solved problems in LeetCode Cards. This helped me a lot, and I feel this is a very underrated learning resource. If you feel stuck, check out YouTube videos for the problem/concept you are looking for.
- Amazon-tagged questions helped me a lot for the interviews, and also previously asked questions from LeetCode Discuss.
- I suggest you take premium only if you can afford it. But it is worth taking for solving company-wise questions, practice assessments, and a few premium cards like DP, Graphs, and Heap.
- Writing contests helped me understand the gaps I had. I suggest you give them and ignore the cheating going on.
- Try to cover each and every important topic (Sliding Window, Binary Search, DP, Graphs, Trees) and solve problems in them until you feel confident. Among DSA, LLD and HLD, your 70% of time and focus should be on DSA as it has number of vast topics and problems to cover. If you worked on good projects as part of your work, you can cover LLD and HLD quickly in 4-6 weeks.
LLD:
- Shreyas Jain’s LLD playlist (you can find them on his YouTube, but if your organization provides free Udemy access, you can check out his same course there).
- For people like me who do it in TypeScript: start with understanding the under-the-hood concept of JavaScript’s OOP nature. Chai aur JavaScript playlist (just watch 6 [42-47] videos). Then you can go for Shreyas Jain’s LLD playlist (understand the concepts here and don’t focus on language style).
https://cloudaffle.com/series/category/typescript-design-patterns — This also helped me understand examples in each design pattern. - Learn from ChatGPT. Always think of AI as your intelligent friend and ask any doubts you have. You will learn so much from it.
HLD:
- First understand fundamental concepts from anywhere that you need to learn for the interviews. I watched this Udemy Course. It was helpful for me. I definitely recommend it if it’s free for you.
- Watch HelloInterview system design walkthroughs in their youtube channel. You’ll get a clear idea of what you need to do in an interview. Check out their other videos on technologies (like Redis, Kafka, etc.). These are commonly used in multiple designs and will give you more confidence if you understand them.
- Books – Alex Xu (Volume 1 & Volume 2). This is a very famous resource you’ll find everywhere. My honest opinion is that Volume 2 is not necessary. Volume 1 should be enough.
- Do mocks with your friends before the interview. It much better to practice implementing rather than just watching videos.