My first experience with Swiggy was bad, and I had given negative feedback on Glassdoor. Later, the HR approached me and invited me for another round of interviews.
I appreciate their gesture in addressing the concern. The effort to trace back an anonymous review is commendable.
The first round was around 2.5 hours with the CTO. He presented a real-life problem that Swiggy faced, and we worked on a solution. This was followed by a design discussion, during which there was healthy debate.
The second round was for an hour with the Director of Engineering. We discussed my passion, my work experience, and why I was interested in Swiggy. The discussion was again healthy.
The third round was machine coding. It was a relatively simpler problem compared to the first round, but the approach, extensibility, and test cases mattered.
Implement a Cache that works on Least Recently Used (LRU) and Last-In, First-Out (LIFO) principles.
The design should be extendible to support more logic, such as the most frequently used element.
The following metrics were computed from 2 interview experiences for the Swiggy Software Development Engineer III role in Bengaluru, Karnataka.
Swiggy's interview process for their Software Development Engineer III roles in Bengaluru, Karnataka is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Swiggy's Software Development Engineer III interview process in Bengaluru, Karnataka.