Synthesized from 67 candidate submissions for ALL.
Swiggy maintains a structured interview process that varies significantly by department, utilizing technical problem-solving for engineering roles and situational business case studies for operations and analyst positions. Candidates are generally evaluated on their ability to bridge fundamental theoretical knowledge with practical, real-world application relevant to the company's delivery ecosystem.
The interview process was smooth and well-structured, consisting of five rounds covering coding, design, and behavioral aspects. The candidate successfully received an offer.
Conducted on Hackerrank for 1.5 hours, consisting of 3 questions: one sorting variation, one union-find variation, and one job scheduling variation.
Online assessment consisting of three coding problems of varying difficulty levels.
Best time to buy stock variation
Union find variation
Maximum profit in job scheduling variation
Machine coding round focused on designing and implementing a Splitwise application with emphasis on Object-Oriented Design principles.
Design a Splitwise application
Problem solving and data structures round involving two algorithmic problems.
Maximum gain in a circular array game
Palindrome pairs
Low-level design round focusing on API design and filtering logic for the Swiggy application.
Design APIs and LLD for application filters
Hiring manager round covering team responsibilities, a chess game design task, and behavioral questions.
Design a chess game
The candidate participated in two rounds for the Associate Software Developer Engineer (Android) role at Swiggy. They completed the mandatory tasks in the machine round but missed some edge cases. In the second round, they answered Android and Kotlin-related questions but skipped DSA due to lack of confidence. The candidate received a rejection email after these rounds.
The candidate was given a live assignment to implement an API to fetch data and run an APK. The task included mandatory and optional parts (e.g., using DI, implementing Paging) within a limited time. The candidate completed the mandatory tasks but missed some edge cases. The interviewer provided hints and shared insights about Swiggy's workflow from requirement to production.
This round combined Android and DSA questions. The interviewer asked questions on Android, Kotlin, Architecture, syntax, output guessing, and OOPs. The candidate answered many questions, some partially correct. The interviewer then asked about the candidate's projects, work experience, and challenging tasks in Android. The candidate requested to skip DSA due to lack of confidence.
Interview Digest