Engineering and IT · Interview questions
Mobile Developer interview questions
These questions check whether a candidate can keep an iOS and Android app stable, released on a steady rhythm and usable on weak connections. Ask every candidate the same questions and score against the notes.
The questions
Ask every candidate the same questions in the same order, and score each answer against the notes before you talk it over with the panel.
Tell me about the worst crash you have had in a released app. How did you find it, fix it and stop it coming back?
- What it tests
- Crash-free rate outcome.
- A strong answer
- They used a crash reporting tool to find the affected versions and devices, reproduced it and shipped a fix quickly. They added a test or guard and changed their release checks.
- Watch for
- Waiting for users to complain instead of watching crash data.
Here is a crash trace: a null pointer exception when the order screen opens after the app returns from the background. What are the likely causes and what would you check first?
- What it tests
- Practical debugging, app lifecycle.
- A strong answer
- They suspect state lost when the operating system killed the process in the background. They would check how screen state is saved and restored and reproduce it with developer settings that kill background activities.
- Watch for
- Wrapping the line in a null check without asking why the value is missing.
Walk me through how you get a release from a finished branch into users' hands on both stores.
- What it tests
- Two-week release outcome.
- A strong answer
- They describe a version bump, automated build, beta testing through TestFlight and a Play testing track, then a staged rollout while watching crashes. They know common store rejection reasons and plan for review time.
- Watch for
- Releasing to 100 percent of users at once with no way to pause.
Design offline support for an order history screen. What is stored on the phone, what does the user see with no signal, and what happens when the connection returns?
- What it tests
- Offline outcome, design work sample.
- A strong answer
- They store recent orders locally, show them with a clear last updated note and queue any user changes. On reconnect they sync, handle conflicts with a simple rule and tell the user if something failed.
- Watch for
- Showing an endless spinner when there is no connection.
The backend team wants to rename a field in an API response. Thousands of users have not updated the app. What do you tell them?
- What it tests
- Working with backend, supporting old versions.
- A strong answer
- They explain that old app versions will break and ask for both fields to be sent for a period. They mention tracking how many users are on old versions and using a forced update screen only as a last resort.
- Watch for
- Assuming every user updates the app straight away.
Tell me about a time you used app store reviews to find and fix a problem.
- What it tests
- Store rating outcome.
- A strong answer
- They noticed a pattern in reviews, matched it to device or version data and fixed it. They replied to the reviewers after the fix and saw ratings recover.
- Watch for
- Treating reviews as marketing noise that developers do not need to read.
Our app takes eight seconds to open on an older Android phone. How would you approach that?
- What it tests
- Performance on real devices.
- A strong answer
- They profile start-up on a real low-end device, find work that can be delayed or moved off the main thread and cut unnecessary libraries. They measure before and after on the same phone.
- Watch for
- Testing only on the newest flagship phone.
When would you follow the platform's own design conventions instead of making iOS and Android look identical?
- What it tests
- Platform knowledge, working with design.
- A strong answer
- They follow platform conventions for navigation, back behaviour, dialogs and system controls so the app feels familiar. They keep brand colours and content the same across both.
- Watch for
- Ignoring the Android back button or iOS swipe gestures.
New to structured interviews? Read how to run structured interviews and how to build an interview scorecard.
Start from the job description
These questions follow the first-year outcomes in the matching template.
Mobile Developer job description templateSimilar roles
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.