Design the app, not the backend
Android architecture rounds ask you to design a feature or library from the device’s side: screen state, layers, caching, offline behaviour and background sync. The Diagram tab draws the components as the question is asked, so you can talk through them in order.
How an Android loop runs
Big tech pairs a design round with DSA and an Android depth round. Indian product companies usually add a timed machine-coding build.
Phone screen
Usually a DSA problem with follow-ups, even for Android roles. Reddit, 2024 (opens in a new tab); Medium, 2025 (opens in a new tab)
With Assisted Voice: Capture the problem for an approach and working code in Kotlin or Java.
DSA rounds
About 60 min each
One or two rounds. PhonePe candidates report two problems in an hour. Medium, 2025 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
With Assisted Voice: Each problem gets an approach and code from one shortcut.
Android domain round
About 60 min
Lifecycle, ViewModel, coroutines and Flow, Compose, services and DI, probed with “how does it work underneath?” LeetCode Discuss, 2025 (opens in a new tab); LinkedIn, 2024 (opens in a new tab); Medium, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
With Assisted Voice: Press the answer shortcut for an explanation of the internals in the first person.
Machine coding or pairing
90 min to 3 hours
Build a working app from an API in MVVM and Clean Architecture. Uber, and one Airbnb candidate, instead paired on a partly built Android Studio project. LinkedIn, 2025 (opens in a new tab); LinkedIn, 2024 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab); Taro, 2025 (opens in a new tab); LinkedIn, 2025 (opens in a new tab)
With Assisted Voice: Capture the brief for a structure and code to build from.
Android system design
45–60 min
Design an app, feature or SDK on a whiteboard. The client is the focus and the API contract is the boundary, though some interviewers still run a generic design round, so ask your recruiter. Meta Careers, 2016 (opens in a new tab); Blind, 2025 (opens in a new tab); Calibrd, 2026 (opens in a new tab); DEV Community, 2025 (opens in a new tab)
With Assisted Voice: The Diagram tab draws the components and data flow.
Hiring manager
A project deep dive. At PhonePe it included an open-ended design, such as a map app or an SDK. interviewexperiences.in, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
With Assisted Voice: Answers draw on your resume, so project details stay consistent.
The layers you’re expected to draw, and what each one draws out
Interviewers expect the shape of Android’s own architecture guide. Each layer comes with a follow-up candidates were asked about it.
UI
Jetpack Compose
Android’s architecture guide calls Compose the recommended UI toolkit.
“XML or Compose, and why? How does navigation work?”
Asked at Google, PhonePe, Tesco. Android Developers, 2026 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab); Medium, 2026 (opens in a new tab)
ViewModel
StateFlow, one uiState
Expose a single UI state as a StateFlow and collect it in a lifecycle-aware way. A ViewModel doesn’t survive process death, so keep small UI state in SavedStateHandle.
“How does a ViewModel survive rotation, and what’s lost when the Activity is recreated?”
Asked at Swiggy, Zomato, PhonePe. Android Developers, 2026 (opens in a new tab); Android Developers (opens in a new tab); LinkedIn, 2025 (opens in a new tab); Medium, 2024 (opens in a new tab); Medium, 2025 (opens in a new tab)
Use cases
Optional domain layer
Recommended for big apps where business logic is reused across ViewModels.
“Where does mapping logic live, and how would you unit-test it?”
Asked at Tesco. Android Developers, 2026 (opens in a new tab); Reddit, 2025 (opens in a new tab); Medium, 2026 (opens in a new tab)
Repository
Single entry to data
UI and ViewModels never touch data sources directly.
“Which source is the source of truth when the network and cache disagree?”
Android Developers, 2026 (opens in a new tab); Android Developers (opens in a new tab); DEV Community, 2025 (opens in a new tab)
Data sources
Room and Retrofit
For offline-first apps, the local database is the source of truth, with at least one local and one network source.
“How do you refresh once a day unless the user pulls to refresh?”
Asked at Swiggy, Tesco. Android Developers (opens in a new tab); Android Developers (opens in a new tab); LinkedIn, 2025 (opens in a new tab); Medium, 2026 (opens in a new tab)
Background sync
WorkManager
Queue offline writes and drain them with WorkManager when the device is back online.
“How does WorkManager guarantee the work runs?”
Asked at Zomato. Android Developers (opens in a new tab); Reddit, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
Across every layer, expect dependency injection with Hilt: it was asked at Google, Zomato and PhonePe, and one interviewer had to prompt a candidate for it, which counted against them. Android Developers, 2026 (opens in a new tab); Reddit, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
What Android candidates report
Raise offline, caching and DI yourself
A rejected candidate whose interviewer had to prompt for DI, offline mode, testing and low network was told by senior engineers to drive those topics unprompted. Meta’s guide also says to drive the discussion.
Meta Careers, 2016 (opens in a new tab); Reddit, 2025 (opens in a new tab)
Internals, not just APIs
Zomato emphasised how components work underneath. PhonePe tested Compose, Hilt and coroutine internals, and a Swiggy interviewer asked why each line of the machine-coding solution was written.
Medium, 2024 (opens in a new tab); Medium, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab)
Battery, network and freshness trade-offs
Meta asks how you balance battery, network and CPU against keeping data fresh. One Airbnb candidate’s coding round required slow-network and error states.
Meta Careers, 2016 (opens in a new tab); Taro, 2025 (opens in a new tab)
DSA still gates the offer
Swiggy and PhonePe candidates say a weak DSA round hurt despite strong Android rounds. A Google L5 Android hire called DSA the only hard part.
Reddit, 2025 (opens in a new tab); LinkedIn, 2025 (opens in a new tab); interviewexperiences.in, 2025 (opens in a new tab)
Formats reported at companies
| Company | Format reported | Hands-on round | Source |
|---|---|---|---|
| GoogleL4–L5 Android, 2025 | Phone screen and DSA rounds, an Android domain round on architecture, coroutines and memory, and Googlyness. L5 adds Android system design. Google’s virtual-interview guide says using AI during an interview means disqualification. | Hands-on round: None reported beyond DSA. | Reddit, 2025 (opens in a new tab); LeetCode Discuss, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab); Google (opens in a new tab) |
| MetaAndroid E4–E6 | A 45-minute design interview, mostly talking and drawing, matched to your Android background. Meta’s hiring FAQ says outside AI tools aren’t allowed; only the tools inside its interview environment may be used. | Hands-on round: Coding rounds are DSA. | Meta Careers, 2016 (opens in a new tab); Calibrd, 2026 (opens in a new tab); Meta Careers (opens in a new tab) |
| UberAndroid L4 and senior, 2024–25 | Phone screen, DSA, an Android depth round, mobile system design and a hiring manager. | Hands-on round: Pair-program a UI from a mockup in Android Studio. | Reddit, 2024 (opens in a new tab); TrueInterview, 2026 (opens in a new tab); LinkedIn, 2025 (opens in a new tab) |
| SwiggyAndroid SDE 2, 2024–25 | Machine coding, an Android and DSA round, system design and a managerial round. | Hands-on round: Two hours to build an API-backed list app with search and sort. | LinkedIn, 2025 (opens in a new tab); Medium, 2024 (opens in a new tab) |
| PhonePeSDE Android, 2025 | DSA (two problems in an hour), an Android platform round, machine coding and a hiring manager. | Hands-on round: 90 minutes for four to five features of an e-commerce app with backend sync. | interviewexperiences.in, 2025 (opens in a new tab); Medium, 2025 (opens in a new tab) |
| FlipkartAndroid SDE 2, single report, 2024 | Phone screen, machine coding, a one-hour DSA round, Android core concepts, system design and a hiring manager. | Hands-on round: Three hours, any stack, including Kotlin and Compose. | LinkedIn, 2024 (opens in a new tab) |
Prompts candidates were actually given
- An image loading and caching library like GlideUnnamed FAANG companiesCalibrd, 2026 (opens in a new tab); DEV Community, 2025 (opens in a new tab)
- A one-to-one chat app that also sends imagesMeta and Uber, in aggregated reportsCalibrd, 2026 (opens in a new tab); DEV Community, 2025 (opens in a new tab)
- A places or address search bar SDKUberCalibrd, 2026 (opens in a new tab); TrueInterview, 2026 (opens in a new tab)
- One login shared by the customer and delivery-partner appsSwiggyLinkedIn, 2025 (opens in a new tab)
- An event logging library that became a cart and wishlistFlipkartLinkedIn, 2024 (opens in a new tab)
- A loyalty campaign that refreshes once a dayTescoMedium, 2026 (opens in a new tab)
Popular on prep lists, but not in reports
An offline-first app, a news feed, a file downloader and live ride tracking appear on most prep lists. An aggregation of candidate reports found no one who was actually asked them. Calibrd, 2026 (opens in a new tab)
Offline behaviour still comes up constantly, as a follow-up inside other prompts rather than as the prompt itself. Reddit, 2025 (opens in a new tab); Medium, 2026 (opens in a new tab)
Follow-ups candidates were asked
- How does a ViewModel keep its data across a configuration change?
- How would you handle offline mode, testing, DI and a slow network in this design?
- How do you balance battery, network and CPU against keeping data fresh?
- How do Hilt, coroutines and Compose work underneath?
- Why did you write each line of your machine-coding solution the way you did?
Where candidates slip
- Waiting for the interviewer to bring up offline mode, caching, DI and testing.
- Designing servers and load balancers when the round is about the app.
- A weak DSA round undoing strong Android rounds.
- Buggy or unfinished features in timed coding, such as a broken sort or no time for the second screen.
You design an app, feature or client library out loud, from the device’s point of view: screen state, layers, the API contract, caching, offline behaviour and background sync. Meta’s prep guide describes its Android design interview as 45 minutes of talking and drawing, almost never coding, and recent candidate reports match.
Keep preparing
- System design roundsBackend design, for loops that run a generic design round.
- DSA coding roundsThe rounds that still gate Android offers.
- SDE 2 interviewsMachine coding and what changes at mid level.
- Android developer questionsCommon questions with sample answers.
- Mobile developer questionsQuestions across Android and iOS.
- PhonePe interviewsQuestions and process for PhonePe roles.
Sources
Last reviewed . Candidate reports are paraphrased, and formats vary by team, location and year.
- Recommendations for Android architectureAndroid Developers, 2026 (opens in a new tab)
- Build an offline-first appAndroid Developers (opens in a new tab)
- Data layerAndroid Developers (opens in a new tab)
- Save UI statesAndroid Developers (opens in a new tab)
- Preparing for your Android engineering interviewMeta Careers, 2016 (opens in a new tab)
- What is expected in an Android mobile system design interview? (r/androiddev)Reddit, 2025 (opens in a new tab)
- Got L5 Android engineer role at Google India (r/leetcode)Reddit, 2025 (opens in a new tab)
- Uber interview experience, senior software engineer, Android (r/leetcode)Reddit, 2024 (opens in a new tab)
- Google L4 Android framework, Bangalore, October 2025 (offer)LeetCode Discuss, 2025 (opens in a new tab)
- Google: Android system designBlind, 2025 (opens in a new tab)
- Mobile system design interview: how Meta, Google, Uber and others test itCalibrd, 2026 (opens in a new tab)
- The mobile system design interview: my FAANG prep journeyDEV Community, 2025 (opens in a new tab)
- My Google Android L4 interview experienceMedium, 2025 (opens in a new tab)
- My interview journey: Swiggy Android developer (SDE2)LinkedIn, 2025 (opens in a new tab)
- Swiggy SDE-2 interview experience (Android)Medium, 2024 (opens in a new tab)
- Flipkart Android SDE-2 interview experience (reposted from LeetCode)LinkedIn, 2024 (opens in a new tab)
- Android developer interviews at Zomato, Rapido and MeeshoMedium, 2025 (opens in a new tab)
- PhonePe interview experience, SDE (Android), Bengaluruinterviewexperiences.in, 2025 (opens in a new tab)
- Journey to PhonePe: cracking the Android engineer interviewMedium, 2025 (opens in a new tab)
- Cracking the Tesco Android engineer (L2) interviewMedium, 2026 (opens in a new tab)
- Airbnb senior Android engineer interview (United States)Taro, 2025 (opens in a new tab)
- Uber SDE-2 Android (L4) interview experienceTrueInterview, 2026 (opens in a new tab)
- My Uber mobile engineering interview experience (SDE-1)LinkedIn, 2025 (opens in a new tab)
- Guidelines for virtual interviews at Google (candidate guide)Google (opens in a new tab)
- Hiring process FAQMeta Careers (opens in a new tab)
Talk through the design in order
Your first 30 minutes are free. After that it’s $5 an hour, pay as you go, with no subscription.
Start free — 30 minutes, no card