
This is the round most Android engineers walk into unprepared - because it isn't web system design, and the usual prep material doesn't fit.
We'll run a real mobile design problem end to end: offline-first sync and conflict resolution, local persistence and caching strategy, pagination, API contract design from the client's side, background work, push and real-time updates, modularisation and feature boundaries - plus the non-functional things interviewers actually probe: battery, data usage, cold start, crash safety and staged rollout.
Both HLD and the mobile LLD variant (design this feature's classes and state). Say which you want when you book.
I've made these trade-offs at 300M-user scale on Paytm, so the answers come from production rather than from a blog post.
Free while I build this page up - all I ask is an honest review afterwards.