Technical Program Manager, Software Modernization & Gen AI Enablement

Job Description Summary 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.

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 leading indicator of process health, and feed findings back into tooling, process, and modernization priorities.

Ensure release governance is applied consistently across the four regional teams, adapting for regional constraints without fragmenting the standard.

Define and run the organization’s roadmap for adopting GenAI tools in the software lifecycle (coding assistants, code review, documentation, testing). Establish lightweight governance: usage guidelines, security/IP considerations, and success metrics for AI tool adoption - with attention to what’s appropriate in a regulated development environment. Run enablement programs - training, champions network, pilot-to-scale playbooks - tailored to each region. Track adoption and impact (velocity, quality, satisfaction) and report ROI to leadership.

Stay current on the GenAI tooling landscape and pressure-test new tools before wider rollout.

Act as the connective tissue between architects (who set direction), software leads (who run delivery), and regional teams (who execute) - without owning any single team’s delivery schedule. Partner with Quality/Regulatory to keep tooling, process, and release governance changes aligned with applicable software development lifecycle requirements (e.g., IEC 62304, design controls). Translate ambiguous, evolving priorities - both architectural and AI-related - into structured programs with clear…