Principal, Software Engineer
Nike
- Location
- Beaverton, Oregon
- Work model
- On-Site
- Level
- Principal
- H-1B history
- 111 approvals (FY2023)
- Posted
- Sep 3, 2026
Skills
About this role
Become a Part of the NIKE, Inc.
Team
NIKE, Inc. does more than outfit the world’s best athletes. It’s a place where passionate individuals come together to create the future of sport. We are unapologetic about who we are and what we’re after - bringing innovation and inspiration to every athlete* in the world. We look for athletes who can push boundaries, elevate our potential and continue leading us to greatness. The next tastemakers, playmakers, risk takers and glue players. Are you game? WHO YOU’LL WORK WITH The Activity Apps team builds and operates Nike Run Club (NRC) and Nike Training Club (NTC) - the mobile experiences that move millions of Nike athletes through runs, workouts, training plans, and guided coaching every day. This role partners directly with Directors, Architects, Product Managers, Designers, Sport Science, and engineering squads across iOS, Android, wearables, and the backend services that power activity at Nike. This role reports to the Director of Engineering for Activity Apps and collaborates across mobile platform, athlete, coaching content, and developer experience functions globally.
WHO WE ARE
LOOKING FOR Nike is seeking a Principal Software Engineer who brings architectural depth, technical authority, and a passion for transforming how mobile activity experiences get built at consumer scale. The successful candidate has a proven track record of leading consumer mobile applications, influencing cross-functional technical strategy across iOS and Android, and mentoring senior engineers toward higher standards. This role requires someone who thinks in systems, drives modern mobile development practices, and can bridge long-term platform vision with day-to-day execution. The ideal candidate thrives in ambiguity, takes ownership of the hardest technical problems - the always-on workout session, the sensor that disagrees with itself, the watch that has to keep working when the phone dies - and leaves the apps measurably better than they found them. 10+ years of software engineering experience; Bachelor’s degree in Computer Science, Engineering, or equivalent combination of education, experience or training Expert-level proficiency in one or more of Swift/SwiftUI, Kotlin/Compose, or modern cross-platform stacks (KMP), with a strong record of shipping consumer mobile applications at significant scale (10M+ MAU) Deep experience with the systems that make activity apps work: Core Location / FusedLocationProvider, Core Motion / SensorManager, background execution and lifecycle, audio session management, push and silent-push pipelines, and durable offline session storage At least 5 years of hands-on experience architecting companion-device experiences on watchOS and/or Wear OS, including phone-to-watch sync, standalone workouts, and state reconciliation Working knowledge of health and fitness data platforms - HealthKit, Health Connect / Google Fit - and third-party device integrations (Apple Watch, Garmin, Strava-class partners) Deep experience with mobile CI/CD ecosystems, build and release tooling (Xcode, Gradle, Fastlane, App Store Connect, Google Play), experimentation infrastructure, and developer experience optimization for mobile teams Demonstrated ability to lead technical architecture reviews, establish engineering standards, and influence decisions across multiple teams and platforms WHAT YOU’LL WORK ON You’ll architect and own the most critical and complex pieces of Nike’s activity apps - products used daily by athletes across the globe. Your work shapes standards, tools, and technical culture at a scale few companies can offer. Design end-to-end architecture for NRC and NTC across iOS, Android, and companion wearables - ensuring session reliability, sensor accuracy, battery efficiency, security, and scale Own the long-term shape of the workout session stack - sensor capture, GPS pipelines, background reliability, recovery from process death, and durable upload - so that