I recently had my interview experience for the SDE-1 role at Swiggy, which consisted of two rounds.

1st Round – DSA (60 mins)

My first round was a 60-minute Data Structures & Algorithms session. I was presented with two problems. The first one was Codeforces 1133C, which I initially approached with a brute-force O(n²) solution and then managed to optimize to O(n log n) within 25 minutes. For the second question, 'Partition Array Into Two Arrays to Minimize Sum Difference' from LeetCode, I thoroughly explained my DP-based logic and proceeded to complete the full code in the remaining 30 minutes. This round concluded positively, and I was advanced to the next stage.

2nd Round – LLD (Design + Implementation) (60 min)

The second round was a 60-minute Low-Level Design session, which involved both design and implementation. It began with a brief 5-minute self-introduction. The interviewer then tasked me with designing and implementing a Splitwise application. I dedicated about 10 minutes to discussing the functional requirements and identifying the key objects necessary for the design. The interviewer was very keen on seeing the actual coding. I started sketching a UML diagram, but the sheer volume of requirements combined with the limited time began to make me panic. Despite this, I managed to start coding in VS Code and implemented partial functionality. However, it became clear that the interviewer expected a fully working application within the allotted time, which I couldn't deliver. Consequently, I was rejected after this round.

In my opinion, the LLD round was genuinely overwhelming, and expecting a fully functional Splitwise application complete with a UML diagram in just 45 minutes felt quite unrealistic.

My interview process for the SDE-2 role at Swiggy was quite structured. It began with an Online Assessment (OA) where I tackled two medium-level coding questions focusing on Arrays, HashMap, and Sliding Window topics, both of which I solved within the time limit.

The second round was another Coding Round, where I faced two DSA questions. One was a medium-level coding question on finding the longest subsequence from a string, and the other was a hard-level graph problem involving finding the shortest path with 'k' hops. I implemented both solutions efficiently and made sure to discuss edge cases and possible optimizations.

Next up was the Low-Level Design (LLD) round. I was given the task to design a Cab Booking System. During this round, I covered all essential aspects: defining entities like Rider, Driver, Trip, and Cab; outlining core functionalities suchas booking, allocation, and ride status. I presented a class diagram, the overall system flow, and API designs. We also delved into scalability considerations and various edge cases.

The final round was with the Hiring Manager, which was a blend of system design and techno-managerial discussions. We discussed my previous projects in depth, covering design patterns I had used. The conversation also touched upon technologies like Kafka, Redis optimizations, and database internals. My thought process around scaling systems and handling bottlenecks was also evaluated.

Ultimately, the verdict was not selected. The feedback indicated that my performance was good across all rounds. The final rejection reason given was my decision to switch companies within 3 months of joining my then-current company. Overall, it was a good learning experience, and I found Swiggy’s interview process to be well-structured and balanced across DSA, LLD, and system knowledge.

I recently appeared for the Swiggy SDE-2 interview, specifically for Round 1. I was presented with two coding questions, for which I had 25 minutes each. I was able to successfully solve both problems and felt it was a good experience overall. Based on my performance, I have been selected to proceed to Round 2, which will focus on Low-Level Design (LLD).

I applied for the SDE Intern position at Swiggy by filling out a Google form circulated on LinkedIn by Swiggy employees, and I also shared my resume with some of them. Shortly after applying, I received an email from HR inviting me to an Online Assessment (OA) scheduled for the same day. The OA, conducted on Hackerrank, consisted of medium-difficulty questions primarily focused on greedy algorithms and dynamic programming. My friends, who also took the OA, encountered standard medium-level graph problems.

After successfully clearing the OA, I was contacted by HR for the first interview round. This round was with an SDE-1 and was structured into three parts: an introduction and a discussion about my projects and previous experiences, core subject questions on MongoDB, a comparison between MongoDB and SQL, and ACID properties, followed by two DSA questions on Greedy algorithms and Tries, along with a time and space complexity follow-up question. A key takeaway from this round was the importance of thoroughly understanding every data structure and its time/space complexity.

About 30 minutes after the first round, I received another call from HR confirming I had cleared it and would proceed to the second interview with the Hiring Manager. This round extensively covered my internship tasks, projects, and the APIs I had developed. It also included one DSA question based on BFS and Heaps, which was of medium to hard difficulty, and concluded with some situational-based questions. Soon after this interview, I received the offer for the SDE Intern role at Swiggy! This internship proved to be one of my best experiences, working for a top unicorn startup. After dedicating three months to working with Golang, Spring Boot, and Reactjs, I was delighted to receive a full-time offer from Swiggy.

I am a 2024 passout from a Tier-2 college and currently work as a Software Engineer at a consultancy. In December 2024, I applied for an ASDE role at Swiggy.

My interview journey began with a Hackerrank assessment. This included two very simple DSA questions, two easy-to-medium SQL queries involving simple joins, and a few easy Computer Science fundamentals MCQs.

After the initial assessment, I filled out a Google form to apply and kept an eye on LinkedIn for updates. I then received a technical assignment. Since this was a backend-heavy role, the task was to build a simple attack/defend game. I had the flexibility to choose between Node, Java, or Golang for the implementation.

The next stage was my 1st Face-to-Face interview, which was an LLD Round. This round was conducted by a third party and felt more like a discussion than a strict interview. The interviewer was primarily interested in how I think, rather than just my coding ability. My task was to design a follow/unfollow functionality for a social media application. The focus was on requirement gathering, designing the database schema, identifying the necessary API endpoints, and determining their types (GET/POST/PUT/PATCH/DELETE). I was encouraged to think aloud and interact with the interviewer, without worrying too much about the actual code.

Finally, I had the HM Round (Hiring Manager). This round started with a resume screening. Following that, I was asked questions covering Computer Science fundamentals, including OS, CN, and DBMS. There was also one DSA question, which for me was Merge Intervals. The other questions asked were:

• Difference between Process and Thread? Why are they different? / Why do we require these differently?
• What is indexing? Why/Where is it used? How is it implemented? (I couldn't answer this one)
• Difference between TCP and UDP? Use cases?
• Difference between TCP and HTTP? Difference between HTTP and REST? What is REST?

Overall, things went well, and I was pleased to receive an offer from Swiggy.

Hi everyone,

I wanted to share my recent experience with the Swiggy ASDE role Hackerrank test. After being shortlisted through my resume, I received the test link and completed the assessment. Here's how the test was structured:

Test Structure:

• Total Questions: 13
• Adhoc: 1 question
• Problem Solving: 1 question
• HTML/CSS/JS: 10 multiple-choice questions
• React Coding: 1 question (using TypeScript)

Detailed Experience:

The Adhoc Question was straightforward, seemingly designed to assess basic logical and analytical skills. Following that, the Problem Solving Question involved a simple array manipulation problem, which I found quite basic and a relief to solve, restricted to JavaScript for coding.

The HTML/CSS/JS MCQs consisted of 10 multiple-choice questions, predominantly covering fundamental concepts and common scenarios in these technologies. These were generally easy.

The most engaging part was the React Coding Question. The task required me to complete several features for a movie website. Specifically, I had to implement a search functionality and a favorites table for movies that were fetched from an API. This challenge truly tested my understanding of React and TypeScript.

Verdict:

I am pleased to report that I cleared this round!

Overall, I found the test to be well-balanced and fair. The problem-solving and React coding questions were particularly enjoyable. For anyone preparing for a similar test, I'd strongly recommend brushing up on JavaScript basics, React fundamentals, and ensuring comfort with TypeScript.

My interview process for the SDE 1 role at Swiggy was structured into three distinct phases:

1. Online Coding Test: This round consisted of three coding challenges: one easy, one medium, and one medium-hard problem. I performed well and received a positive response, advancing to the next stage.
2. PSDS Round (Technical Discussion): This was a technical problem-solving and data structures round. I was given a problem involving currency conversion rates, which I solved using Golang. The problem required finding the conversion rate between two given currencies based on an array of direct conversion rates.
3. HM-Round: The final round was with the Hiring Manager, focusing on System Design. We discussed Low-Level Design (LLD) principles, resilient system patterns, and concurrency concepts.

All three rounds were positive, and I successfully received an offer for the SDE 1 position.

I applied for an Associate Software Development Engineer (ASDE) role at Swiggy through a referral in late November. It took approximately three weeks to receive an email asking me to fill out a form with basic details like my resume, college, and CPI. Around two weeks later, on December 19th, I got another email stating my resume was selected, and I subsequently received a link for a Hackerrank test.

The Hackerrank test included:

• One database SQL query question, focusing on joins.
• One medium-to-hard coding question, which I recall being based on arrays and binary search.
• A few basic MCQs.

I managed to solve all these within 30-40 minutes.

A week after the online test, I received an email for Round 1, which was an assignment based on low-level design. The task was to design a playing arena where two players could fight according to a specified logic. I was restricted to using Java, NodeJS, or Go for the project. I completed the assignment using Java + Maven within a day and was quite pleased with the code I produced.

However, after submitting the assignment, I waited almost two weeks without further communication. I was really hoping for this opportunity. I subsequently received a call from HR. To my surprise, the role wasn't full-time as expected but a 3-month internship with a potential conversion to a full-time position. This was nowhere mentioned in the original job description, which I found to be a waste of candidates' time. HR confirmed my last round went well and asked if I wanted to proceed, mentioning an offer of 8 CTC for the internship (I assumed this meant 8 LPA, so 2 LPA for 3 months).

Application Process

I applied for the Swiggy SDE1 - Backend position in Bangalore through a referral. My professional background included over a year of experience as an SDE1 at a product-based company. The entire interview process took place virtually in September 2021.

Round 1: Online Assessment (1.5 hours)

This round was conducted on HackerRank. I successfully solved all three questions presented:

1. A problem focused on determining the number of distinct subarrays that could be formed with at most a given number of odd elements.
2. A question involving a number line from 0 to 'n' and a string of moves, where I needed to find the number of subsequences of moves that would lead from a given point 'x' to 'y'.
3. A problem asking to select weights from a given list such that their sum did not exceed a specified capacity.

Two days after the online assessment, I received a call to proceed to the interview rounds.

Subsequent Rounds (Conducted on the same day)

Round 2: Machine Coding Round (3 hours)

The primary task was to design and code a multilevel parking lot system. Although I couldn't complete all the given requirements within the two-hour timeframe, the interviewer paid close attention to my design approach. We had a detailed discussion about my design choices and how I would implement the remaining features. Additionally, I was asked to code the Singleton design pattern, which led to a thorough discussion where I successfully answered all related questions.

Round 3: Data Structures and Algorithms (1 hour)

This round began with a brief discussion about the previous machine coding round. Following that, I was given a problem similar to LeetCode's Rotting Oranges. We explored numerous follow-up questions based on this problem.

Round 4: Hiring Manager Round (1 hour)

In this final round, we discussed a Data Structures & Algorithms question related to a parking lot system, though the specifics were not elaborated. The hiring manager also inquired about my current work responsibilities and asked me to explain one of my projects in detail.

I received the interview results approximately 4-5 days after the final round. I found the interviewers and HR team to be very friendly, and the overall interview process was remarkably smooth.