Engineering and IT · Job description template
Mobile Developer job description template
For many customers, the mobile app is the product. The mobile developer owns the iOS and Android apps, from code to app store release. They are accountable for an app that stays stable, works on the phones customers really own and handles weak connections well.
First-year outcomes
What should be visibly different a year from now. Results, not tasks.
- The crash-free session rate stays at or above 99.5 percent on both iOS and Android, shown in a crash reporting tool such as Firebase Crashlytics.
- A new app version reaches both stores at least every two weeks, with no release rejected twice for the same reason.
- Core screens such as the home feed and order history open and show saved data with no connection, and sync changes when the connection returns.
- The app store rating rises to at least 4.3 on both stores, with every one-star review about a bug answered and logged.
The work
Recurring work
- Build new app features with the designer and backend developers.
- Prepare, test and submit releases to the App Store and Google Play.
- Watch crash reports after each release and fix the top crashes first.
- Read and respond to app store reviews that point to bugs.
Projects
- Add offline storage and sync for the most used screens.
- Set up automated builds and beta distribution through TestFlight and Google Play testing tracks.
- Reduce app size and start-up time on older Android phones.
Decisions they own
- How to structure the app code and local data storage.
- When a release is ready to go to all users or only a staged percentage.
- Which minimum iOS and Android versions to support, with the product owner.
People they work with
- The designer, to follow platform conventions on each operating system.
- Backend developers, to agree API changes that will not break older app versions.
- Support staff, to reproduce problems reported by users.
Requirements
Essential on day one
- Has published at least one app to the App Store or Google Play.
- Working skill in Swift, Kotlin, or a cross-platform framework such as React Native or Flutter.
- Understanding of app lifecycles, background work and local storage on mobile.
- Comfort with Git, code review and reading crash reports.
Helpful, but can be learned
- The second platform, if they are strong on one.
- Your build and release automation tools.
- Push notification services and deep linking.
How to assess it
One piece of evidence for each first-year outcome.
| Outcome | Evidence to look for |
|---|---|
| Crash-free rate at or above 99.5 percent | Show a real crash stack trace and ask what they would check first. Good candidates read the trace, form a likely cause and explain how to confirm it. |
| Releases every two weeks to both stores | Ask them to describe their release checklist. Good answers include staged rollouts, a beta group and how they handle a store rejection. |
| Core screens work offline | Ask them to design offline support for an order history screen. Good work covers local storage, showing stale data clearly and resolving conflicts when back online. |
| Store rating at 4.3 or above | Ask for an example of a bug found through reviews. Good answers show they linked reviews to crash data and replied after the fix shipped. |
Opening for the job ad
You will own our iOS and Android apps, from the first line of code to the store release. In your first year, the app should rarely crash, ship to both stores every two weeks and keep working when a customer loses signal.
Turning this into an ad? See how to write a job ad that gets applicants.
Next: interview for these outcomes
Eight structured questions for this role, each tied to an outcome above.
Mobile Developer interview questionsSimilar roles
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.