Product Manager - AWS Enterprise Imaging

Date:
Oct 1, 2026

Remote, CA

Agfa Health Care , is a division of the Agfa-Gevaert Group which is headquartered in Mortsel, Belgium and traded on Euronext Brussels (AGFB).

At Agfa Health Care, we support healthcare professionals across the globe to transform the delivery of care. Our focus is 100% on providing best-of-suite Imaging IT software solutions that enable secure, effective and sustainable imaging data management.

From product development to implementation, our unified Enterprise Imaging Platform is purpose-built to reduce complexity, improve productivity and deliver clinical value. We use our proven track record as an innovator, our in-depth medical knowledge and our strategic guidance to help healthcare providers achieve their clinical, operational and business strategies.

The Global Product Manager - Platform Deployment & Lifecycle is responsible for defining and delivering the product strategy for packaging, installing, configuring, scaling, upgrading, rolling back, and recovering AGFA Health Care Enterprise Imaging software across public cloud, private cloud, virtualized, and Kubernetes environments.

The role owns the transition from manual, engineer-dependent installation practices to standardized, repeatable, secure, and supportable deployment automation. Working across R&D, Dev Ops, Platform Engineering, Architecture, Security, Service, and Support, the Product Manager translates operational needs into roadmaps, use cases, acceptance criteria, and release guidance for immutable AMI-based virtual machines, Kubernetes and Helm, Git Ops, infrastructure as code, automated validation, and lifecycle governance.

Daily hands-on engineering is not the primary responsibility; however, the role requires sufficient technical depth to understand designs, challenge assumptions, identify dependencies, and make informed product trade-offs.

• Remote:
  North America (Waterloo or Remote)

• Define and own the product vision, strategy, and roadmap for platform deployment, installation, configuration, upgrade, rollback, scaling, and recovery capabilities.
• Prioritise investment based on customer value, operational risk, deployment effort, supportability, security, cost, and strategic alignment.
• Establish standard product patterns that reduce site-specific configurations and support consistent delivery across cloud, virtualized, and Kubernetes-based environments.
• Define clear product boundaries between AGFA-owned deployment capabilities, platform infrastructure, third-party software, and customer-managed responsibilities.
• Maintain a sequenced roadmap that distinguishes minimum viable capability, technical enablers, and validated future expansion.

• Drive the transition from in-place binary installation to immutable, image-based virtual machine replacement using prebuilt Amazon Machine Images and equivalent cloud image patterns.
• Define product requirements for isolating persistent state from compute lifecycle so that virtual machines can be replaced, resized, scaled, redeployed, or rolled back without reinstalling or losing required state.
• Shape Kubernetes deployment capabilities using containers, Helm charts, standard deployment profiles, Git-managed configuration, and Git Ops reconciliation through tools such as Flux or Argo CD.
• Ensure that Terraform, Ansible, image-building pipelines, cloud-init, configuration stores, secrets management, and CI/CD workflows operate as a coherent product lifecycle rather than disconnected engineering tools.
• Define requirements for automated bootstrap, idempotent installation, controlled overrides, version management, health validation, smoke testing, observability registration, and documented recovery.
• Support horizontal scaling and resilient deployment patterns, including auto-scaling groups, rolling replacement, high-availability topologies, and controlled zero- or minimal-downtime upgrade approaches.
• Requirements, Backlog & Delivery Leadership
• Convert strategic outcomes and operational pain points into well-structured epics, use cases, acceptance criteria, non-functional requirements, impact analysis, and definition-of-done expectations.
• Maintain an actionable backlog that balances customer-facing outcomes with platform enablers, automation, technical debt, security, observability, and supportability.
• Work with engineering teams to identify contracts and dependencies between AMIs,…