Mobile QA Engineer interview questions and answers

9 of 9 questions shown

1. juniorCoverageHow do you choose which devices and OS versions to test?

   Model answer. Start from your own analytics: top devices and OS versions by sessions. Cover the latest two major OS versions, one low-memory Android phone, small and large screens, and major vendor skins such as Samsung One UI. Use real devices for sensors, camera and performance, and emulators or simulators for fast checks.

   Tools: BrowserStack

   I can answer this
2. juniorScenariosName mobile-specific scenarios that web testers often miss.

   Model answer. Interruptions such as calls and notifications, and backgrounding or process death with state restore. Permission denial and later revocation, offline and network switches, and rotation. Low battery or storage, upgrade from an older version with data migration, and push-notification deep links.

   I can answer this
3. midAppiumWhat causes Appium test instability and how do you reduce it?

   Model answer. Slow or fragile lookups (XPath), implicit waits and leftover device state. Use accessibility ids or resource ids, explicit waits, reset app state through launch arguments or adb, and one device per parallel session with its own ports. Keep driver and OS versions pinned.

   Tools: Appium

   I can answer this
4. midTool choiceWhen would you pick Espresso or XCUITest over Appium?

   Model answer. Native frameworks run in the same toolchain as the app, synchronise with the UI thread so they are faster and more stable, and allow white-box access. The cost is two suites, one per platform. Appium gives one cross-platform black-box suite in a language you choose, with slower and less deterministic execution.

   Tools: Espresso, XCUITest, Appium

   I can answer this
5. midNetworkHow do you test an app on an unreliable network?

   Model answer. Throttle with Network Link Conditioner on iOS, emulator profiles on Android, or a proxy such as Charles or mitmproxy. Check timeouts, retry with backoff, offline queues, no duplicate submissions when a request is retried, and understandable user messages.

   I can answer this
6. midReleaseHow do you test an app release through the App Store and Google Play?

   Model answer. Use TestFlight and Play internal testing tracks, check signing and version codes, and test upgrades from the previous two releases. Use staged rollout on Play and phased release on iOS and watch crash-free rate. On iOS you cannot roll back to an earlier build, only pause the phased rollout and ship a fix.

   I can answer this
7. midNavigationHow do you test deep links and universal links?

   Model answer. Open them from a cold start, from the background and while logged out, and with the app not installed to confirm the store fallback. Check malformed parameters, Android App Links verification (assetlinks.json) and the iOS apple-app-site-association file, and that login redirects return to the target screen.

   I can answer this
8. seniorPerformanceHow do you test mobile app performance?

   Model answer. Measure cold and warm start time, frame rate and jank (Perfetto on Android, Instruments on iOS), memory growth, battery and payload size, always on a low-end device. Set baselines and track them per build so regressions show up in CI.

   I can answer this
9. seniorSecurityWhich mobile-specific security checks belong in QA?

   Model answer. Tokens kept in Keychain or Keystore instead of plain preferences, certificate pinning behaviour, validation of deep-link input, exported Android components, PII in logs and behaviour on rooted or jailbroken devices. OWASP MASVS is a good checklist.

   I can answer this

No question matches those filters. Clear the search or choose All.