Quality and Release Manager at Raya | Torre

Quality and Release Manager

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: Employment

Provide your expected compensation while applying
location_on
Remote (anywhere)
Shared by
Emma of Torre.ai
9 days ago

Responsibilities


We prioritize learning and teamwork and love giving people the opportunity to champion solutions to big challenges and grow into better versions of themselves. You thrive at the intersection of quality and shipping, and you're excited to build the release systems, quality gates, and testing strategy that let Raya ship a consumer app our members trust every time.ResponsibilitiesQuality 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 leadershipContinuous Improvement: Run release retros, turn incidents and escaped defects into durable process fixes, and connect release decisions to the incident response processRelease 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 forwardGo/No-Go Process: Define release readiness criteria, lead go/no-go decision makingQualifications6+ years in software quality, release management, or engineering, with 3+ years managing peopleDeep knowledge of the App Store release lifecycle: TestFlight, phased release, expedited review, and rejection handlingExperience with subscription and payment flows on iOSExperience building test automation strategy for mobile, including real-device testing, feature flags, and progressive rolloutsExperience deciding the split between automated and manual testing, and managing third-party QA or crowdtesting vendorsFluency with CI/CD tools such as GitHub Actions, and strong knowledge of Git branching strategies for mobile release workflowsClear, direct written communicationWhat Sets You ApartSystems Builder: You build process and automation, so release quality depends on systems rather than memoryImpact-driven: You focus regression and automation coverage on the paths that matter most to members, rather than chasing full coverage everywhereOwnership mentality: You take escaped defects from discovery to root cause to preventionBridge Builder: You partner with engineering managers, product, and leadership, embedding quality into everyday workflows while balancing team velocityBias toward shipping and iteration: You improve the release process incrementally in short cycles rather than waiting for a perfect system