Technical Program Manager V

We need to output HTML fragment with sections: About the role? Actually we have content: About Ascendion (company description) maybe not needed as section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - About Ascendion: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have a company description. Might be better to put under "About the role"? However instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map content accordingly. We have: - Minimum Qualifications: Must have directly supported or led software programs governed by medical device regulation. - Preferred Qualifications: Established new release processes from scratch. Potential companies where candidates may have previously worked: Apple, Verily/Google, Samsung. - Key Responsibilities: list of many responsibilities. - Location: Burlingame, CA [5 Days Onsite] (Schedule? Actually location and schedule). Could be Schedule section? But schedule is about work schedule (e.g., full-time, part-time, remote). Here we have location and onsite days. Could treat as Schedule? Might be better to include location in a short paragraph, not as a heading. - Salary Range: $199,600 - $249,600 annually. That's Pay. - Benefits: list of benefits. Thus we can have sections: Responsibilities (ul), Qualifications (maybe combine Minimum and Preferred?), Benefits (ul), Pay (p). Possibly also About the role (p) using company description? But the company description is about Ascendion, not the role. Could be considered "About the role"? Might be okay to include a short paragraph about the role/responsibility? Actually we already have responsibilities. The "About the role" could be a brief summary of the role: Technical Program Manager V. But we are told not to repeat job title as heading. Could still have a paragraph describing the role: maybe combine company description and role purpose. However we must preserve all substantive information. The company description is substantive; we could include it as a paragraph under a heading "About the role" or maybe not needed. The instruction says "Prefer a few substantive sections over many thin ones." So we could combine company description and role summary into an "About the role" paragraph. But we also have location and schedule info; we could include location in a short paragraph under maybe "About the role" or separate? There's no heading for location; we could just include it as a paragraph after responsibilities. We must not create sections with filler. So we need to ensure each heading has real content. Let's plan:

  About the role

  Ascendion is an AI-native software engineering disruptor helping businesses innovate faster, smarter, and with greater impact. We partner with enterprise clients across North America, the UK, Europe, and APAC to solve complex challenges in data, experience design, software product engineering, and workforce transformation. Powered by expert engineers, thousands of AI agents, and our Engineering to the Power of AI (EngineeringAI) method, we deliver measurable outcomes that build trust, unlock value, and accelerate growth. As a Technical Program Manager V, you will manage deliverables for an FDA‑approved Hearing Correction feature classified as Software as a Medical Device (SaMD), ensuring compliance with QMS and regulatory standards.

  But we need to preserve all substantive information; we must not lose details like trademarks etc. The trademarks list is likely boilerplate? It's legal/trademark info; maybe we should remove as boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Trademarks might be considered legal boilerplate; we could drop it. However we need to preserve substantive information; trademarks are not substantive for job posting. Likely okay to drop. We also have culture description: "We have a culture built on opportunity, inclusion, and a spirit of partnership..." That's also maybe boilerplate but could be considered substantive about company culture. Might keep as part of About the role. We need to include Minimum Qualifications, Preferred Qualifications. Could combine into a "Qualifications" section with two sublists? Or separate Minimum and Preferred? The instruction only gives headings like Requirements, Qualifications, Skills. We could use "Qualifications" for both minimum and preferred, maybe with subheadings? But we cannot add extra headings beyond those? Not prohibited but we should follow given examples. Could use

  Qualifications

  and then within that have

  Minimum: ...

  Preferred: ...

  Or we could use
  for each. Better: Use

  Qualifications

  then
  • Minimum: Must have directly supported or led software programs governed by medical device regulation.
  • Preferred: Established new release processes from scratch. Potential previous employers include Apple, Verily/Google, Samsung.
  That preserves info. Responsibilities: we have a long list; we can put each as
  • . Benefits: list of benefits inside brackets; we need to extract them: medical insurance, dental insurance, vision insurance, 401(k) retirement plan, long-term disability insurance, short-term disability insurance, 5 personal days accrued each calendar year (Paid time off benefits meet the paid sick and safe time laws that pertains to the City/ State), 10-15 days of paid vacation time, 6 paid holidays and 1 floating holiday per calendar year, Ascendion Learning Management System. We should preserve as list. Pay: Salary Range: $199,600 - $249,600 annually. Also note factors affecting pay. We can include that as a paragraph. Schedule: we have location and onsite days: Burlingame, CA [5 Days Onsite]. Could be considered Schedule? Might be better to include location in a short paragraph under maybe "About the role" or separate heading "Location"? Not in allowed headings. Could treat as Schedule? The schedule is about work schedule (onsite days). Could include as

    Schedule

    Burlingame, CA – 5 days onsite per week.

    But we must not create Schedule section unless posting actually states them. It does state location and onsite days, so we can. Now we need to remove boilerplate: The repeated lines like "Learn more at https://ascendion.com/." maybe we can keep as part of About the role? It's a link; maybe we can keep as part of description. But it's not essential; could drop. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at ..." is not boilerplate but maybe navigation? It's a link to company site; could be considered navigation; but it's not duplicated. Might keep? Safer to drop as it's not substantive to job. Also the trademarks list we drop. The culture paragraph: "We have a culture built on opportunity, inclusion, and a spirit of partnership. Come, change the world with us: ..." That's somewhat promotional but could be considered substantive about company culture. Might keep as part of About the role. The "Want to change the world? Let us know...." is application instruction; we should drop. Now produce HTML. We need to ensure we don't include any markdown fences. Let's craft:

    About the role

    Ascendion is an AI-native software engineering disruptor helping businesses innovate faster, smarter, and with greater impact. We partner with enterprise clients across North America, the UK, Europe, and APAC to solve complex challenges in data, experience design, software product engineering, and workforce transformation. Powered by expert engineers, thousands of AI agents, and our Engineering to the Power of AI (EngineeringAI) method, we deliver measurable outcomes that build trust, unlock value, and accelerate growth. We have a culture built on opportunity, inclusion, and a spirit of partnership. Come, change the world with us: build the coolest tech for the world’s leading brands, solve complex problems and learn new skills, experience the power of transforming digital engineering for Fortune 500 clients, master your craft with leading training programs and hands‑on experience, and join a community of change‑makers.

    Responsibilities

    • Manage deliverables to completion for a United States Food and Drug Administration (FDA)-approved Hearing Correction feature, classified as Software as a Medical Device (SaMD), in accordance with the Quality Management System (QMS) software release process end-to-end, including defining release scope, schedules, and milestones.
    • Maintain a single source of truth for release status, dependencies, risks, and open items across all functions.
    • Coordinate release activities across Program Management (scope/prioritization), Engineering (build/development), Software Quality Assurance (QA), Bench Verification and Validation (V&V) (test coverage, verification, and validation evidence), Risk Management (hazard analysis, risk-benefit assessment), Design Assurance (design controls, Design History File (DHF) completeness), Regulatory (submission impact and change assessment), Post-Market Support (field readiness and complaint handling), and Cybersecurity (vulnerability management and Software Bill of Materials (SBOM)).
    • Resolve cross-team dependencies, blockers, and conflicts; escalate decisively when timelines or quality are at risk.
    • Ensure release activities and documentation comply with the Quality Management System (QMS) and applicable standards, including ISO 13485, IEC 62304, ISO 14971, United States Food and Drug Administration (FDA) premarket and postmarket cybersecurity expectations, and IEC 81001-5-1.
    • Ensure medical device files, verification and validation records, risk files, and change control records are driven to completion and are audit-ready before release by the responsible functions.
    • Manage the software change control process, ensuring impact assessments and regulatory change assessments are completed by the responsible functions, including Regulatory and Design Assurance.
    • Track and communicate release risks, mitigations, and residual risk acceptance with the appropriate approvers.
    • Provide clear and timely status reporting to leadership and stakeholders.
    • Drive continuous improvement of the release process, tooling, and metrics, including release approval time, on-time milestone rate, and audit finding closure rate.

    Qualifications

    • Minimum: Must have directly supported or led software programs governed by medical device regulation.
    • Preferred: Established new release processes from scratch. Potential previous employers include Apple, Verily/Google, Samsung.