Sr Software Engineer iOS

Sr Software Engineer iOS Department: Engineering Team: iOS Location: San Francisco, United States Type: Full-Time **About the Role** We are looking for an **L5A Senior iOS Engineer** to build and own **earner‑facing iOS experiences for fleets**. You will: 1. Ship high‑impact features for **fleet earners** (couriers, mobility drivers, AV fleet operators) 2. Translate the **FleetHub** vision into intuitive iOS workflows that help fleet earners manage shifts, zones, earnings, and performance while collaborating with fleet managers and operations teams. 3. Implement **bespoke, fleet‑specific flows** for Courier, Mobility, and AV fleets while leveraging shared mobile platform components and patterns. This is a **hands‑on senior IC role**: you will lead projects end‑to‑end on iOS, contribute to architecture, and mentor other engineers, while partnering closely with Android, backend, product, design, and ops. What you will do: ### Build fleet earner experiences on iOS 1. Design, build, and maintain **iOS features for fleet earners** across courier, mobility, and AV fleets — from onboarding to daily operations and performance management. 2. Own end‑to‑end flows that help fleet earners: 3. Understand and plan **shifts & breaks** 4. Navigate **zones and positioning recommendations** 5. Interact with **depot and field support operations** 6. Track **earnings and performance** in a fleet context ### Bring the FleetHub model to life in the iOS app 1. Implement iOS features that sit on top of **Fleet Foundations** and **Fleet Management Core Modules** (onboarding, performance, incentives, command center, earnings). 2. Surface **Fleet Intelligence** (demand‑aware shift and positioning recommendations) in ways that are understandable and actionable for earners and fleet managers. ### Contribute to mobile architecture and platformization 1. Apply and extend Uber’s mobile architecture patterns (e.g., RIBs, shared platform components) so Fleet surfaces are **modular, testable, and reusable** across vertical teams. 2. Collaborate with Android and backend engineers to clearly separate **p