Senior Product Manager - ADI Platform, Developer Experience & Entity Master

ADI is a micro front-end (MFE) architecture: a common shell (authentication, navigation, notifications, search, component library, home and admin pages) into which independent squads — Investor, Payments, Fund of Funds, Reporting and others — plug their surfaces. GMDM sits beneath all of them: it is the single canonical source of truth for Clients, Investors, Funds, Vendors and related parties across the entire enterprise — the foundation without which no squad can correctly identify, secure, or display its data.

You are not building features for end users directly — you are building the products that enable every other product team. Your customers are internal squads and their engineers, and your success is measured by their velocity, consistency, and ability to ship. At the same time, you own capabilities that are end-user facing and mission-critical: authentication and access control, the home experience, notifications, universal search, the shared component library, and the Entity Master admin experience. You must hold both platforms to the same rigour as any customer-facing product — with performance, availability, security, data quality and developer experience treated as first-class requirements.

You will work hands-on: authoring executable PRDs, building the first prototypes yourself, and partnering tightly with engineering, architecture, and the other product managers across the ADI programme.

YOUR RESPONSIBILITIES

Platform vision, strategy & roadmap

• Own the vision, strategy and roadmap for the ADI Platform — the MFE shell, authentication and authorisation layer, shared component library, notifications engine, universal search, and all cross-cutting platform capabilities.

• Define and maintain a clear boundary between what the Platform owns and what belongs to feature squads — resolving ambiguity at pace and with authority, so no squad is ever blocked by an unclear ownership question.

• Prioritise the platform backlog against squad-enablement velocity, non-functional requirements, technical debt, and programme-level delivery commitments.

• Act as the product authority for the platform, making the decisions that trade off between feature-squad needs and platform coherence.

Developer experience & internal product

• Treat the other ADI squads as your primary customers — understand their dependency needs, pain points and roadmap commitments, and design the platform to enable them rather than constrain them.

• Own the golden-path developer experience: template projects, the shared NPM component library (Photon), CI/CD patterns, MFE composition standards, and deployment infrastructure — ensuring every squad has a well-lit path to building and shipping.

• Establish and govern the standards and contracts between the platform and squad microsites — import maps, API standards, component versioning, and token enrichment — so the platform can evolve without breaking consumers.

• Work alongside the other product managers to help their teams onboard to, and correctly consume, platform capabilities.

Authentication, authorisation & multi-tenancy

• Own the end-to-end authentication and authorisation product: integration with CIAM and GSP, role-based access control (RBAC), UI component-level authorisation patterns, token enrichment, and the multi-tenancy and client-isolation model.

• Define the access model clearly — who can see what, in which context, for which client or fund — and ensure it is implemented consistently across every squad’s surface.

• Own org context switching, user account management (/account), and the admin experience (/admin).

Core platform experiences

• Own the ADI home page — including the customisable widget framework (calendar views, user-based preferences) — and ensure it serves as a coherent, high-value landing experience for all user personas.

• Own universal search across ADI — defining scope, relevance, and the integration model with squad-specific content — in alignment with the AI-unified search strategy.

• Own the notifications engine — defining the notification taxonomy, routing logic, SLA and priority model, and the interfaces through which feature squads publish notifications — and partner with the squads (e.g. Fund of Funds, Payments) who consume it.

• Own the cross-team calendar service, the feature-flagging framework, and user-analytics instrumentation.

Global Master Data Management (GMDM) / Entity Master

• Own the product vision, roadmap and backlog for GMDM — ADI's single mastered entity layer covering Clients, Investors, Fund Structures, Vendors and related parties, each with a unique enterprise ID, cross-reference registry, relationship model, and full audit trail.

• Define what GMDM must expose to each consuming squad — the canonical data contracts, API interfaces, field ownership model, and change-event choreography — and ensure every squad can consume entity data without building their own shadow copies.

• Own the boundary between GMDM (enterprise identity and organisational mastering) and GSP (resource-level authorisation) — resolving the integration model with the Platform squad and ensuring tenant isolation and security are production-grade.

• Own the Entity Master admin experience — the UI through which data stewards and operations teams create, manage, merge, soft-delete and audit entity records — and drive adoption of clean, governed data entry practices across the business.

• Act as the product interface between GMDM and the 10+ squads that depend on it (Investor, Payments, Fund of Funds, Waterfall, Private Credit, Reporting, I3C and others) — managing their inbound requirements, triaging competing demands, and making clear prioritisation decisions so the squad is not swamped by reactive asks.

• Partner with operations, client delivery and data stewardship teams to ensure production entity data is owned, populated and maintained — closing the gap between a live API and an empty or brittle data set.

• Own the data quality and governance model for entity master data: field-level ownership, source-system ingestion pipelines (Salesforce, Fenergo, SAP, Investran, eFront), and the cross-reference and deduplication standards that underpin every downstream squad's data reliability.

Non-functional requirements & operational readiness

• Own platform-level non-functional requirements — performance, availability, scalability, security (including penetration testing), accessibility and observability — as first-class product requirements, not afterthoughts.

• Define the platform’s SLAs and the squad contracts that rely on them; ensure monitoring, logging, error handling, alerting and rollback capability are production-grade from day one.

• Own the global and regional deployment and caching strategy, and the CI/CD framework that all squads depend on.

Building AI-Native — how we work

• Author Executable PRDs (xPRDs) — structured context repositories that combine natural-language intent, machine-actionable specification, complete business and technical context, edge cases, success metrics and acceptance criteria, and embedded governance guardrails.

• Build the first functional prototype yourself during ideation and discovery, using AI tooling to validate desirability (product-market fit with clients) and feasibility (with architects) in parallel — then hand a high-fidelity, context-rich prototype to engineering to curate and take to production quality.

• Own the non-functional requirements — performance, availability, scalability, security and accessibility — from day one, treating them as first-class product requirements rather than an afterthought.

• Work within an enhanced design-thinking approach with governance embedded from day one — ethical AI and user rights, privacy, security, risk and compliance, and audit/traceability — alongside explicit attention to data readiness (maturity, availability and quality).

Quality & governance

• Own platform and GMDM quality, reliability and consistency governance — establishing the standards and review processes that prevent squad divergence from platform and data contracts.

• Embed security, privacy, accessibility (WCAG), and auditability into platform and entity master decisions from the outset.

• Own the API standards governance framework across ADI — ensuring consistent, well-documented APIs across squads, aligned to OpenAPI/Swagger standards.

Delivery & cross-functional

• Own platform and GMDM quality, reliability and consistency governance — establishing the standards and review processes that prevent squad divergence from platform and data contracts.

• Embed security, privacy, accessibility (WCAG), and auditability into platform and entity master decisions from the outset.

SKILLS & EXPERIENCE

Essential

• Proven senior product management experience delivering platform, infrastructure, or developer-experience products in a complex, multi-team technology environment — owning products whose primary customers are internal engineering teams.

• Deep understanding of micro front-end (MFE) architecture, front-end platform patterns, component libraries, and API design — sufficient to hold technical discussions with architects and make grounded product decisions.

• Demonstrated experience owning authentication, authorisation and identity products — RBAC, CIAM integration, token-based auth, multi-tenancy — as product capabilities.

• Demonstrated experience owning or working closely with master data management, entity resolution, or data governance products — understanding canonical data models, cross-reference registries, data stewardship and source-system ingestion.

• Demonstrated ability to work AI-native — authoring executable PRDs and building functional prototypes with AI tooling, rather than relying solely on traditional specification and handoff.

• Strong dependency management and cross-squad stakeholder skills — comfortable managing backlogs that must serve many internal customers simultaneously, with competing priorities and high inbound demand.

• Excellent prioritisation, communication and technical communication skills — able to create clarity from ambiguity and translate complex platform and data constraints into decisions squads can act on.

Desirable

• Experience building or scaling a shared component library or design system across a large, multi-team product.

• Familiarity with CI/CD pipelines, cloud infrastructure (AWS), feature flagging, and product-analytics tools (e.g. Heap, Datadog, LaunchDarkly).

• Experience in enterprise B2B, fintech, or financial-services products; alternatives or fund-administration domain a plus.

• Experience in agile, multi-team delivery (Agile Release Train / PI planning).

• Familiarity with WCAG accessibility standards and security-by-design practices.

Personal Attributes

• Systems thinker with a strong instinct for coherence at scale — able to see how platform decisions ripple across every squad and every user experience.

• Highly collaborative and influential with engineering teams, architects, and peer product managers — yet decisive and willing to hold the line on platform standards and contracts.

• Hands-on, fast, and energised by using AI tooling to raise both the speed and quality of product thinking and specification.

• Comfortable with invisible infrastructure — motivated by enabling others to ship great products, even when the platform itself is not visible to end users.

• High standards for operational excellence — takes non-functional requirements and production readiness as seriously as feature delivery.