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 - 1 Interview Experience | Selected
Summary
I applied for an SDE-1 role at Amazon, cleared the online assessment, and successfully navigated three rounds of interviews focusing on coding, system design concepts, and Leadership Principles. I received positive feedback and an offer.
Full Experience
About Me: Batch: 2024 CSE, Tier-3 YOE: 10 months in a product-based company
I recently had the opportunity to interview with Amazon, and here's a detailed account of my experience:
31st Jan 2025 – Applied for the job.
7th Feb 2025 – Received the OA (Online Assessment) link.
11th Feb 2025 – Attempted the OA. I don't remember the questions exactly, but they were of easy to medium difficulty.
There was no communication after the OA for about a month. Then on 13th March, I received an email from the recruiter regarding upcoming interviews scheduled for 19th March.
19th March – 1st Round: This round went quite well. The interviewer started with a few Leadership Principles (LP) questions and then moved on to a coding problem: Question: Trapping Rain Water
I explained my approach clearly and coded the solution within 10 minutes. After that, the interviewer asked if I had any questions, and I asked a couple. The interview lasted around 50 minutes.
About 1.5 hours later, I received a call from the recruiter informing me that my 2nd interview was being scheduled within the next 3 hours. I agreed, but later I got another call saying the panel had requested to reschedule the interview for the next day.
20th March – 2nd Round: The interview began with a quick self-introduction, followed by two coding problems:
Minimum Number of Platforms
A simple DFS-based graph traversal question, where I was later asked to design a class for the graph, implement relevant methods, and turn it into a complete solution.
This round lasted around 1.5 hours and ended with 2 LP questions. Initially, I got the first question wrong, but when the interviewer gave me another test case, I realized the mistake and corrected it. I was able to solve the second question, but the interviewer pointed out minor things—like using “Package” instead of “Packages” as a variable name—which made me feel like I may have messed up the round.
Surprisingly, after about 2 hours, I received an email from the loop scheduler for the 3rd round, scheduled for 24th March. This time, however, I did not receive a call from the recruiter regarding the update.
3rd April – 3rd Round: After the 3rd interview got rescheduled twice, I finally had it on 3rd April. This round did not include any coding questions; it was entirely based on Leadership Principles, with an in-depth discussion around the work I’ve been doing in my current role.
I believe I performed really well in this round. The interviewer seemed satisfied with my responses and even mentioned that the recruiter would follow up with the next steps.
After waiting for almost 2 weeks, I finally got a call from the recruiter today, informing me that I received positive feedback and they are moving ahead with making an offer!
God is great!!! Jai Shree Ram!!!
Interview Questions (3)
The interviewer started with a few Leadership Principles (LP) questions and then moved on to a coding problem: Question: Trapping Rain Water. I explained my approach clearly and coded the solution within 10 minutes.
The interview began with a quick self-introduction, followed by two coding problems: Minimum Number of Platforms.
A simple DFS-based graph traversal question, where I was later asked to design a class for the graph, implement relevant methods, and turn it into a complete solution.