Mobile App Developer, Remote Worldwide
This is a full-time, fully remote mobile app developer position, open to candidates in any location. The salary is $110,000 a year in USD. Work happens on either iOS or Android, depending on the candidate's background, and the apps involved are already live and in use, not starting from a blank slate.
The app in question has an active user base, which changes the nature of the work somewhat. A change that looks small in a pull request can still show up in hundreds of support tickets if it's wrong, so testing and release discipline matter more here than they would on something still in early development.
Background and experience
A bachelor's degree is required, most commonly in computer science or a related technical field. Candidates should have 24 months of experience building mobile applications, along with a portfolio of apps that have actually been published, not just built and shelved. Native development experience is expected, though solid cross-platform work counts as well if the underlying fundamentals are clearly present.
Reviewers weigh a shipped app more heavily than a portfolio site, since getting something through app store review and into real users' hands surfaces problems a personal project never has to face. Submission requirements, crash reports, one-star reviews explaining exactly what broke: that history matters here.
Two years is the floor for this role, not an ideal number. Someone with more experience who's spent most of it maintaining a single legacy app, with little exposure to newer frameworks or current app store requirements, may actually be a weaker fit than someone closer to the two-year mark who's worked across a couple of projects.
Skills
- iOS or Android development
- Swift or Kotlin
- REST APIs
- Mobile UI design
- App Store deployment
- Git
Cross-platform frameworks such as Flutter or React Native aren't required, but are worth mentioning if you've used them, particularly for a team maintaining both iOS and Android versions from a single codebase. Experience with push notification services like Firebase, mobile-specific testing tools such as XCTest or Espresso, and basic CI/CD setup for app builds will all strengthen an application. None of these are dealbreakers on their own, and a candidate strong in the core skills shouldn't rule themselves out just because one or two are missing from their background. Accessibility work on mobile, such as ensuring a screen reader can navigate the app correctly, comes up occasionally and is a plus rather than a requirement.
What the work looks like
This developer designs, builds, and maintains mobile applications end-to-end and connects those apps to backend services via REST APIs. A meaningful share of the job is compatibility work: an interface that looks correct on a current flagship phone can still break on a five-year-old Android device with a smaller screen and an older OS version, and catching that before release is part of the role, not an edge case someone else handles.
- Own the full lifecycle of a mobile feature, from initial build through ongoing upkeep
- Integrate the app with backend services and REST APIs
- Test across device types and OS versions to catch compatibility issues before release
- Diagnose and fix performance problems, including slow load times and memory issues
- Prepare and submit builds for app store review
- Write documentation for how a feature works, especially anything touching platform-specific quirks
Backend integration work leans on whatever API contract the server team has already defined, so a good chunk of the debugging here involves figuring out whether a bug lives on the app side or somewhere further back in the request chain before fixing it.
Pay and benefits
The role pays $110,000 per year, and the position is remote with no location restrictions.
- Health coverage
- Paid time off
- 401(k) matching
- Remote-work flexibility
- Regular performance reviews with merit-based pay increases
The performance review process is straightforward: reviews happen on a set schedule rather than an unpredictable one, and a strong review translates into an actual increase rather than a conversation about one. There's no cap on how many review cycles someone can go through before an increase is on the table; it's tied to the work, not to tenure.
Day to day
Work is organized around app store release cycles rather than a fixed weekly rhythm, since a submission to Apple or Google can take a few days to clear review, regardless of how ready the build is. Naukri Mitra sees steady interest in postings like this one because remote mobile roles paying at this level, open worldwide, still aren't the norm across the industry. Planning tends to build in that review lag rather than treating it as a surprise each time.
Device-specific bugs show up more often here than they would on a purely backend team, and some of them only appear on hardware nobody on the team currently owns. Part of the job is figuring out how to reproduce and fix a problem you can't directly see in front of you, using crash logs and remote debugging rather than a device in hand.
Direct communication with whoever reported an issue helps more than most people expect going in. A vague bug report becomes fixable much faster once someone asks the right two or three follow-up questions about the device model, OS version, and the exact steps that led to the crash.
How to apply
Submit a resume along with links to at least one published app you built or significantly contributed to. Note which parts of the app were your work if it was a team project. Applications are reviewed as they arrive, and candidates who move forward can expect a first conversation about their published work before any coding exercise.
The coding exercise is scoped to be completed in an evening rather than treated as a second job, and it draws on the same kind of compatibility and integration work described above rather than on an abstract algorithm problem. It's meant to look like the actual job because it is the actual job.
