Technical Mobile Release Manager

We are looking for a Mobile Release Manager with a heavy emphasis on Quality Assurance and technical proficiency. You will be responsible for the end-to-end delivery of our mobile applications. Unlike a traditional project manager, you will dive into the codebase, understand automated test suites, and bridge the gap between "code complete" and "App Store ready."

• Release Orchestration: Own the release lifecycle, including scheduling, coordinating, and managing deployments across multiple mobile platforms.
• QA & Risk Mitigation: Leverage your QA background to evaluate build health. You will identify "go/no-go" risks based on manual test results and automation coverage and results.
• Technical Troubleshooting: Use your programming skills to help debug CI/CD pipeline failures and understand technical debt that might impact release stability.
• Process Automation: Improve the mobile "Release Train," looking for opportunities to automate repetitive manual checks.
• Stakeholder Communication: Act as the primary point of contact for Product, Engineering, and Marketing. You must translate technical delays into business impact and vice versa.
• App Store Management: Manage submissions, metadata, and phased rollouts in App Store Connect and Google Play Console.

• Experience: 3-5 years in mobile software development or software quality assurance.
• QA Mastery: Deep understanding of the QA lifecycle. You must be comfortable performing "sanity checks" and interpreting complex automation reports.
• Programming Skills: Proficiency in at least one programming language (e.g., Swift, Kotlin, Python, or JavaScript). You should be able to read code and understand logic flow.
• Mobile Ecosystem: Strong knowledge of the Apple Human Interface Guidelines and Google Material Design submission requirements.
• Communication: Exceptional verbal and written skills. You can lead a "War Room" during a hotfix and clearly explain the path to resolution.

Preferred Skills

• Experience with CI/CD tools like Bildkite, Jenkins, or GitHub Actions.
• Experience with crash reporting tools like Sentry or Crashlytics to monitor post-release health.