This is a full-time, fully remote Android Developer role open to candidates anywhere, with a salary up to $112,000 per year. The team builds and maintains native Android applications used across a range of devices, and the person hired for this seat will own real, shipping features rather than first shadow someone else's work for months.
What you'll do
- Design, build, and maintain native Android applications across a range of devices and OS versions
- Integrate app features with backend REST APIs, coordinating directly with the engineers who own those services
- Diagnose and resolve bugs and performance issues surfaced through automated testing and real user feedback
- Take part in code reviews and keep the codebase clean and well-documented in Git
- Shape UI decisions using Material Design principles as the working standard
Performance issues don't always show up in a test suite. Some of them only surface once an app is running on a five-year-old device with a cracked screen and a spotty connection, and part of this job is chasing those down without waiting for a ticket to tell you where to look.
Qualifications and experience
The entry-level education bar here is a four-year college degree in a computing-related field. That alone won't carry an application far, though. Hiring managers want to see a portfolio of Android applications that have actually shipped, not coursework projects that never left a local build. Candidates should bring at least 24 months of hands-on experience building native Android apps. Kotlin or Java should feel like home, and working knowledge of the Android SDK is assumed rather than something to pick up on the job.
Required skills
- Kotlin
- Java
- Android SDK
- Material Design
- REST APIs
- Git
- Mobile app testing
Most candidates lean more heavily on one of Kotlin or Java than the other, and that's fine. What matters more is comfort moving between them when a legacy module or a client library forces the issue.
Nice to have
None of the following is required, but each one makes an application stronger. Experience with Jetpack Compose is increasingly common on newer codebases, and familiarity with Firebase for analytics, crash reporting, or push notifications tends to shorten the ramp-up period. Exposure to CI/CD pipelines for mobile release management is useful, and so is prior work on an app with a meaningful install base, since that kind of experience tends to come with lessons about scale that smaller projects don't teach.
Team and how the work actually runs
The team is fully distributed, so async communication is the default rather than an exception written into a handbook nobody reads. Naukri Mitra lists postings like this one on behalf of employers who have already committed to remote-first hiring, meaning the interview process is built around that reality rather than treating it as a compromise. Standups happen more often via written updates than via video calls, and code review turnaround matters more than being online at any particular hour. Release weeks run tighter than the rest of the sprint, and anyone joining this role should expect a handful of late pushes each quarter alongside the steadier stretches in between.
Compensation and benefits
- Health coverage
- Paid time off
- 401(k) matching
- Remote-work flexibility
- Paid holidays and occasional team-building events, depending on the employer
The $112,000 annual salary reflects the experience level requested above; it isn't a ceiling reserved for exceptional candidates, nor a floor that gets negotiated down. For anyone comparing Android developer remote salary ranges with other remote openings, this one sits solidly within the range typical for a mid-level native Android role with a 2-year experience bar.
Getting started in a role like this
Most people who land remote Android developer jobs get there the same way: a public portfolio of shipped work, a couple of years spent solving real bugs instead of tutorial exercises, and enough Kotlin or Java fluency that the SDK stops feeling like a reference manual and starts feeling like a tool. If that description matches where a candidate already is, the qualifications above should read as familiar rather than aspirational.
How to apply
Submit a resume along with a link to a portfolio or published app, or both if available. Applications that include a direct link to a live app on the Play Store tend to move through screening faster, since it gives the reviewing engineer something concrete to look at before the first call is scheduled. Location doesn't factor into eligibility for this posting; the work is remote and open worldwide, and the hiring team reviews applications on a rolling basis.
