u/tiwari_ashuism

I've been an Android developer for a little over 2 years, and I'm struggling to get interviews despite applying consistently.

The problem is that most of the work I've done has been fairly straightforward product development, implementing screens, API integrations, bug fixes, feature enhancements, Firebase, Room, Jetpack Compose, MVVM, Coroutines, etc. I've definitely learned a lot, but none of it feels "resume worthy" compared to candidates who have worked on large scale architecture, performance optimization, offline sync, custom frameworks, SDKs, or other engineering heavy projects.

When I look at my resume, it feels very generic.

1. Built feature X
2. Integrated API Y
3. Fixed bugs
4. Improved UI
5. Released app updates

I rarely get the chance to write things like:

1. Reduced app startup time by 40%
2. Designed a scalable caching layer
3. Built a custom networking library
4. Led a migration from XML to Compose
5. Improved CI/CD pipeline
6. Built internal developer tools

I'm currently working full time, so I can't exactly change the type of work my company assigns me.

For those of you who have been in a similar situation:

1. What skills or projects made your resume stand out?
2. Are there engineering focused side projects that recruiters actually value?
3. Should I focus on things like custom libraries, SDKs, performance optimization, system design, AOSP, Gradle plugins, static analysis tools, or open source contributions?
4. If you had one year to transform a "generic" Android resume into one that gets interviews at top companies, what would you build or learn?

I'd really appreciate hearing from senior Android engineers or hiring managers about what actually catches their attention on a resume versus what's just resume fluff.

I’m planning to build one for a new product and I’m curious whether it was worth the added complexity.

Did it make your app development faster and cleaner, or did it just shift complexity to the backend?

I’d love to hear your experience, lessons learned, and whether you’d choose the same architecture again.

I'm not looking for the usual one-page resume with "Built scalable apps" and "Worked in Agile."

I want to see the resumes that actually got interviews at companies like Google, Uber, Airbnb, Stripe, Cash App, DoorDash, or high-growth startups.

Things I'd love to see:

1. Strong bullet points that quantify impact.
2. Side projects that stand out.
3. Open-source contributions.
4. Architecture or system design sections.
5. Performance optimizations.
6. CI/CD, build systems, Gradle, Kotlin, Compose, Coroutines, etc.
7. ATS-friendly formatting.
8. Anything that made recruiters reach out.

Feel free to anonymize your personal information before sharing.

The goal is to create a thread where Android developers can learn what an exceptional resume actually looks like instead of generic templates.

If you've landed interviews at top companies, your resume could help hundreds of fellow developers.

Let's build the ultimate Android resume reference thread.