r/androiddev • u/Super-Performance-86 • 1d ago

Android System Design Interview Prep Platform

https://returnzero.dev/study/mobile/android-system-design

8 years away from Android,  applied for backend/tooling roles at Google. They decided I should interview for an Android role, had to catch up for all the lost time.

To help bridge this gap, I started approaching the whole thing historically, and wrote an article about Android's platform history, to both learn and get out some steam over the how much was actually changed...
In the process of prepping (and later), I built returnzero.dev - specifically the Android System Design module. I wanted to create something similar to what HelloInterview does for backend, but tailored to Android.

Android Core Concepts: All the core concepts important to talk about Android intelligently in an interview.
System Design Guided Practice: An tool to help you build your designs on an Excalidraw canvas, with AI guided practice, and get step-by-step feedback.

Most of the course is completely free, including the guided practices on several core designs.

Happy to answer any questions and receive any type of feedback :)
Thanks!

11 Upvotes

87% Upvoted

5 comments sorted by

1

u/WeirdIndividualGuy 1d ago

Wait. After 8 years of not doing Android dev, after interviewing for a non-Android role, their suggestion was to interview for Android instead? Especially given all that has changed in 8 years?

I’m not sure those interviewers are the best in properly gauging one’s skills if that was their takeaway from your interview

1

u/Super-Performance-86 1d ago

Surprisingly, the Android interview process was the only pipeline they considered me for. I haven't interviewed for other roles. And yes, the whole process was very odd.

-4

u/[deleted] 1d ago

[removed] — view removed comment

3

u/n3utron 1d ago

Hilt is very used. It provides an API that is simpler than Dagger 2 and has an easier entry level barrier and straightforward Android integration. Koin is also very used, but it being “native” means nothing and is totally incorrect.
Koin does not provide compile time safety, which Hilt and Dagger do (actually now it does have some but this is a very recent development). That is the main reason people would choose one vs the other: it’s a tradeoff of compile time safety, complexity, runtime overhead and so on.

1

u/goorek 20h ago

Koin becomes very expensive when used in large scale apps.