Sr Staff Engineer, Mobile

About the role and team
Engineering at Uber means building for real-world impact under real-world constraints. As a Senior Staff Software Engineer in Rider, you will shape the technical architecture and long-term evolution of the systems that power the Rider experience globally.
Deep mobile architecture expertise will be the anchor for this role, but not its boundary. You will operate across mobile clients, edge capabilities, and backend services, tackling problems spanning application architecture, performance, reliability, server-driven experiences, client-server contracts, and emerging on-device intelligence.
Your impact will extend well beyond the code you write. You will shape how multiple engineering teams build and ship Rider experiences—establishing durable technical foundations, simplifying complex systems, making high-leverage architectural decisions, and enabling teams to move faster without compromising performance, reliability, or quality.
What you’ll do
Define the multi-year technical strategy and architecture for Rider experiences across mobile applications, client platforms, edge capabilities, and supporting backend services.
Set the architectural direction for the Rider application and client platform, enabling multiple teams to independently build and evolve experiences without compromising performance, reliability, or consistency.
Establish engineering standards and technical foundations across architecture, dependency management, build health, application size, startup and runtime performance, observability, testing, and release quality.
Architect server-driven and cross-platform experience frameworks, making deliberate trade-offs between native, web-based, shared, and backend-driven implementations.
Define durable client-server contracts covering API design, schema evolution, backward compatibility, rollout safety, experimentation, offline behavior, and failure recovery.
Shape the architecture for emerging on-device and edge capabilities, determining what should run on the client versus backend systems while balancing latency, privacy, reliability, battery consumption, and cost.
Build frameworks, SDKs, developer tools, and reusable abstractions that make it easier for product teams to deliver high-quality Rider experiences without repeatedly solving underlying platform problems.
Work with Product and Engineering leadership to identify architectural constraints and technical bets that materially expand the set of Rider experiences we can build, and shape investment priorities accordingly.