How would you design the test strategy for releasing a mobile banking app on iOS and Android every two weeks?
What the interviewer wants to hear
- Device and OS matrix based on analytics, using real devices or a device cloud
- Layered automation: unit, API, and a focused UI suite with Appium, XCUITest or Espresso
- Mobile-specific risks: interruptions, background kill, permissions, network changes, upgrades from old versions
- Security and compliance: secure storage, certificate pinning, session timeout, biometrics
- Staged rollout, crash monitoring, feature flags and forced update paths
- Backward compatibility of APIs for users on older app versions
Model answer
I would pick devices and OS versions from analytics, covering most users plus low-end and oldest supported devices, and test on real devices through a device cloud like BrowserStack. Automation would be layered: unit and API tests carry most checks, and a focused UI suite in Appium, or XCUITest and Espresso, covers login, transfers and payments on every build. Manual and exploratory time goes to mobile risks: calls and notifications mid-transfer, the app killed in the background, permission changes, switching between Wi-Fi and mobile data, and upgrading from older versions with saved data. Security checks cover secure storage, session timeout, biometrics and certificate pinning. Because users stay on old versions, backend APIs must remain backward compatible. Releases go out in stages, with crash monitoring, feature flags to switch off problems and a forced-update path for critical issues.
Can you answer it under time pressure?
Take a timed hard round and get scored on every answer.
More hard QA Engineer questions
- A critical bug reached production even though QA tested the release. How do you handle it and what do you change afterwards?
- Which quality metrics would you track for a product team, and which would you avoid?
- How would you test an integration with a third-party payment gateway that you do not control?
- Your team finds most bugs late, just before release. How would you shift quality earlier in the process?
- How would you test a feature whose output is not fixed, such as an AI chatbot or a recommendation engine?
- You join a company with no automation. How would you design a UI and API test automation framework that will still be healthy in three years?
- A product is built from 15 microservices owned by different teams. The shared end-to-end environment is slow and often broken. How would you design the testing strategy?
- You are not a penetration tester, but you are the only QA on the team. How do you include security testing in your everyday work?
- The full regression suite takes six hours, so the team releases only once a week. How would you get feedback down to under 30 minutes without losing confidence?