Interview scorecard
Mobile Engineer
Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.
Mobile architecture
Structures a mobile app so features can be added, tested, and changed safely.
Questions
- Tell me about an app you structured. How did you divide the code?
- Describe a time the app's structure slowed your team down. What did you change?
- How did you decide where data lives between the app and the server?
1: Below the bar
Describes screens and files but not why the code is split that way. Cannot name a downside of the structure.
3: Meets the bar
Explains a clear structure and why they chose it. Names one or two downsides and how the team handled them.
5: Above the bar
Ties structure choices to team size and app growth. Explains trade-offs, a change they made later, and what it improved.
Platform knowledge
Uses iOS or Android capabilities and rules correctly, and explains why the platform works as it does.
Questions
- Tell me about a time a platform rule or limit changed how you built a feature.
- Describe a feature that behaved differently across OS versions or devices. What did you do?
- Tell me about a time you learned a new platform change. How did you apply it?
1: Below the bar
Names few platform features and treats the OS as a black box. Can't say why something behaves as it does.
3: Meets the bar
Describes platform rules and OS differences accurately from experience. Handles them with some research and explains the main reasons.
5: Above the bar
Explains the reasons behind platform behavior, uses native features fluently, and anticipates OS version differences and upcoming platform changes unprompted.
Performance
Finds and fixes slowness, battery drain, and memory problems in mobile apps by measuring before changing.
Questions
- Tell me about a time an app felt slow. How did you find the cause?
- Describe a fix you shipped for performance. How did you know it worked?
- Tell me about a time you traded speed for something else. What did you decide?
1: Below the bar
Guesses at causes and changes code without measuring. Cannot say whether the fix helped.
3: Meets the bar
Uses profiling tools to find a real bottleneck and checks the result. Focuses mostly on speed, less on battery or memory.
5: Above the bar
Sets a target, measures first, and proves the gain with numbers. Weighs speed, battery, and memory and prevents regressions.
Release management
Ships app updates safely through store review, staged rollout, and quick recovery when something goes wrong.
Questions
- Tell me about a time you shipped a mobile release. How did you prepare?
- Tell me about a release that went wrong after launch. What did you do?
- How do you decide whether a fix goes out now or waits for the next release?
1: Below the bar
Describes releasing as just uploading a build. Has no plan for store rejection, rollout, or undoing a bad release.
3: Meets the bar
Follows a clear checklist with testing and staged rollout. Handles a bad release but learns the lessons only afterward.
5: Above the bar
Plans rollout, monitoring, and a fallback before shipping. Weighs fix urgency against risk and improves the process after each problem.
Debugging
Finds the cause of a mobile app bug by narrowing it down methodically.
Questions
- Tell me about a hard bug you tracked down in a mobile app. How did you start?
- Tell me about a bug you couldn't reproduce on your own device. What did you do?
- Tell me about a fix that didn't work. How did you find out and what next?
1: Below the bar
Changes code by guesswork and hopes the bug goes away. Can't describe how they confirmed the cause or the fix.
3: Meets the bar
Reproduces the bug, uses logs or a debugger, and finds the cause. Confirms the fix but adds no safeguards afterward.
5: Above the bar
Forms and tests hypotheses, uses crash reports and device details to narrow it down, and adds a test or alert afterward.
Overall recommendation
Decide on your own, before you compare notes with the rest of the panel.