I'm working with a client in the Insurance industry on a Senior QA Automation Engineer role and am keen to speak with QA engineers who have built mobile automation frameworks from scratch.
Set up a mobile automation framework from scratch - chosen the tool, written the first tests, integrated it into CI, and grown coverage - across native iOS and Android apps. Web/API is a given; mobile is the main factor.
Must-haves -
- Mobile automation framework built from scratch. The CV must describe choosing the tool, structuring the framework, writing the first suite, and growing it. Not just maintenance part of it.
- A named mobile automation tool used in production - Maestro, Appium, Espresso, or XCUITest. The name must appear in a work bullet, not only in the skills list.
- Native iOS and Android exposure, not responsive web on BrowserStack. We want to see signing/provisioning, simulators/emulators, TestFlight, real-device labs etc named in their experience.
- Mobile CI/CD integration - Azure DevOps, GitHub Actions, or similar - for app build artefacts (IPA/APK), not just web test runs.
- Playwright/Postman (or equivalent modern web & API automation) on the web side. These are still important.
Strong nice-to-haves -
- Maestro specifically (we're standardising on it).
- BrowserStack, TestFlight, Intune named in real project context.
- Test coverage for native-mobile-only behaviours - offline mode, push notifications, deep links, biometric auth, app-permission flows, device fragmentation.
- Insurance, fintech, or payments domain experience.
- Azure DevOps Pipelines specifically.
- AI dev-tooling (Copilot, Cursor etc) in current use.