Technical Product Manager (Systems)

We need to output HTML fragment with sections: About the role? The posting includes "Job Summary" and "Responsibilities (Essential Functions)", "Qualifications (Education & Experience)", "Tools" (maybe part of responsibilities), "Benefits" (Our Benefits and Rewards), "Pay" (base salary range). No Schedule. Also "Location" maybe not needed. We must not repeat job title. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info, remove boilerplate: disclaimer, EEO, etc. Also remove "Description Local to Plano, TX Job Summary" maybe we keep location? It's minor metadata; we can fold into short

  . The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So location can be in a short p. We need sections only when posting has real specific content. So we can have: - About the role (maybe from Job Summary) - Responsibilities - Qualifications - Benefits - Pay We need to include Tools? Could be part of Responsibilities or Qualifications. The posting has a "Tools" bullet under Responsibilities? Actually after "Technical Tradeoffs, Risks & Delivery Enablement" there is "ToolsJira: Manage". It seems like a bullet: Tools Jira: Manage Knowledge, Skills, And Abilities ... Actually it's weird formatting. Let's parse: Responsibilities (Essential Functions) Product Definition Partnership (Shared with Marketing)Co-own product definition with Marketing PM (e.g., PRD/TPP, user needs, use cases, target outcomes), ensuring feasibility and testability. Translate PRD/user needs into system/sub-system requirements and technical acceptance criteria; drive shared understanding across engineering domains. System & Sub-system Requirements OwnershipAuthor and maintain system and sub-system requirements that are unambiguous, feasible, verifiable, and traceable, with clear acceptance criteria. Decompose requirements across mechanical, electrical, firmware, software, connectivity, and cloud; ensure constraints and assumptions are explicit. Own requirements change control for the assigned product: impact analysis, review/approval facilitation, and controlled updates through the lifecycle. Traceability & Verification Alignment (Design Controls Support)Maintain bidirectional traceability from user needs → system requirements → design outputs → verification evidence (trace links, trace matrix, and rationale). Partner with Verification & Validation to ensure verification plans/protocols align with requirement intent and acceptance criteria; resolve ambiguity and gaps early. Manage requirements + traceability artifacts through PLM to support lifecycle governance, controlled changes, and auditable history. Technical Tradeoffs, Risks & Delivery EnablementLead technical tradeoff discussions (architecture, scalability, performance, reliability, security, serviceability) for the assigned product, documenting decisions and rationale. Identify risks and dependencies; drive mitigation plans and timely decision escalation. ToolsJira: Manage Knowledge, Skills, And Abilities Strong systems thinking across HW/FW/SW/cloud; ability to translate needs into engineered requirements and interface definitions. Requirements engineering discipline: decomposition, acceptance criteria, traceability, and change impact analysis. Strong facilitation and communication skills; lead through influence across Engineering, Marketing, Quality/Regulatory, and IT. Operational excellence in intake and backlog governance using Jira; predictable pipeline practices. It seems the "ToolsJira: Manage Knowledge, Skills, And Abilities" is actually part of Qualifications? Actually after Technical Tradeoffs they list "ToolsJira: Manage Knowledge, Skills, And Abilities". Then they list "Strong systems thinking..." etc. This looks like a misplaced section: maybe they intended "Knowledge, Skills, And Abilities" as part of Qualifications. But we can treat that as part of Qualifications or Responsibilities. However the posting already has a Qualifications section later. The "Knowledge, Skills, And Abilities" bullet list seems like qualifications. So we should incorporate those into Qualifications. Thus we will have: - About the role (Job Summary) - Responsibilities (list of essential functions) - Qualifications (Education & Experience plus Knowledge, Skills, And Abilities) - Benefits (Our Benefits and Rewards) - Pay (base salary range) We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we should list each responsibility as
  • . For Qualifications we should list each requirement as
  • . For Benefits we list each benefit as
  • . For Pay we can just put a

    with the salary range. We need to preserve all substantive info, not invent or summarize away detail. So we need to include all details from the posting. Let's extract details. Job Summary: "Local to Plano, TX Job Summary The Technical Product Manager (TPM) partners with Marketing Product Management and cross-functional stakeholders to translate customer and stakeholder needs into clear, testable system and sub-system requirements across hardware, firmware/software, connectivity, and cloud components. The TPM drives technical clarity and alignment from requirements through delivery for a defined product and/or system scope. This role focuses on one primary product and owns intake and prioritization for that product’s R&D Engineering pipeline, ensuring work is triaged, clarified, sequenced, and delivered predictably using objective criteria and transparent backlog practices." We can combine location into a short p: maybe

    Location: Plano, TX

    then About the role heading. Responsibilities: Let's break down each bullet: - Product Definition Partnership (Shared with Marketing): Co-own product definition with Marketing PM (e.g., PRD/TPP, user needs, use cases, target outcomes), ensuring feasibility and testability. Translate PRD/user needs into system/sub-system requirements and technical acceptance criteria; drive shared understanding across engineering domains. - System & Sub-system Requirements Ownership: Author and maintain system and sub-system requirements that are unambiguous, feasible, verifiable, and traceable, with clear acceptance criteria. Decompose requirements across mechanical, electrical, firmware, software, connectivity, and cloud; ensure constraints and assumptions are explicit. Own requirements change control for the assigned product: impact analysis, review/approval facilitation, and controlled updates through the lifecycle. - Traceability & Verification Alignment (Design Controls Support): Maintain bidirectional traceability from user needs → system requirements → design outputs → verification evidence (trace links, trace matrix, and rationale). Partner with Verification & Validation to ensure verification plans/protocols align with requirement intent and acceptance criteria; resolve ambiguity and gaps early. Manage requirements + traceability artifacts through PLM to support lifecycle governance, controlled changes, and auditable history. - Technical Tradeoffs, Risks & Delivery Enablement: Lead technical tradeoff discussions (architecture, scalability, performance, reliability, security, serviceability) for the assigned product, documenting decisions and rationale. Identify risks and dependencies; drive mitigation plans and timely decision escalation. - Tools: Jira: Manage (maybe part of responsibilities? Actually "ToolsJira: Manage Knowledge, Skills, And Abilities" seems misplaced. But we can treat "Manage Jira for backlog management" as a responsibility. However the phrase "ToolsJira: Manage Knowledge, Skills, And Abilities" is weird. Let's interpret: The responsibility includes using Jira to manage backlog. The "Knowledge, Skills, And Abilities" likely belongs to qualifications. So we will not include a Tools section; we will incorporate Jira usage into Responsibilities as a bullet: "Manage backlog using Jira for intake and prioritization." But we need to be faithful: The posting says "Operational excellence in intake and backlog governance using Jira; predictable pipeline practices." That's under Qualifications? Actually appears after Knowledge, Skills, And Abilities. Let's re-evaluate. The text after "ToolsJira: Manage Knowledge, Skills, And Abilities Strong systems thinking across HW/FW/SW/cloud; ability to translate needs into engineered requirements and interface definitions. Requirements engineering discipline: decomposition, acceptance criteria, traceability, and change impact analysis. Strong facilitation and communication skills; lead through influence across Engineering, Marketing, Quality/Regulatory, and IT. Operational excellence in intake and backlog governance using Jira; predictable pipeline practices." This looks like a list of Knowledge, Skills, And Abilities (KSAs). So we should treat that as part of Qualifications. Thus Responsibilities end at Technical Tradeoffs, Risks & Delivery Enablement. Now Qualifications: Education & Experience: Bachelor’s degree in Engineering, Computer Science, Biomedical Engineering, or related technical discipline required. 3–5 years in systems engineering, technical product management, V&V, software/hardware engineering, or technical program leadership. Demonstrated experience translating user needs into system/sub-system requirements and collaborating with engineering teams to deliver verified outcomes. Proficiency with Jira for backlog management and with PLM for requirements + traceability artifacts management. Then Knowledge, Skills, And Abilities: Strong systems thinking across HW/FW/SW/cloud; ability to translate needs into engineered requirements and interface definitions. Requirements engineering discipline: decomposition, acceptance criteria, traceability, and change impact analysis. Strong facilitation and communication skills; lead through influence across Engineering, Marketing, Quality/Regulatory, and IT. Operational excellence in intake and backlog governance using Jira; predictable pipeline practices. We can combine these into a single qualifications list. Benefits: "Our Benefits and Rewards: In addition to the expected base salary, this role is eligible to participate inInogen’sannual performance bonus incentive plan,highly competitiveand company-sponsored benefits, and wellbeing programs rooted in our strong culture of excellence. As a valued member of our team, Inogen provideshealth, dental, and vision insurance, 401(k) plan plus employer contribution and match, andgenerous paid leaves such as vacation and sick leave, including paid volunteer time, that can support you and your family through moments that matter." We need to parse benefits: annual performance bonus incentive plan, highly competitive company-sponsored benefits, wellbeing programs, health/dental/vision insurance, 401(k) plan plus employer contribution and match, generous paid leaves (vacation, sick leave, paid volunteer time). We'll list each as
  • . Pay: "The base salary for this position is expected to be between $86,000.00 and $101,241.87 annually. However, actual base salary if hired will be determined on an individualized basis and will be based on non-discriminatory factors, including as to individual skills, education, experience and market location." We need to include that as a

    under Pay section. We should not include filler like "commensurate with experience". This is actual range, so we include. We must not include boilerplate: Disclaimer, EEO, etc. Now produce HTML. Structure:

    Location: Plano, TX

    About the role

    [Job Summary text]

    Responsibilities

    • Product Definition Partnership (Shared with Marketing): Co-own product definition with Marketing PM (e.g., PRD/TPP, user needs, use cases, target outcomes), ensuring feasibility and testability. Translate PRD/user needs into system/sub-system requirements and technical acceptance criteria; drive shared understanding across engineering domains.
    • System & Sub-system Requirements Ownership: Author and maintain system and sub-system requirements that are unambiguous, feasible, verifiable, and traceable, with clear acceptance criteria. Decompose requirements across mechanical, electrical, firmware, software, connectivity, and cloud; ensure constraints and assumptions are explicit. Own requirements change control for the assigned product: impact analysis, review/approval facilitation, and controlled updates through the lifecycle.
    • Traceability & Verification Alignment (Design Controls Support): Maintain bidirectional traceability from user needs → system requirements → design outputs → verification evidence (trace links, trace matrix, and rationale). Partner with Verification & Validation to ensure verification plans/protocols align with requirement intent and acceptance criteria; resolve ambiguity and gaps early. Manage requirements + traceability artifacts through PLM to support lifecycle governance, controlled changes, and auditable history.