Qualification and Experience:
- 5‒8+ years in software QA, automation engineering, or release engineering
- Proven experience owning orsignificantly building a CI/CD or test automation system from
the ground up
- Experience working in mobile-first or product-driven engineering organizations
- Familiarity with both iOS and Android release tracks preferred
Required Technical Skills:
- Strong proficiency in at least one test automation framework (Appium, Playwright, Detox,
XCUITest, Espresso, or equivalent)
- Hands-onexperience designing and maintaining CI/CD pipelines (GitHub Actions, Bitrise,
GitLab CI, or similar)
- Experience with test architecture across multiple layers (unit, integration, E2E)
- Solid understanding of mobile build and release processes (App Store / Play Store
deployment, versioning, environment management)
- Experience with test reporting, coverage tooling, and quality dashboards
- Proficiency in at least one scripting/programming language (Dart, Python, TypeScript, Kotlin,
or Swift)
Required Leadership Skills:
- Ability to define and advocate for quality standards across the engineering team.
- Strong written and verbal communication —you can clearly explain why a release should or
should not go out.
- Ability to work cross-functionally with mobile engineers, backend engineers, and product
without needing to be managed.
- Comfort making judgment calls on release readiness under time pressure.
- Systematic thinker who documents and shares decisions, not just fixes problems quietly.
Nice to Have:
- Experience with performance testing integration into CI pipelines (k6, Gatling, or similar).
- Flutter or Dart experience.
- Experience with feature flags and canary / staged release strategies.
- Background working in F&B, logistics, or high-frequency consumer applications.
Who Will Succeed in This Role (You will thrive here if you...)
- Treat the pipeline as a product and hold it to the same quality bar as the app itself
- Get frustrated when releases are blocked by uncertainty rather than actual bugs
- Look at a flaky test and feel compelled to fix the root cause, not just re-run it
- Are comfortable owning a system that other engineers depend on and take that
responsibility seriously
- Want to leave a team measurably faster and more confident at shipping than when you join
a Necessity, not a Luxury