Swiggy Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Swiggy.
Swiggy
Android Engineer
Intern Difficult Positive experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Coding Coding Technical
It was a really smooth process. I got through the DSA and Machine Coding rounds but unfortunately didn't make it past the Android Fundamentals round. They have a prompt process where you get reminders for interviews and they confirm a slot with you.
Confirmed questions1 question
- What are configuration changes in the Android Ecosystem?
Swiggy
Android Developer
Entry Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Take home
Interview formats
Coding Technical
The recruiter reached out, and I submitted my resume. After about a week to 10 days, I heard back that my resume was shortlisted, and an interview was set up right away. The first round was a machine coding task where I had to integrate a REST API using Retrofit, and optionally, I could implement dependency injection and focus on UI performance. The interviewer gave some hints when I got stuck. At the end, they asked about Android UI components and Kotlin. Even though the interviewer seemed positive, I haven't heard back, and the application tracking system shows no updates.
Confirmed questions7 questions
- Can you implement REST API integration using Retrofit?
- Optionally, can you implement dependency injection?
- Can you improve UI performance?
Swiggy
Senior Android Developer
Senior Easy Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical
It was a coding round where I had to build an app that fetches data from an API and displays it in a list, using MVVM, DI, etc. It was pretty straightforward and easy. The only issue was that the interviewer seemed uninterested and was distracted. He'd take a long time to respond when I asked questions and was asking subjective questions about my approach but expecting objective answers. He also lacked basic Android knowledge and kept changing the problem statement. It was a horrible experience, and I was happy to get the generic rejection.
Confirmed questions1 question
- Implement an app to fetch and display movie data from an API in a list, adhering to clean architecture, MVVM, DI, and including unit tests.
Swiggy Android Engineer Interview Questions
Quoted word for word from Swiggy interview reports.
“Build a movie listing website with two screens, following the given documentation.”
Read reports →“Implement an app to fetch and display movie data from an API in a list, adhering to clean architecture, MVVM, DI, and including unit tests.”
Read reports →“What are configuration changes in the Android Ecosystem?”
Read reports →“Can you implement REST API integration using Retrofit?”
Read reports →“What are OOPS concepts?”
Read report →“Can you build a Jetpack Compose app that makes network calls within one hour?”
Read report →“Can you improve UI performance?”
Read report →“How do you do memory profiling?”
Read report →“Tell me about Android UI components.”
Read report →Formats, difficulty and experience
Across all 11 Swiggy interview reports.