Staff Software Engineer, Visits at Hinge Health · LumiJobs
Remote
senior
$192k–$264k
H1B: yes
Hinge Health Staff Software Engineer at Hinge Health leading technical direction for the Incentive Platform. Responsible for domain modeling, production data migrations, and building APIs for eligibility and entitlement logic.
Responsibilities
We're looking for a Staff Engineer to join our Referrals team and help us build a unified Incentive Platform. The domain that tracks eligibility, entitlement, and fulfillment state for incentive rewards. Our team owns and operates this platform: the system of record for what a member is owed and when.
This is a high-ownership, systems-first role within the team. You'll set technical direction for a platform that's mid-consolidation. Carving a clean domain boundary out of an existing service, closing known correctness gaps, and negotiating the contracts that other teams build against. You'll work closely with product and data science, and have a direct line to business outcomes like referral conversion and cost-per-acquisition.
Own the technical direction for the Incentive Platform. Carve a dedicated domain out of its current home, with enforced boundaries and a facade other services call instead of reaching into internals.
Generalize eligibility and entitlement logic into real, owned APIs, replacing duplicated caps and ad hoc scripts with a single source of truth for what a member has earned and is owed.
Run production data migrations. Dual-write, backfill, cutover on a system with financial and compliance stakes, where correctness during the transition matters as much as the end state.
Negotiate and build the technical contract with Fulfillment: idempotent order creation, failure handling, real-time inventory, and reserve/release semantics. You're the technical counterparty other teams negotiate with, not just an implementer of their asks.
Find and close correctness gaps in the current system. Places where real dollar-value entitlements are miscounted, under-specified, or rely on an undocumented assumption.
Partner with product, design, and analytics to define what to build and why, balancing short-term wins with long-term platform leverage.
Raise the engineering bar by driving code quality, system design standards, observability, and technical decision-making on the team.
Mentor engineers on the team, growing their judgment on architecture and cross-team tradeoffs over time.
Participate in the team’s weekly on-call rotation, helping ensure the reliability and timely support of the systems we build.
Qualification
High ownership
Required
Domain modeling under legacy constraints - You've carved a bounded context out of a service with accreted responsibilities, without a rewrite, while it kept shipping.
Production migration experience - You've run a dual-write/backfill/cutover on a real data model, ideally with financial or compliance stakes where getting it wrong is expensive.
Full-stack depth - Strong skills across technologies such as React, React Native, TypeScript, NestJS, GraphQL, Node.js, relational and non-relational databases, Docker, Kubernetes, AWS, and Redis. We don’t expect a perfect match on every technology, but you should be fluent in most.
Staff-level leadership - You’ve set technical direction for a team, influenced cross-functional roadmaps, and made architectural decisions that have held up over time.
Bachelor’s degree (or foreign equivalent) in Computer Science, Engineering, or a related technical field.
10+ years of professional software engineering experience, including meaningful time working on production systems at scale.
Hands-on experience building and operating full-stack applications (for example, using React/React Native on the frontend and Node.js/TypeScript or similar on the backend).
Preferred
Experience designing or evolving incentive, rewards, ledger, or entitlement systems that carry real financial or compliance stakes.
Experience running a production data migration (dual-write, backfill, cutover) without a maintenance window, on a system where correctness during the transition mattered.
Experience negotiating or owning a service contract with another engineering team — API design as a cross-team negotiation, not just an internal interface.
Proven experience setting technical direction for a team, owning architectural decisions, and driving high-quality execution in partnership with product and data science.
Proven experience setting technical direction for a team, owning architectural decisions, and driving high-quality execution in partnership with product and data science.
Prior work at a consumer growth-focused company (for example, e-commerce, marketplaces, or consumer apps) and/or experience with viral or referral growth mechanics.
Experience working in healthcare or other regulated-data environments.
High ownership, low bureaucracy — this team moves quickly and ships iteratively while maintaining high technical standards.