My SDE Android Internship Interview Experience at Groww (2025)
Summary
I interviewed for an SDE Android Intern role at Groww, which involved a coding assignment followed by a technical interview focusing on Android architecture, Kotlin, data handling, and a RecyclerView scenario. Despite not being selected, I found it a valuable learning experience.
Full Experience
I recently got the opportunity to interview for the SDE Android Intern role at Groww.
I had applied through a Google Form on 13th May 2025, and on 25th June 2025, I received an assignment to build a stock display app using Kotlin (everyone who applied received the same assignment). I submitted it on 4th July 2025, and got an interview call from HR on 22nd July 2025.
During the interview, most of the discussion revolved around the assignment. I began by explaining the app, its architecture, and why I chose the MVVM pattern with Repository. I was asked: • What is MVVM architecture? • What happens when the user rotates the screen? • What are lambda functions and their use cases? • How did I implement the bottom navigation bar? • What is dependency injection? • How does my ViewModel help retain data across screen rotations? • What is the Activity lifecycle?
I was also given a scenario: If a screen shows a RecyclerView with payment options like PhonePe and Cash on Delivery, how would I ensure that only one card is selected at a time? I had to explain how I would manage selection and persist the user’s choice.
There were also several questions around data handling. I explained that I implemented caching — if data is in the cache, I use it; otherwise, I make an API call. I was asked where I handled the logic to validate the cache and how I structured my API calls.
The interviewer also asked me about the numbers mentioned in my resume — how I calculated them and what they represented.
There were some Kotlin-specific questions too: • What is a data class? • Can a data class be empty? • How is it different from a regular class?
In terms of feedback, I was told that I could have gone deeper into how things actually work under the hood, which is something I’ll definitely work on moving forward.
Although I wasn’t selected (HR informed me the next day), it was a valuable learning experience.
I’m sharing this because while preparing for my interview, I struggled to find real Android interview experiences online. Hopefully, this helps someone else who’s preparing for theirs.
Interview Questions (13)
What is MVVM architecture?
What is MVVM architecture?
Android Screen Rotation Effects
What happens when the user rotates the screen?
Lambda Functions and Use Cases (Kotlin)
What are lambda functions and their use cases?
Bottom Navigation Bar Implementation
How did I implement the bottom navigation bar?
What is Dependency Injection?
What is dependency injection?
ViewModel and Data Retention on Screen Rotation
How does my ViewModel help retain data across screen rotations?
Android Activity Lifecycle
What is the Activity lifecycle?
RecyclerView Single Selection and Persistence
If a screen shows a RecyclerView with payment options like PhonePe and Cash on Delivery, how would I ensure that only one card is selected at a time? I had to explain how I would manage selection and persist the user’s choice.
Cache Validation and API Call Structure
I explained that I implemented caching — if data is in the cache, I use it; otherwise, I make an API call. I was asked where I handled the logic to validate the cache and how I structured my API calls.
Explaining Resume Metrics
The interviewer also asked me about the numbers mentioned in my resume — how I calculated them and what they represented.
What is a Kotlin Data Class?
What is a data class?
Can a Kotlin Data Class be Empty?
Can a data class be empty?
Data Class vs. Regular Class in Kotlin
How is it different from a regular class?