Technical Program Manager, Software Modernization & Gen AI Enablement

About the role

The Advanced Technical Leader leads projects and initiatives with broad scope and high impact to the business or is a recognized expert in a specialized field. The Technical Program Manager, Software Modernization & AI Enablement drives execution of the software organization’s long-term technical health — modularization, tech debt reduction, tooling, and release governance — partnering closely with architects to turn technical direction into concrete, resourced programs. This position also leads the organization’s Generative AI enablement effort, driving adoption of AI-powered tools and workflows across all the software development poles. The Software leads own delivery of individual programs (schedule, dependencies, releases); this role owns the standards, tooling, and structural roadmap that all programs run on and improve against over time. The role operates within a regulated medical device software environment and partners closely with Quality and Regulatory functions to ensure process rigor is maintained as the organization modernizes.

Responsibilities

• Partner with architects to translate technology direction (modularization, platform consolidation, tech debt reduction) into a structured, resourced program with milestones and owners.
• Own the long-term technical roadmap independent of feature/release cycles — the work that competes for attention against feature delivery.
• Build and maintain visibility into tech debt: inventory it, prioritize it with architects and software leads, and track burn-down over time.
• Identify where architectural intent isn’t translating into practice, and course-correct through structured execution rather than direct authority.
• Own the organization’s software development tooling strategy (ALM, CI/CD, code review, defect tracking), ensuring consistency and fitness-for-purpose across all four regions.
• Evaluate, select, and roll out tooling changes with minimal disruption to active programs.
• Own core software development process definitions and drive their consistent, low-friction application across regions.
• Own global standardization of the merge and release process, including Merge Committee structure, cadence, and decision rights.
• Define and maintain release governance: what needs sign-off, by whom, and at what stage, balancing rigor with delivery speed.
• Monitor the software organization’s adherence to and outcomes from the org-wide Ready-for-Verification (RFV) process, using Software Problem Report (SPR) trends found during formal verification as a