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
Swiggy Interview Experience - Full Stack (SDE-2)
Summary
I interviewed for a Full Stack SDE-2 role at Swiggy. The process included an online coding test, a JavaScript coding round, a System Design discussion, and a Hiring Manager interview, ultimately resulting in a rejection.
Full Experience
I applied for a Full Stack (SDE-2) position at Swiggy after seeing a Google Form shared by a recruiter on LinkedIn. With 2.5 years of experience in a service-based company, I was eager for this opportunity.
My journey began with an Online Test on HackerEarth. The task was to build a CRUD application, with a React frontend and a Node.js backend. I had three hours for this. I managed to get all frontend test cases to pass, but unfortunately, one backend test case failed. Overall, I'd rate the difficulty as medium.
A week later, I received a call from a third-party vendor, informing me that I had cleared the online test and would be proceeding to the first interview round.
Round 1 - (JavaScript, HTML, CSS) was conducted by an interviewer from the same third-party vendor. We started with a discussion about my projects. Following that, I was presented with an easy-to-medium level JavaScript coding problem that required the use of currying. I initially explained an approach, but while coding, I realized it wouldn't work. I quickly corrected myself and provided a working solution using currying. The interviewer was very supportive and even allowed me to debug with the console. The feedback was positive.
The very next day, the recruiter called to inform me that I had cleared the first round and would be moving on to interviews with the Swiggy team.
Round 2 – HLD + LLD started with a problem statement: designing 'Book Search functionality'. I followed a structured approach, beginning with requirements gathering, then moving into High-Level Design (HLD) discussions. We spent most of our time on HLD and didn't get a chance to dive into Low-Level Design (LLD). Towards the end, we discussed the frontend part, where I explained UI implementation, Server-Side Rendering (SSR), and CDN usage.
Again, the next day, the recruiter called to confirm I had cleared the second round and would be proceeding to the final interview with the Hiring Manager.
Round 3 – Hiring Manager was scheduled for an hour, but it started 15 minutes late. The recruiter had mentioned it would be a mix of behavioral and technical questions. It began with a few behavioral questions and some casual talk. Surprisingly, the round ended abruptly after only about 15 minutes. Despite answering all questions, I felt the brevity was unusual.
About two hours later, I received an automated rejection email. I'm unsure if the decision was predetermined given the short HM round, but overall, it was a great learning experience throughout the process.
Interview Questions (3)
The task was to build a CRUD (Create, Read, Update, Delete) application. This involved developing two separate applications: a Frontend using React and a Backend using Node.js. The time allotted for this was 3 hours.
I was presented with an easy-to-medium level JavaScript coding problem. The core of the solution required implementing the concept of currying.
The problem statement required me to design a 'Book Search functionality'. The discussion primarily focused on the High-Level Design (HLD) aspects, including gathering requirements and outlining the overall architecture. We did not delve into the Low-Level Design (LLD).
Preparation Tips
My preparation involved consistent practice of coding problems, which proved crucial for quickly identifying and correcting my approach during the JavaScript round. For the system design, I focused on a structured methodology for tackling HLD problems. I also gained practical experience by building a CRUD application, which was directly relevant to the online test.