Jobs · Marketing · California

Sr. Product Manager, R&D Enablement

Hinge Health · San Francisco, CA · 1 mo ago
HybridMarketing$163k–$224k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes About Us, About The Role, Key Responsibilities, What You'll Do, Basic Qualifications, Preferred Qualifications, Compensation Range. No explicit Benefits, Schedule. So we should include sections: About the role (maybe we can combine About Us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule only if content exists. We have content for About the role (the "About The Role" paragraph). Responsibilities: we have "Key Responsibilities" and "What You'll Do". Requirements: maybe Basic Qualifications? Qualifications: maybe Preferred Qualifications? Skills: maybe technical fluency etc. Benefits: none. Pay: we have Compensation Range. Schedule: none. We must preserve all substantive information, not invent or summarize away detail. So we need to include the content under each heading appropriately using

for prose and

  • for lists. We need to avoid boilerplate: remove "About Us", "Beware of Phishing Attempts", etc. Also remove duplicated lines. We need to keep all substantive info: About Us maybe not needed? The instruction says include a section ONLY when posting has real specific content for it. About Us is not one of the allowed headings; we could maybe treat it as part of About the role? But we have "About The Role" separate. The "About Us" could be omitted because not requested heading. However we might lose some info about company mission. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit About Us, we lose that info. But we cannot create a heading not in list? The allowed headings are those listed; we could still include a

    without heading? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g...). Likely they expect only those headings. However we could embed About Us as a

    before the first heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we cannot have extra paragraphs outside headings. But they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections. Possibly we can include an introductory

    before any heading? Not sure. Safer to include About Us as part of About the role? Could combine: About the role section could include both About Us and About The Role? But that might mix. Better: include a heading "About the role" and under it include the About The Role paragraph. Then maybe also include a preceding

    for About Us? But that would be outside any heading; maybe acceptable. Let's read instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other elements. It says use h3 for section headings (list). Likely they want only those headings. So we should not add other headings like About Us. But we need to preserve About Us info. Could we incorporate About Us into About the role section as a paragraph? The About the role heading is about the role, not about us. But we could still include a paragraph about the company under that heading; it's still substantive. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About Us and About The Role under About the role heading. That would preserve the info. Thus:

    About the role

    About Us Hinge Health is pioneering the world's most patient-centered Digital Musculoskeletal (MSK) Clinic. We are building a world-class R&D organization where engineers, product managers, and designers can move fast with confidence, create high-quality solutions, and stay deeply engaged in their work.

    About The Role We are seeking a Senior Product Manager to lead our R&D Enablement initiatives. In this pivotal role, you will treat our internal developer experience as a product, driving the strategy to achieve P90 industry benchmarks in velocity, throughput, and satisfaction. You will oversee the product roadmap for our Service Enablement, Mobile App Enablement, Platform Quality and SRE pods. Your mandate is to eliminate friction across the entire development lifecycle—from concept and code inception to deployment and observability—empowering our EPD (Engineering, Product, Design) teams to deliver value to our members faster and more reliably.

    Then Responsibilities: combine Key Responsibilities and What You'll Do. We need to use
    • for any list of duties/requirements/benefits. The responsibilities are bullet-like but not explicitly bullet list; they are paragraphs with bold headings. We could turn each responsibility into
    • . The content includes multiple responsibilities each with a bold heading and description. We'll parse them. Key Responsibilities list: - Define the R&D Enablement Strategy: Evolve our internal platform strategy from "Engineering Enablement" to broad "R&D Enablement" expanding scope to support Product Managers and Designers along with engineers with AI-powered tools and streamlined workflows. - Drive the "5 Pillars" of R&D Excellence: * AI Adoption: Lead the integration of AI tools (coding assistants, observability, knowledge management) to automate repetitive tasks and save 5+ hours/week per individual. * Velocity & Local Iteration: Champion initiatives like ephemeral environments (Okteto) and CI/CD optimization to drastically reduce lead time for changes. * Quality Engineering: Prioritize tooling for flaky test elimination and advanced testing paradigms to reduce production incidents. * Instrumentation & Observability: Drive the adoption of structured logging and unified dashboards (DataDog) to democratize production visibility. Ensure our RnD process is well instrumented so that we can measure improvements that process changes & tools bring in. * Knowledge Management: Treat documentation as a product, consolidating fragmented knowledge into a centralized, authoritative source. - Manage the Platform Roadmap: Partner with Engineering Managers to prioritize technical investments against business value, managing backlogs for Service Enablement, App Enablement, and SRE teams. - Measure What Matters: Rigorous tracking of success metrics, including DXI (Developer Experience Index), PR Throughput, DORA metrics, and Mean Time-to-Recovery (MTTR). - Voice of the Customer: Conduct quarterly DX surveys and "listening tours" to identify friction points and translate feedback into actionable product requirements. What You'll Do: - Translate the "RnD Enablement Strategy" into concrete quarterly roadmaps. - Lead the rollout of a unified Developer Experience Platform (DXP) to measure productivity and team performance. - Collaborate with App Enablement (Mobile DevOps & Mobile App Platform) to optimize the mobile/frontend developer experience, specifically for our Phoenix application stack and release processes. - Drive cultural change by incentivizing documentation, deep work, and "paved road" adoption across the organization. - Partner with Security and Infrastructure teams to balance speed with compliance and reliability. We can combine these into a single
        list. Requirements: Basic Qualifications. Basic Qualifications: - 5+ years of Product Management experience, with a strong preference for candidates who have worked on Internal Developer Platforms (IDP), DevOps tools, or B2B technical products. - Technical Fluency: You can have deep technical conversations with engineers about CI/CD pipelines, microservices architecture, cloud infrastructure (AWS), and mobile release cycles. - Data-Driven: Experience using metrics like DORA, SPACE, or DevEx to guide decision-making and measure success. - Program Management: Strong technical program management skills to orchestrate complex, cross-functional initiatives. - Change Management: Proven ability to drive adoption of new tools and processes across a large, distributed engineering organization. We can put these as
          . Qualifications: Preferred Qualifications. Preferred Qualifications: - Working knowledge with our specific tech stack: AWS, Kubernetes, TypeScript, React Native, Kafka, and DataDog. - Familiarity with Backstage (Mission Control) or similar internal developer portals. - Experience implementing GenAI tools (e.g., GitHub Copilot, Cursor, Glean) in an enterprise environment to drive productivity. - Background in SRE or Platform Engineering principles. We can put as
            . Skills: maybe we could extract technical fluency etc. But we already have those under qualifications. Could create a Skills section summarizing technical skills: AWS, Kubernetes, TypeScript, React Native, Kafka, DataDog, CI/CD, microservices, etc. But we risk duplicating. The instruction: prefer few substantive sections over many thin ones. We could omit Skills if content overlaps with Qualifications. But we need to preserve all substantive info; if we omit Skills we might lose explicit mention of skills. However the qualifications already cover skills. Might be okay. Pay: we have Compensation Range: $163K - $224K. So we need a Pay section with that. Schedule: none, so omit. Benefits: none, omit. Thus final HTML:

            About the role

            About Us Hinge Health is pioneering the world's most patient-centered Digital Musculoskeletal (MSK) Clinic. We are building a world-class R&D organization where engineers, product managers, and designers can move fast with confidence, create high-quality solutions, and stay deeply engaged in their work.

            About The Role We are seeking a Senior Product Manager to lead our R&D Enablement initiatives. In this pivotal role, you will treat our internal developer experience as a product, driving the strategy to achieve P90 industry benchmarks in velocity, throughput, and satisfaction. You will oversee the product roadmap for our Service Enablement, Mobile App Enablement, Platform Quality and SRE pods. Your mandate is to eliminate friction across the entire development lifecycle—from concept and code inception to deployment and observability—empowering our EPD (Engineering, Product, Design) teams to deliver value to our members faster and more reliably.

            Responsibilities

            • Define the R&D Enablement Strategy: Evolve our internal platform strategy from "Engineering Enablement" to broad "R&D Enablement" expanding scope to support Product Managers and Designers along with engineers with AI-powered tools and streamlined workflows.
            • Drive the "5 Pillars" of R&D Excellence:
              • AI Adoption: Lead the integration of AI tools (coding assistants, observability, knowledge management) to automate repetitive tasks and save 5+ hours/week per individual.
              • Velocity & Local Iteration: Champion initiatives like ephemeral environments (Okteto) and CI/CD optimization to drastically reduce lead time for changes.
              • Quality Engineering: Prioritize tooling for flaky test elimination and advanced testing paradigms to reduce production incidents.
              • Instrumentation & Observability: Drive the adoption of structured logging and unified dashboards (DataDog) to democratize production visibility. Ensure our RnD process is well instrumented so that we can measure improvements that process changes & tools bring in.
              • Knowledge Management: Treat documentation as a product, consolidating fragmented knowledge into a centralized, authoritative source.
            • Manage the Platform Roadmap: Partner with Engineering Managers to prioritize technical investments against business value, managing backlogs for Service Enablement, App Enablement, and SRE teams.
            • Measure What Matters: Rig

Similar jobs