Built by Android devs, for Android devs
AndroidDevKit is a free, community-maintained study guide for Android engineers. It brings practical questions, clear answers, and first-hand interview experiences into one place.
Why we built it
Interview preparation is often scattered across old blog posts, private notes, and courses that are difficult to evaluate before paying. We wanted a useful starting point that anyone can read, question, and improve.
What you'll find here
- Topic guides - Kotlin, Coroutines, Compose, Jetpack, architecture, system design, and more, each with a curated question bank.
- A real question bank - standalone questions tagged by difficulty, with answers that explain the reasoning an interviewer is after.
- Interview experiences - first-hand accounts of real interviews, including the rounds, questions, and outcome.
- Guides & strategy - longer articles on preparing, negotiating, and growing as a mobile engineer.
Why open source
The best interview material comes from people who just sat in the chair - and it goes stale fast. Keeping everything on GitHub means anyone can fix an answer, add a question, or share an experience in minutes, and the whole community benefits. No paywall, no sign-up, ever.
How the content is handled
Questions are organized by topic and level, then reviewed for usefulness, technical accuracy, and readability. Advanced questions stay in the senior section so beginners do not mistake them for prerequisites. When an answer depends on a specific Android or library version, contributors should say so and link to primary documentation.
Independence and attribution
AndroidDevKit is an independent community project. It is not affiliated with, endorsed by, or sponsored by Google or any company mentioned in an interview experience. Android, Kotlin, and other names belong to their respective owners. Shared experiences should not include confidential interview material or personal information.
Corrections and contact
Found an error, an outdated answer, or something that should not be published? Open an issue or pull request on GitHub. The editorial policy explains how corrections and contributions are reviewed.
The stack
Built with Astro, content authored in Markdown, and deployed on Cloudflare Pages. It's fast, static, and free to run - so it can stay that way.