Data Product Manager

London
2 days ago
Create job alert

Role Overview

The Data Strategy Lead / Data Product Manager is accountable for defining and driving the strategic direction of a specific data domain or capability within corporate banking. Acting as the strategic owner, this role ensures alignment with enterprise architecture, governance frameworks, and business priorities. It serves as a critical bridge between strategy and execution, empowering Agile delivery teams to build scalable, compliant, and high-quality data products that support business operations, regulatory obligations, and analytical needs.

This role operates horizontally across delivery verticals under the ITGPST Data Strategy and Delivery organization, enabling consistent end-to-end data flow design patterns, reducing rework, and embedding modernization opportunities such as cloud migration, AI adoption, and data-as-a-product principles.

Key Responsibilities

  • Domain Strategy & Roadmaps
    Define and maintain the strategic vision for the data domain, addressing current-state challenges, modernization opportunities, and simplification goals. Co-develop roadmaps with delivery teams to balance long-term direction and near-term execution.

  • Portfolio Intake & Discovery
    Evaluate new demand during intake to identify opportunities for strategic execution (e.g., governance, data quality, modernization). Influence scope and design decisions to align with enterprise priorities.

  • Delivery Outcome Tracking
    Monitor delivery outputs against strategic objectives using clear metrics; escalate misalignments and propose corrective actions to ensure predictable delivery.

  • Voice of Customer & Use Case Capture
    Engage with business, regulatory, and operational stakeholders to ensure strategy reflects real-world needs and drives measurable business value.

  • Integration with Enterprise Architects
    Partner with architects to enforce alignment with enterprise blueprints and standardized data design patterns; co-own pattern libraries and governance routines.

  • PI Planning & Inspect & Adapt
    Actively participate in PI Planning and Inspect & Adapt workshops. Incorporate audit learnings, production incident themes, and delivery retrospectives into strategy updates to strengthen governance and improve audit readiness.

  • Data-as-Product Advocacy
    Promote treating data as a product through canonical models, reusable APIs, and shared contracts; collaborate with Agile Product Owners to embed these into team backlogs.

    Primary Skill: Data Strategy & Architecture

    Secondary Skill: Global Payments Business Domain /Financial Services Expertise

    Tertiary Skill: Data Product Management

    Required Skills & Experience

  • Strategic Leadership: Proven ability to define and execute domain-level strategies in complex organizations.

  • Global Payments Expertise: Deep understanding of payment rails, clearing/settlement, cross-border flows, correspondent banking, treasury/payments operations; ISO 20022, SWIFT MT/MX.

  • Regulatory & Reporting Knowledge: PSD2/Open Banking, AML/Sanctions (GFCC), NFRR/FRR reporting controls, audit readiness; data retention/lineage requirements.

  • Data Management Expertise: Canonical data modeling, shared contracts/APIs, event-driven and batch patterns, lineage/metadata, reference/master data, data quality controls.

  • Governance Leadership: Design-pattern stewardship, control frameworks, standards enforcement, policy-to-implementation traceability.

  • Enterprise Alignment: Collaboration with Enterprise Architects; blueprint adherence; PI Planning of strategic enablers (SAFe or similar).

  • Product Management: Roadmap definition, value hypothesis, backlog curation, Epic/Feature acceptance criteria; use-case capture and prioritization for reuse and measurable value.

  • Portfolio Intake & Discovery: Ability to challenge scope for simplification/modernization; dependency and risk management across CDPO verticals.

  • Communication & Stakeholder Management: Executive-level storytelling, cross-functional influence, multi-location collaboration across EMEA and global teams.

  • Experience: Typically 10+ years in data/architecture/product roles, including 5+ years in Payments/Treasury or banking; proven delivery in regulated environments.

    Preferred Qualifications

  • Modern Data Practices: Data mesh/product-based operating models; event streaming (e.g., Kafka); interoperability standards.

  • Cloud & Modernization: Experience guiding migration to modern platforms (e.g., Azure, AWS), data lakes/warehouses, streaming, real-time payments integration.

  • Certifications: SAFe POPM/Architect, CDMP/DAMA, and cloud certifications (Azure/AWS).

  • Understanding of Data Mesh Principles: Domain-oriented data ownership models and federated governance

Related Jobs

View all jobs

Product Manager - Agentic AI (Airline)

Senior Backend Engineer

Data Scientist/AI Engineer

Assistant Director - Digital and Product

Frontend Developer

UI Developer - 13042

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

Cloud Computing Jobs for Career Switchers in Their 30s, 40s & 50s (UK Reality Check)

Thinking about switching into cloud computing in your 30s, 40s or 50s? You aren’t alone. Across the UK, employers are hiring professionals from diverse backgrounds to help organisations adopt, manage & optimise cloud technology. But let’s cut through the buzzwords. This guide gives you a practical, UK-focused reality check on cloud computing careers for career switchers — what roles exist, what you actually need to learn, how long it takes to retrain and, importantly, whether age matters. If you’re exploring a move into cloud computing, this article lays out what’s realistic and how to get there without falling for hype.

How to Write a Cloud Computing Job Ad That Attracts the Right People

Cloud computing underpins much of the UK’s digital economy. From startups and scale-ups to enterprise organisations and the public sector, cloud platforms enable everything from data analytics and AI to cybersecurity, DevOps and digital services. Yet despite high demand for cloud skills, many employers struggle to attract the right candidates. Cloud job adverts are often flooded with unsuitable applications, while experienced cloud engineers, architects and platform specialists quietly pass them by. In most cases, the problem is not the shortage of cloud talent — it is the quality and clarity of the job advert. Cloud professionals are pragmatic, technically experienced and highly selective. A poorly written job ad signals confusion, unrealistic expectations or a lack of cloud maturity. A well-written one signals credibility, good engineering culture and long-term thinking. This guide explains how to write a cloud computing job ad that attracts the right people, improves applicant quality and strengthens your employer brand.

Maths for Cloud Jobs: The Only Topics You Actually Need (& How to Learn Them)

If you are applying for cloud computing jobs in the UK you might have noticed something frustrating: job descriptions rarely ask for “maths” directly yet interviews often drift into capacity, performance, reliability, cost or security trade-offs that are maths in practice. The good news is you do not need degree-level theory to be job-ready. For most roles like Cloud Engineer, DevOps Engineer, Platform Engineer, SRE, Cloud Architect, FinOps Analyst or Cloud Security Engineer you keep coming back to a small set of practical skills: Units, rates & back-of-the-envelope estimation (requests per second, throughput, latency, storage growth) Statistics for reliability & observability (percentiles, error rates, SLOs, error budgets) Capacity planning & queueing intuition (utilisation, saturation, Little’s Law) Cost modelling & optimisation (right-sizing, break-even thinking, cost per transaction) Trade-off reasoning under constraints (performance vs cost vs reliability) This guide explains exactly what to learn plus a 6-week plan & portfolio projects you can publish to prove it.