The process started with a recruiter calling and scheduling two technical rounds. I was hesitant to proceed with the interview the moment I saw previous Glassdoor reviews for the role. It turns out my fears were right; Swiggy's process is not meant for smart engineers who value their time.
Round 1: One problem-solving/data structure question and Android basics.
Round 2: One and a half hours to code a movie listing application from scratch. They do not mention this beforehand, and around 40 minutes get wasted in setting up Gradle, downloading, and setting up boilerplate code for basic dependencies like Retrofit, Picasso, and Dagger.
The biggest flaw with Swiggy is that their Android machine coding round is not aimed at measuring competency. It's rather a speed test—typing and internet speed. The task is also not doable if someone follows clean architecture, dependency injection, and unit testing. What more can be expected in 1.5 hours, especially when you do not provide a basic skeleton to save time and to check actual competencies during the interview?
Anyone planning to attend an interview at Swiggy should look at other options before putting yourself through this unpleasant ordeal.
PS/DS problem: Find the count of the longest consecutive integers in an array.
Android app: Fetch and show a list of movies and their details. To be implemented from scratch in just 1.5 hours, including clean coding, Dagger, unit testing, and a good UI.
The following metrics were computed from 1 interview experience for the Swiggy Senior Software Engineer III role in Bengaluru, Karnataka.
Swiggy's interview process for their Senior Software Engineer III roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Swiggy's Senior Software Engineer III interview process in Bengaluru, Karnataka.