Engineering Manager, Home Library

Hinge Health•San Francisco, CA

4d•Hybrid

About The Position

Every time a Hinge Health member opens the app, your team's work is what greets them. The Home ("Today") tab and Explore/Library experience are the primary surfaces through which millions of people find, start, and return to their care — and a platform that a dozen other pods build on top of every sprint. We're evolving these surfaces from static, one-size-fits-all screens into a flexible, personalized member experience that routes each person to the right activity at the right moment. This is an experimentation-first team: we validate every bet in production, move through A/B tests at a high clip, and treat the Home screen as an ongoing product — not a shipped feature. We need a hands-on engineering leader to own what comes next.

Requirements

Bachelor's degree in Computer Science, Engineering, or a related technical field
3+ years of experience managing a team of 5+ engineers in a fast-paced product environment
Strong mobile or client-side engineering background — React Native, or equivalent depth in a BFF/full-stack web context — with a track record of shipping member-facing UI at scale
Experience owning a major product surface end-to-end , from architecture through experimentation through production reliability
Demonstrated ability to run A/B experiments and reason about experimentation strategy (sample sizes, interference effects, decision rules)
Track record of hands-on technical contribution as an EM — code reviews, architecture decisions, PR merges

Nice To Haves

React Native / Phoenix depth : Experience building or leading teams in large React Native codebases, with working knowledge of client performance, render optimization, and app architecture patterns
Server-Driven UI experience : Familiarity with SDUI patterns and the tradeoffs of moving layout logic from client to server
AI-native development practices : Experience using Cursor, Claude Code, or equivalent agents as core workflow infrastructure — not just autocomplete. Opinions on prompting, agent review, and harness engineering
Platform engineering mindset : Experience operating a shared product surface where other teams build on top of your output — balancing internal velocity with external stability
GraphQL / Apollo : Familiarity with Apollo caching, BFF patterns, and the performance implications of client-driven data fetching in a mobile context

Responsibilities

Build deep trust with your team of ~8 engineers, embed yourself in the React Native (Phoenix) codebase and BFF layer, and establish your rhythm with PM and Design partners.
Audit the current SDUI migration plan, identify risks, and start sequencing the team's experiment backlog with clear owners and dates.
Drive the SDUI migration to completion — enabling new experiments and layouts to ship without app releases and unlocking a step-change in experiment velocity.
Stand up a rigorous experimentation framework (card ordering, layout variants, content strategies) that balances sample sizes, interference effects, and isolation in a constrained user pool.
Make the Today tab a meaningful daily pull for members and turned Explore into a high-intent "second session" surface through Favorites, content discovery, search, and better personalization.
Own the team's AI-native development practices — architecture docs, Claude Code skills, AI-assisted PR workflows — and be recognized across the neighborhood as the standard-bearer for Harness Engineering.
Operate as a high-trust platform partner, with clear extension patterns that allow other pods to build safely on Home.