Principal Mobile Engineer, Platform

Remote $227k–$272k senior 2 months ago full-time quality 8.7/10
React NativeiOSAndroidSwiftKotlin

As a Principal Engineer, you will:

  • Own mobile platform architecture
  • Define and evolve the architecture of MetaMask Mobile (React Native + native).
  • Make key tradeoffs between JS/TS, RN, and native to balance performance, reliability, and iteration speed.
  • Design and steward core platform systems (e.g., OTA, analytics foundations, data/persistence, auth, VPN/geolocation primitives).
  • Lead high‑impact, cross‑team initiatives.
  • Drive large upgrades and migrations (React Native, navigation, foundational libraries).
  • Lead structural performance and stability work: startup time, crash rate, ANRs, jank, memory usage, bundle size.
  • Break large efforts into incremental, shippable milestones with clear impact.
  • Elevate developer experience & automation.
  • Improve tooling, local dev ergonomics, build/test pipelines, and release workflows for all mobile engineers.
  • Establish clear patterns for navigation, state management, and platform primitives to reduce cognitive load.
  • Push towards “push‑button” releases and reduced operational toil via automation.
  • Build an AI‑enabled platform.
  • Integrate AI/LLMs into workflows to scaffold code, enforce patterns, and improve testing and feedback loops.
  • Help define how tickets and platform patterns leverage AI safely and effectively.
  • Drive app health & performance culture.
  • Define and evolve metrics and dashboards for performance, stability, and efficiency.
  • Provide tools and guidance so feature teams can self‑diagnose and own regressions.
  • Champion shared accountability for app health across all teams contributing to mobile.
  • Multiply impact through leadership.
  • Mentor Senior/Staff engineers and influence technical direction across Wallet Platform and MetaMask.
  • Lead design and architecture reviews for critical platform areas.
  • Help shape hiring and technical culture for a lean, senior, high‑leverage Mobile Platform team.

Would be great if you brought this to the role:

Experience:

  • 10+ years building and scaling mobile apps, including ownership of large, production React Native or hybrid mobile platforms.
  • Prior Staff/Principal‑level impact: leading complex, cross‑team technical initiatives.

Technical depth:

  • Deep expertise with React Native in production: architecture, performance, debugging, bridging.
  • Solid experience with native iOS (Swift/SwiftUI) and/or Android (Kotlin/Jetpack), including native modules and performance tuning.
  • Strong understanding of mobile CI/CD, release engineering, and OTA systems.

Platform & systems mindset

  • Track record building internal platforms, shared libraries, or tooling for other engineers.
  • Comfort operating in ambiguity and designing durable, reusable solutions.
  • Strong architecture and communication skills; able to align diverse stakeholders.

Leadership & mentorship:

  • Proven ability to influence without authority, set technical direction, and raise the engineering bar.
  • Experience mentoring senior engineers and shaping technical culture.

AI‑curious / AI‑pragmatic

  • Experience or strong interest in using AI/LLMs to improve developer productivity and code quality.

We’re passionate about building a diverse team of humans and as such, if you think you've got what it takes for our chaotic-but-fun, remote-friendly, start-up environment—apply anyway, detailing your relevant transferable skills in your cover letter.

  • The salary range for US-based candidates only will be determined throughout the interview process depending on experience and skills.
  • US pay range (not including bonus, equity or other benefits) $227,000—$272,000 USD.

Similar jobs

Before you apply

  • Legitimate employers never ask you to pay anything to apply or get hired.
  • Never share seed phrases or private keys. No real job needs them.
  • Do not install software ("test tasks", "trading tools", "video call clients") sent during hiring.
  • Check that the application page's domain really belongs to Consensys.