Quality and Release Manager

Role overview This role owns quality and release management for a consumer iOS application that depends on member trust. The position sits at the intersection of QA strategy and shipping, building the release systems, quality gates, and testing programs that let the mobile team ship confidently. It combines hands-on process design with people leadership across engineering, product, and third-party QA partners.

Responsibilities - Define and own the QA strategy across automated and manual testing, deciding what to automate, what to test by hand, and what to accept as risk, with regression coverage on critical paths such as onboarding, payments, subscriptions, messaging, and login. - Run the end-to-end release process for the iOS app, including release trains, code freeze, App Store submission, phased rollout, rollback, and fix-forward. - Define release readiness criteria and lead go/no-go decisions with cross-functional stakeholders. - Maintain the release calendar and quality scorecards, reporting crash rates, defect escape rates, and overall release health to leadership. - Run release retrospectives and turn incidents or escaped defects into durable process and tooling improvements connected to the incident response workflow. - Evaluate and integrate third-party testing services and AI-assisted QA tooling into the quality program.

Requirements - 6+ years of experience in software quality, release management, or engineering, with 3+ years managing people. - Deep knowledge of the App Store release lifecycle, including TestFlight, phased release, expedited review, and rejection handling. - Hands-on experience with iOS subscription and payment flows. - Experience building a mobile test automation strategy, including real-device testing, feature flags, and progressive rollouts. - Experience deciding the automated-versus-manual testing split and managing third-party QA or crowdtesting vendors. - Fluency with CI/CD tooling such as GitHub Actions and strong knowledge of Git branching strategies for mobile release workflows.

Nice to have - Comfort designing systems and automation so that release quality depends on process rather than memory. - Strong written communication style with a bias toward incremental shipping and iteration.