Quality and Release Manager

Quality Strategy: Own the QA strategy across automated and manual testing, deciding what we automate, what we test by hand, and what we accept as risk, with regression coverage on critical paths like onboarding, payments, subscriptions, messaging, and login, including where third-party testing services and AI-assisted QA tooling fit in.

Visibility and Communication: Maintain the release calendar and Quality scorecards including report crash rates, defect escape rates, and release health to leadership

Continuous Improvement: Run release retros, turn incidents and escaped defects into durable process fixes, and connect release decisions to the incident response process

Release Ownership: Run the release process end-to-end for the Raya iOS app from predictable release trains with clear cut, freeze, and submission dates through App Store submission, phased rollout, and rollback/fix forward

Go/No-Go Process: Define release readiness criteria, lead go/no-go decision making

Deep knowledge of the App Store release lifecycle: TestFlight, phased release, expedited review, and rejection handling

Experience with subscription and payment flows on iOS

Experience building test automation strategy for mobile, including real-device testing, feature flags, and progressive rollouts

Experience deciding the split between automated and manual testing, and managing third-party QA or crowdtesting vendors

Fluency with CI/CD tools such as GitHub Actions, and strong knowledge of Git branching strategies for mobile release workflows

Clear, direct written communication

Systems Builder: You build process and automation, so release quality depends on systems rather than memory

Impact-driven: You focus regression and automation coverage on the paths that matter most to members, rather than chasing full coverage everywhere

Ownership mentality: You take escaped defects from discovery to root cause to prevention

Bridge Builder: You partner with engineering managers, product, and leadership, embedding quality into everyday workflows while balancing team velocity

Bias toward shipping and iteration: You improve the release process incrementally in short cycles rather than waiting for a perfect system