Search by job, company or skills

Technical Product Manager Claims Platforms

Technical Product Manager Claims Platforms

Chubb
12-15 Years
Not Disclosed
  • Posted 30 minutes ago
  • Be among the first 10 applicants

Job Description

Purpose

The Technical Product Manager (TPM) for Claims Platforms is a leadership role within COG Claims. Unlike a traditional business PM, this role sits firmly at the intersection of product thinking and platform architecture — owning the capability and data landscape across all COG platforms and owning the business intent, engineering execution, and architectural integrity.

The TPM is a key partner to the Principal Engineer in the ongoing simplification, scalability, and resilience programme across COG platforms. All Platform Business Analysts report into this role, positioning the TPM as the single source of truth for requirements, capability decisions, and cross-platform product coherence.

Responsibilities

1. End-to-End Transaction Flow Ownership

  • Own and maintain the authoritative map of claims transaction flows end-to-end across all COG platforms.
  • Identify friction points, redundancies, and failure modes in transaction paths, and drive their resolution.
  • Ensure transaction flow design decisions are aligned to simplification and resilience goals.

2. Data Flow & Data Residency Governance

  • Define and govern where data should reside across the claims platform landscape — which system of record owns which data entity.
  • Prevent data duplication and fragmentation by enforcing clear data ownership boundaries.
  • Collaborate with architects and engineering leads to align data flow designs to privacy, compliance, and performance requirements.

3. Capability Architecture & Layer Governance

  • For every capability under consideration, answer the critical question: which layer should own it — and equally, which layer must not own it.
  • Prevent capability creep across platform boundaries (e.g., business logic leaking into integration layers, UI logic embedded in backend services).
  • Maintain and evolve a capability registry that maps features and functions to their correct architectural home.
  • Work closely with the Principal Engineer to enforce layering principles as platforms are simplified and re-platformed.

4. Technical Depth & Build Understanding

  • Bring sufficient technical literacy to understand how capabilities are built — API design, integration patterns, event-driven flows, data contracts, and platform dependencies.
  • Actively engage in design reviews and sprint ceremonies to ensure product intent is correctly translated into technical solutions.
  • Challenge and interrogate technical approaches where they introduce unnecessary complexity or violate architectural principles.

5. Platform Simplification & Resilience Partnership

  • Serve as the product-side partner to the Principal Engineer in the platform rationalisation and simplification programme.
  • Identify capability overlaps, redundant integrations, and platform sprawl across the in scope platforms (from engagement layer to systems of processing).
  • Own the product roadmap for capability consolidation, decommissioning, and migration — balancing delivery continuity with long-term architectural health.

6. Business Analyst Leadership

  • Line manage and develop all Platform Business Analysts across COG, setting standards for requirements quality, discovery rigour, and technical alignment.
  • Establish consistent BA practices — user story structure, acceptance criteria, data mapping conventions, and integration documentation standards.
  • Act as escalation point and decision-maker for requirements conflicts across platforms.

7. Stakeholder Engagement & Backlog Management

  • Own and prioritise the cross-platform product backlog in alignment with engineering capacity, business value, and architectural direction.
  • Translate business requirements into technically precise, unambiguous specifications.
  • Engage with business stakeholders, operations, and external product teams to represent the COG platform capability roadmap.

Qualifications

Experience

  • 12 – 15 years of experience in defining, managing platform capabilities with 3+ years of experience of leading capability definition, defining roadmaps, managing scope and prioritization and leading delivery from a product perspective
  • Demonstrated experience across
  • working with multiple platforms
  • distributed teams present in different time-zones
  • leading a team of BA's, junior product owners while working on a platform

Technical Foundations

  • Good understanding of integration architecture patterns — APIs (REST/SOAP/event), message brokers, ESBs, and data pipelines.
  • Ability to read and interrogate technical artefacts: sequence diagrams, data flow diagrams, API contracts, ERDs, and architecture decision records.
  • Experience with cloud-native platforms (Azure/AWS/GCP), containerised environments (AKS/Kubernetes), and CI/CD pipelines.
  • Strong understanding of insurance or financial services claims processing systems is mandatory.

Product & Analysis

  • Proven experience as a Technical Product Owner, Lead BA, or Product Architect in a complex, multi-platform environment.
  • Strong capability model thinking — able to reason about system boundaries, separation of concerns, and where functionality should and should not live.
  • Experience owning cross-platform backlogs with competing priorities and stakeholder groups.
  • Demonstrated ability to translate ambiguous business needs into technically actionable specifications.

Leadership & Influence

  • Experience managing or leading Business Analysts in a platform or product organisation.
  • Comfortable operating in a senior engineering-led environment — able to hold a position on product and architecture decisions, and negotiate effectively with technical leads.
  • Strong communication and facilitation skills — able to bridge between engineering, architecture, operations, and business stakeholders without losing technical precision.

Tools

  • Extensive Experience using JIRA as a tool for product capabilities management – from defining epics, user story, managing dependencies and the end to end capability lifecycle management. Cloud version experience preferred
  • Extensive experience using confluence and other related tools for documentation
  • Hands on experience using Claude as an agent to support in the capability management – from connecting to repos, analysing code information, setting context and building out PRD's, able to help consistency in driving BA output

More Info

Job Type:
Industry:
Employment Type:

Key Skills

ESBs

data pipelines

event message brokers

AKS

CI/CD pipelines

containerised environments

integration architecture patterns

cloud-native platforms

About Company