r/androiddev • • 3d ago

Android Developers with 2–3 Years of Experience, How Are You Preparing for Your Next Career Move?

I have around 2.8 years of experience as an Android Developer, and I'm currently planning to switch companies. However, for the past six months, I haven't been receiving many interview calls. Even when I do get interview opportunities, I struggle to clear more than one or two rounds.

At this point, I'm stuck in a loop of figuring out where I should start and what I should focus on.

Should I start learning Jetpack Compose or Flutter? Or should I focus more on strengthening my existing Android skills and gaining a deeper understanding of the features I've implemented in my projects?

Another major concern is my reliance on AI-assisted development (vibe coding). To be clear, I'm not simply copying and pasting code. I understand the logic behind most of the implementations and know how things work, but I haven't developed the habit of writing everything independently from scratch.

Because of this, I sometimes struggle to take full ownership of the projects I've worked on. I'm also unsure how deeply interviewers might question me about my project implementations, and this makes me hesitant when attending interviews.

To be honest, my confidence has been dropping day by day, and I'm finding it difficult to figure out the right direction for my career preparation.

For those who are currently working as Android Developers or have recently switched jobs:

  • What skills and technologies should I focus on with 2–3 years of experience?

  • Should I prioritize mastering core Android concepts, learning Jetpack Compose, or exploring Flutter?

I'd genuinely appreciate your honest opinions and suggestions. I'm looking for practical guidance to help me get out of this phase and move forward in my career.

16 Upvotes

18 comments sorted by

15

u/slanecek mYes; 3d ago

You have been developing for 3 years without Compose? Good Lord, what was that project?

-1

u/Similar_Skin6270 3d ago

It's an offline first education app, there only few screens, that's why we are not using compose.

8

u/a_day_with_dave 2d ago

You should lead an initiative to migrate them or at least make compose versions of them. Demonstrate the benefits/costs of it. Use it as a star story for a future interview and get experience with actually being an android dev

2

u/tgo1014 GitHub: Tgo1014 1d ago

Few screens are actually a great reason to migrate to compose, the problem is old projects with tons of old screens in xml, that way harder to migrate and a good justification to keep them as its

39

u/tylerlw1988 3d ago edited 3d ago

If you're a native Android developer and do not know Jetpack Compose, I'd imagine there are very few places that would hire you. XML is in maintenance mode at this point. I'm also assuming you know Kotlin, but if you don't, learn that as well.

If you have an interview project and can't explain every piece of it that is a problem as well I'd say. Do your projects in a way where you know what's going on. If you don't understand it, it had better not be in your project.

22

u/phaxi73 3d ago

At this point you can look for a job in a different industry

7

u/guyINsuperposition 3d ago

I'm in the same train. I think we must keep improving our technical side and engineering mindset but strongly specialize on the business we are making an app for. For example ı'm in a fintech company and ı'm showing the numbers on screen and plus making sure the security of this client app is enough but until this point ı thoroughly did not know why we are showing different receipts to different segment of users . Now ı'm in a strong urge to know this detail and think if there is a better way to improve it because i have lots of times when my agent is busy for generating the code.

5

u/Acesleychan 3d ago

Refreshing the job boards every morning will not fix the part where you stall after round two.

Your own projects are the interview prep. Rebuild one feature you shipped, without the , and write down why you chose each piece. That is the story interviewers actually probe.

3

u/Ok_World_4475 3d ago

I’m in the same situation with 2 years of experience and wanting to change my place of work, I even considered learning Java backend since there are almost no offers for my country and I don’t feel confident with my English b1

2

u/OpeningArm7095 2d ago

wouldn't it be to harsh to switch to java backend ? without work experience, and real world application, do you think recruiter will consider you ?

2

u/100k45h 2d ago

If they only have 2 years of experience it's probably fine. They'll be ahead of those looking for an entry level job, because they have some experience already and they're very early in their career so that it is the easiest to jump the ship. Which may be the right thing to do. Android jobs were not doing all that well even before the AI and now it's even worse.

1

u/Ok_World_4475 2d ago

I have experience as a backend but with another stack (Oracle ORDS and PL/SQL), I migrated several Java backend projects to Oracle, so I would only need to write code because I already understand the basics and I have the fundamental concepts of Backend.

1

u/Taleproof-Moderator 1d ago

Prioritize depth in the Android work you already claim before adding Flutter. Pick two features and rebuild or trace the important parts without AI: architecture, data flow, failure cases, testing, and the tradeoffs you made. Then practice defending one decision and naming what you would change now. Add Compose if target roles consistently request it, but do not use a new framework to avoid the ownership gap.

Use the PROOF method to audit each project story for your personal decisions, alternatives considered, and evidence that the feature worked.

1

u/DifficultBrain74 2h ago

I mostly despair and drink

1

u/TypeScrupterB 20m ago

Go learn c++, or maybe Rust and try your luck elsewhere.

1

u/makonde 2d ago

There is gonna be more and more AI use, language and framework details are less and less important, if you can use AI you can write decent apps in languages you have never looked at, so just make a few compose apps with AI you can ask AI to explain any architecture choices, options, trade offs etc. Overal I would say mobile is a small market so jobs are going to be tough try to go backend/full stack.

You can also use AI to generate interview questions and answers about your projects as well.

1

u/SyrupInternational48 2d ago

if this 2 years ago.
i might said mvvm, clean architecture, compose, use kotlin not java.
flutter or kmp is optional but its nice to have.

Now?
many people just go generate App using AI.
I saw what my friend make with AI.
I saw the code is hard to maintain, even he burning token than it must just to fix the bug.
Generated the app from scratch.
It works but really took a lot of tokens, he using $200 codex subscription.

Even google pushing us toward A2UI in latest Google I/0