Lead Mobile Release Engineer

Key Responsibilities

• Act as the primary owner and single point of contact for all mobile release engineering activities across iOS and Android
• Lead the end-to-end mobile release lifecycle, including build orchestration, internal testing, beta distribution, store submission, phased rollout, and production release
• Define and enforce release standards, governance, checklists, timelines, and go/no-go criteria
• Build and maintain CI/CD pipelines for mobile applications using GitHub Actions, Azure DevOps, Jenkins, or Bitrise, integrated with Fastlane
• Manage release workflows for App Store Connect and Google Play Console, including TestFlight, Firebase App Distribution, release tracks, phased rollouts, and store compliance requirements
• Own and secure mobile code-signing processes, including certificate and provisioning profile management using Fastlane Match or equivalent tooling
• Improve build reliability, speed, and developer experience by optimizing macOS runners, caching, dependency management, and artifact handling
• Partner with mobile developers to support native iOS/Android, React Native, and Flutter delivery workflows
• Drive shift-left quality and security practices by integrating unit tests, UI automation, static analysis, dependency scanning, and mobile security checks aligned to OWASP MASVS
• Implement and review post-release observability using Crashlytics, Sentry, and New Relic to monitor app health, regressions, and release quality
• Manage supporting infrastructure on AWS and/or Azure using Terraform and Ansible
• Support internal tooling and backend services used by the mobile ecosystem with Docker and Kubernetes where required
• Coordinate closely with engineering, QA, product, security, and leadership to plan releases, manage dependencies, communicate risks, and resolve blockers
• Mentor engineers on release best practices, improve team maturity, and drive continuous improvement across delivery processes
• Own release metrics such as build success rate, deployment frequency, build duration, failed submissions, rollback rates, and release stability