Senior Software Engineer, GI

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections with real specific content. Need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions. Also remove duplicated lines. Also remove "What You’ll Accomplish" etc? That is responsibilities. "Who You Are" is qualifications/skills. "Basic Qualifications" and "Preferred Qualifications" are qualifications. "What You’ll Love About Us" includes benefits (healthcare, 401k, ESPP). Also "Compensation Range" is Pay. "Hinge Health Hybrid Model & Location" gives schedule (hybrid, 3 days in office). Also location maybe not needed but schedule. We must not repeat job title as heading. No Job ID. We need sections: About the role (maybe from first paragraph describing opportunity). Responsibilities (what you'll accomplish). Requirements (basic qualifications). Qualifications (maybe preferred qualifications). Skills (maybe technologies). Benefits (what you'll love about us). Pay (compensation range). Schedule (hybrid model). Ensure we only include sections with real content. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract. About the role: The first paragraph(s) describing Hinge Health, GI product line, building new product, etc. Let's capture: "The Opportunity Hinge Health is the leader in Digital Physical Therapy and we are expanding to new areas outside of physical therapy. In May we launched the new Migraine product line, and now we are building a new team from scratch for a Gastrointestinal (GI) product line. GI is a $135B market in the US alone and after the acquisition of Cylinder Health, we are in a great position to rapidly build new products in the GI space. This is your opportunity to build a brand new product from scratch, defining the product that millions of Americans will see in their healthcare plan next year. As a Senior Software Engineer for GI, you’ll build an understanding for the 60M+ Americans afflicted by this health condition, ensuring that Hinge Health builds a comprehensive end-to-end experience to treat them, run rapid experiments to validate your assumptions, and launch a brand new digital care product for GI. What differentiates HingeHealth from other platforms is our fast pace of innovation blending licensed care providers with AI solutions and medical grade hardware to deliver a complete experience that improves the health of our users. You’ll partner closely with staff engineers, team leaders including cross-functional partners in Product, Design, and Marketing across our hubs in San Francisco, Montreal, and Bangalore to build a new GI product. As a hands-on engineer, you’ll contribute to and review code daily, raise the quality bar, and independently ship impactful improvements to one of our most visible product surfaces." That seems about the role. Responsibilities: "What You’ll Accomplish" sections with 3 months, 6 months, 1 year bullet points. We need to preserve as list items. Let's extract bullet points: First 3 months: - Contribute to defining the GI product line from scratch. - Deliver at least 1 large project that introduces new product capabilities, often acting as a maintainer for key code repositories. - Break down complex problems into manageable tasks, ensuring steady and predictable delivery while identifying and resolving root causes of incidents. - Exhibit strong user and business judgment, grounding decisions in customer needs and business priorities to drive durable product value - Communicate technical ideas clearly to both technical and non-technical partners, and document solutions for future reference. First 6 months: - Implement key functionalities of the new GI product delivering high-quality, bug-free, high-performance software on a tight schedule. - Have a track record of independently driving 3+ high-complexity projects from the roadmap as their engineering leader. - Implement engineering best practices such CI/CD, automated testing, monitoring, or client performance across the code repo you support. - Proactively improve the maintainability, availability, and performance of the team’s features, and contribute to the team’s overall architecture and developer tooling. - Integrate and leverage AI technologies to automate processes and enhance product features, contributing to Hinge Health’s AI-driven care platform. - Mentor and support junior engineers, providing thoughtful code reviews and real-time pairing First year: - Have launched the new product and already work on iterations to adapt it using real member feedback post-launch. - Drive cross-team initiatives to improve the end-to-end journey for GI end users - Continuously raise engineering standards on the pod (testing, observability, reliability, accessibility, performance) and help scale the team’s impact as the product and membership grow. We'll put these under Responsibilities as

• . Requirements: Basic Qualifications list: - A minimum Bachelor’s Degree (or equivalent) in Computer Science, Engineering or related technical field - A minimum of 3 + years of non-internship full time professional software development experience - 4+ years of experience with at least one software programming language - 4+ years of experience in the full software development life cycle - Experience delivering large software projects or features in a production environment - Proficiency in at least one modern programming language (e.g., Python, Java, JavaScript, etc.) Qualifications: Preferred Qualifications list (maybe combine with Skills). But we need separate sections: Qualifications and Skills. The instruction: use headings for Qualifications, Skills, Benefits, Pay, Schedule. We can put preferred qualifications under Qualifications. Skills under Skills (technologies). Let's extract. Preferred Qualifications: - Technologies: Experience building in large React Native codebases, TypeScript/Node.js & Go backends, GraphQL, AWS services (e.g., Lambda, SQS, SNS, SageMaker), tooling for client performance, render optimization, devops and app architecture patterns. - Product Integration mindset: History operating a product surface that integrates across multiple platforms owned by different teams. - Track record of running experiments (e.g., A/B tests or multivariate tests) on core product surfaces and using results to drive roadmap decisions. - Strong proficiency with TypeScript/JavaScript, React Native, and modern mobile development tooling; familiarity with backend services (e.g., Node/TypeScript, GraphQL, or similar) is a plus. - Demonstrated ability to mentor and grow other engineers through code reviews, design collaboration, and technical guidance. - Comfort collaborating with product, design, and data/analytics partners to define metrics, interpret results, and refine experiences. - Experience developing consumer-facing apps used by millions/billions of users. - Regulated environments: Experience working within healthcare (HIPAA) or other highly regulated domains involving sensitive member data. We can put these under Qualifications. Skills: maybe list specific technologies: React Native, TypeScript, Node.js, Go, GraphQL, AWS (Lambda, SQS, SNS, SageMaker), etc. But we already covered in Qualifications. However we need a Skills section; we can still list them. To avoid duplication, we could put the technology list under Skills, and keep Qualifications more about experience/mentor etc. But the instruction says prefer few substantive sections over many thin ones. We could combine Qualifications and Skills? But headings are prescribed; we must use them if we have content. We can put Qualifications as the list of preferred qualifications (including experience, mentorship, etc.) and Skills as the technology stack. Let's define: Qualifications (Preferred): - Product Integration mindset... - Track record of running experiments... - Strong proficiency with TypeScript/JavaScript, React Native, and modern mobile development tooling; familiarity with backend services... - Demonstrated ability to mentor and grow other engineers... - Comfort collaborating with product, design, and data/analytics partners... - Experience developing consumer-facing apps used by millions/billions of users. - Regulated environments: Experience working within healthcare (HIPAA) or other highly regulated domains... Skills: - Experience building in large React Native codebases - TypeScript/Node.js & Go backends - GraphQL - AWS services (Lambda, SQS, SNS, SageMaker) - Tooling for client performance, render optimization, devops and app architecture patterns But note that some of these overlap with Qualifications; but it's okay. Benefits: From "What You’ll Love About Us": inclusive healthcare and benefits: comprehensive medical, dental, vision coverage, gender-affirming care help, tools for family and fertility planning, travel reimbursements if healthcare not available. Planning for the future: traditional or Roth 401k with 2% company match. Modern life stipends: manage own learning and development, grow with us through discounted company stock via ESPP with easy payroll deductions. We'll list as bullet list. Pay: Compensation Range: $164K - $247K. Schedule: Hybrid role based in San Francisco office, requiring in-person attendance three days per week for a full 8-hour business day. On remote days, employees expected to work during core business hours with flexibility. Office dog-friendly, occasional off-site/on-site events. We'll output as

  maybe. Now ensure we don't include boilerplate like EEO, legal, phishing warning, etc. Also remove duplicated lines (like "This is a hybrid role based in the San Francisco office" appears twice; we keep once). Also remove "Learn more at http://www.hingehealth.com." (that's navigation? maybe not needed). Also remove "About Hinge Health" paragraph (that's company description, but maybe considered boilerplate? It's substantive about company but not about role; but we already have About the role includes some of that. The "About Hinge Health" paragraph is generic company overview; could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Hinge Health" is not explicitly prohibited but might be considered company description not needed. However it's substantive about the company; but we already have some description in About the role. To be safe, we could keep it as part of About the role? But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info too. However the "About Hinge Health" paragraph is about the company overall, not specific to role. It's still substantive. We could include it under About the role as additional context. But we already have a lot. Might be okay to include. But we must not include "Culture & Engagement" EEO etc. That's boilerplate; remove. Also remove "Beware of Phishing Attempts" etc. Also remove "By submitting your application you are acknowledging..." etc. Also remove "Learn more at http://www.hingehealth.com." maybe not needed but it's a link; could be considered navigation; but it's not a legal boilerplate. Might be okay to keep but it's a URL; we could keep as part of About the role? Probably safe to drop as it's just a link. We'll keep About Hinge Health paragraph as part of About the role? Might be redundant but okay. Let's craft HTML. Structure:

  About the role

  ... (combined description)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  $164K - $247K

  Schedule

  Hybrid role based in the San Francisco office, requiring in-person attendance three days per week for a full 8‑hour business day. On remote days, employees are expected to work during core business hours with flexibility. The office is part of a dog‑