Description
The Opportunity
The company’s mobile app reaches members through a production system spanning code integration, mobile builds, release candidates, app-store submission, and phased rollout. App Enablement helps mobile engineering teams ship dependable changes and build on a reliable, shared mobile platform. The team owns both the path from code merge through app-store release and the platform capabilities that help product teams build efficiently and consistently.
As a Senior Software Engineer on App Enablement, you’ll contribute across mobile release operations and platform engineering, with your focus shifting between them as team priorities change. You might improve build, CI, release, and rollout systems, then build or maintain shared mobile-platform capabilities such as the mobile-specific API layer that shapes backend data for the app, server-driven UI, navigation, deep links, and reusable media components. We’re looking for engineers with depth in one area who can partner across the other and are willing to learn into adjacent work. You’ll collaborate with engineering, Quality Engineering, release partners, and product teams. This is a hands-on role with broad impact across the mobile organization.
What You'll Accomplish
Design, build, and maintain tooling for mobile builds, release candidates, app-store submissions, and phased rollouts.
Build and evolve shared mobile-platform capabilities, including the mobile-specific API layer that shapes backend data for the app, server-driven UI, navigation, deep links, and reusable media components, in partnership with product pods.
Improve the reliability, speed, and observability of mobile CI and release pipelines; investigate recurring failures and reduce manual toil with durable fixes.
Coordinate release readiness, blocker triage, communication, and resolution with the teams responsible for affected changes.
Improve dependency management and mobile code-quality practices, including responses to security updates and iOS and Android ecosystem changes.
Reduce friction for feature teams with practical developer tools, documentation, and guidance, while respecting Quality Engineering’s ownership of test automation and sign-off.
Define and improve release-readiness checks, staged-rollout safeguards, monitoring, and rollback practices so teams can detect and respond to release risk.
Measure pipeline and release performance, identify recurring bottlenecks, and use evidence to prioritize improvements and communicate impact.
Balance delivery speed, release safety, maintainability, and compliance; mentor engineers through design discussions, code reviews, and shared operational practices.