A web developer can fix a bug and have every user on the new version within minutes. A mobile app developer cannot. Once a build is in the Play Store or the App Store, old versions stay on people’s phones for months, every release waits on store review, and a crash on one popular budget Android handset can sink your ratings before anyone in the office has reproduced it. That is the job: building apps that behave well on devices you do not control and cannot update on demand.
Here is a mobile app developer job description you can copy for Android, iOS, Flutter or React Native roles, with guidance on choosing between native and cross-platform, how the role changes by level, how to screen candidates on apps they have shipped, the usual mistakes, and the right hiring model.
Mobile app developer job description template
Decide between native and cross-platform before you edit it. A native Android developer works in Kotlin with Jetpack Compose and a native iOS developer works in Swift with SwiftUI or UIKit. Native suits apps that lean heavily on device features, demanding graphics or the newest platform APIs. A Flutter or React Native developer ships one codebase to both stores, which suits most business and content apps and smaller teams. Write the job description for the one you have chosen. A listing that asks for Kotlin, Swift, Flutter and React Native together reads as if the company has not decided.
Pick one platform line in About the role and delete the others. If you need both native platforms, say so clearly.
About the role
[Company] is hiring a Mobile App Developer to build and improve [app name], used by [customers / field staff / partners] on Android and iOS. You will work in [Kotlin and Jetpack Compose / Swift and SwiftUI / Flutter and Dart / React Native and TypeScript] and own features from design to store release. You will join a [team size] mobile team in [city / remote], working with backend developers, designers and QA.
Responsibilities
- Build new features and screens in [platform / framework] following our app architecture [MVVM / Clean Architecture / BLoC / Redux].
- Integrate with backend APIs, handling poor networks, retries and offline use with local storage [Room / Core Data / SwiftData / SQLite / Hive].
- Implement push notifications, deep links and app links, and in-app purchases or subscriptions where the product needs them.
- Monitor crashes and ANRs with Firebase Crashlytics or similar, and fix the most frequent ones first.
- Improve app start time, scrolling smoothness, memory use and battery impact on lower-end devices.
- Write unit and UI tests, and work with QA on device coverage across OS versions and screen sizes.
- Prepare releases: signing, build configuration, TestFlight and Play Console tracks, staged rollouts and store listing updates.
- Respond to store review feedback and keep the app compliant with Apple and Google policy changes.
- Handle app permissions, secure storage of tokens and privacy disclosures correctly.
Requirements
- [X]+ years of mobile development with at least one app you helped ship to the Play Store or App Store.
- Strong skills in [Kotlin / Swift / Dart / TypeScript] and the matching UI framework [Jetpack Compose / SwiftUI / Flutter / React Native].
- Understanding of the app lifecycle, background work limits and memory management on your platform.
- Experience consuming REST or GraphQL APIs, with error handling and offline behaviour.
- Experience with state management suited to the framework, such as ViewModel and Flow, Combine, Riverpod or Redux.
- Experience with crash reporting and analytics tools such as Firebase.
- Comfort with Git, code review and a CI build for mobile.
Nice to have
- Experience on the other platform, or writing native modules or platform channels for a cross-platform app.
- Release automation with Fastlane or a mobile CI service.
- Over-the-air updates for React Native (for example with Expo) where store policy allows.
- UI test automation with Espresso, XCUITest, Maestro or Appium.
- Accessibility work such as TalkBack and VoiceOver support.
What we offer
- [Salary range].
- [Work mode].
- [Test devices provided, benefits].
How the mobile app developer role changes by level
Junior mobile developer. Builds screens and wires them to existing APIs and state, inside an architecture set by others. The job description should ask for one framework, a personal or college app that runs on a real device, and a willingness to learn release processes. Do not ask juniors to own store releases.
Mid-level mobile developer. Owns features fully, including offline behaviour, notifications and edge cases such as the user denying a permission or rotating the screen mid-upload. They handle releases on their own and read crash reports without being asked. Ask for apps they shipped and specific problems they fixed after launch.
Senior mobile developer. Sets the app architecture, modularisation and testing strategy, decides when a cross-platform app needs native code, and plans risky changes such as a migration from UIKit to SwiftUI or from XML layouts to Compose. They manage the release train and minimum supported OS versions. A senior JD should ask for evidence of an app they kept stable and fast over several releases.
Skills that matter most and how to check them
Mobile candidates can be judged on real, public evidence more easily than most developers, because their work is in the stores.
- Shipped apps. Ask for store links and install the apps before the interview. Ask what they personally built, what broke after release and how they found out.
- Lifecycle and offline. Ask: “A user fills a long form, gets a phone call and the OS kills the app. What happens to their data?” Good answers cover saved state, local storage and resuming the work.
- Crash triage. Show a real-looking crash report with a stack trace and the device spread, and ask how they would prioritise and fix it.
- Performance. Ask how they would find why a list scrolls badly on older Android phones. Listen for profiling tools, image sizing, recomposition or re-render counts, and work on the main thread.
- Release knowledge. Ask how they would roll out a risky change. You want staged rollouts, feature flags, and an understanding that a bad build cannot be pulled back from phones that already have it.
- A short build task. One screen that loads a list from an API, caches it for offline use and handles errors shows architecture, state handling and testing in a few hours of work.
Common mobile app developer job description mistakes
- Asking for every platform and framework. Fix: choose native or cross-platform first and name that stack. Put the other as a nice to have.
- Treating mobile as “frontend”. Mobile work includes offline storage, background limits and store compliance that web frontend roles do not. Fix: list these responsibilities so web developers do not apply by mistake.
- Leaving out the release process. Fix: say whether the developer handles signing, TestFlight, Play Console and store review, or whether a release manager does.
- No mention of devices and OS versions. Fix: state the minimum OS versions you support and whether the user base is mostly on lower-end Android phones, because it changes the performance work.
- Ignoring shipped work. Fix: ask candidates to include store links in their application, which filters out people who have only followed tutorials.
Contract, contract-to-hire or permanent
A contract mobile developer fits a first version of an app, a rebuild from native to Flutter or React Native, or a stability push to cut crashes before a big launch. These projects have a clear finish line.
Contract-to-hire works when you are launching a new app and want to see the developer handle real releases, store reviews and post-launch bugs before offering a permanent role.
Permanent suits companies whose app is a main channel to customers and needs continuous releases, OS upgrades every year and long-term ownership of the codebase. Zilo AI can help you hire mobile app developers in India on contract, contract-to-hire or permanent terms, including native Kotlin and Swift developers, Flutter and React Native engineers and mobile QA. Backend and QA roles that support a mobile team are on our IT talent page.
Frequently asked questions
What should a mobile app developer job description include?
The platform and framework (native Android, native iOS, Flutter or React Native), the app and its users, the architecture you use, whether the developer handles store releases, the OS versions you support, the level, and practical details of pay and work mode.
Should I hire a Flutter or a React Native developer?
If your web team already works in React and TypeScript, React Native lets them share knowledge and sometimes code. Flutter gives very consistent UI across platforms and suits teams starting fresh. Both can produce good apps; pick the one you can support long term and hire for it.
Can one developer build both the Android and iOS app?
Yes, with Flutter or React Native, and that is often the most practical choice for a small team. For two native apps, one person can cover both only for a simple app; most teams with native apps have separate Android and iOS developers.
What is the difference between a mobile app developer and a mobile QA engineer?
The developer builds the app. A mobile QA engineer tests it across real devices and OS versions and automates regression tests with tools like Appium, Espresso or XCUITest. Larger mobile teams usually need both.
If you would prefer Zilo AI to find mobile developers who have shipped real apps, tell us your platform, framework and release setup. Talk to Zilo AI about your mobile team.