MDM Architect

CUSTOMER is hiring a Master Data Management Architect in the Data Architecture and Platforms division of the Data Office who will support Customer’s Enterprise Data Management (EDM) and Master Data Management Strategic Programme. Customer are entering a programme on significant transformation and changes with ERP and CRM for which Customer and Product Master Data Management, Quality and Governance is critical to the success of the Transformation.

The role is required to support the ERP and CRM transformation initiatives by defining what is required from the EDM programme, supporting the definition of the EDM roadmap and priorities; supporting the EDM programme define scope, data architecture and solution architecture; and supporting the Data Platform roadmaps for Customer and Product Master Data Enterprise Assets.

Secondary to the enterprise transformation programmes are the significant other master data programmes within our Research & Development business for Ingredients Master Data and expanding markets for Product and Secondary Customers. As CUSTOMER moves towards becoming a truly data centric organisation, this is a high impact and high visibility role that requires strong communication and collaboration skills across numerous business functions that are geographically spread around the world.

Strong master data and architecture experience is required, with experience of large-scale transformation and data migration programmes; ability to engage stakeholders across functions and regions across CUSTOMER and most importantly an enterprise view of Master Data to eliminate functional or siloed thinking.

Key results from this role will see:

• Trusted relationships with the CRM and ERP transformation programmes
• A well-defined roadmap for the EDM programme with correlation to the CRM and ERP transformation.
• An overall improvement to Customer and Product data in Customer, demonstrated by improved trust in the master data
• Roadmap for, and the implementation of new Customer and Product hierarchies
• Customer and Product data is more accessible to systems and users

Responsibilities:

• Define the MDM target architecture across ERP, CRM, and adjacent platforms (data warehouse, data lake/lakehouse, integration layers, governance tools).
• Work with the Enterprise Data Management team to support the definition of the MDM operating model: roles, responsibilities, data ownership (data stewards, custodians, domain owners).
• Data Modelling, Standards and Master Data Design
• Align ERP/CRM data structures to enterprise-wide models.
• Develop and enforce data standards, naming conventions, and attribute definitions.
• Support the design, and maintain hierarchies and relationships
• Document survivorship rules, matching rules, merging rules, and validation constraints.
• Data Governance & Framework Definition
• Define business rules for quality, completeness, enrichment, and lifecycle.
• Partner with governance teams to define data quality KPIs, approval workflows, ownership model & stewardship processes
• Data Migration and Architecture Oversight
• Design the migration approach
• Define migration architecture: staging areas, transformation flows, quality gates.
• Set standards for mapping, transformation logic, de duplication, enrichment, and attribute survivorship.
• Define the migration runbook and cutover process from an MDM perspective.
• Oversee mapping & transformation
• Guide functional teams through mapping legacy to target ERP/CRM schemas.
• Ensure mappings conform to enterprise MDM standards and canonical data models.
• Quality Assurance & Sign‑off
• Define the data quality scorecard for migration.
• Approve cleansing, de duplication, and master data remediations.
• Validate readiness for mock loads, SIT/UAT data, and production cutover loads.
• MDM Solution Design & Tooling
• MDM Architecture for match/merge, master data hubs, workflow & governance, reference data management
• Define integration patterns between MDM, ERP, CRM and other enterprise systems e.g. APIs, event streams, batch interfaces, etc.
• Define semantic consistency across MDM/ERP/CRM and analytical environments
• Maintain version control and impact analysis for MDM schemas
• Stakeholder, Governance and Change Leadership
• Communicate architectural principles to executives, programme managers, solution architects, business stakeholders and MDM teams
• Be active, and potentially lead MDM design authorities and data governance councils

Why you?

Basic Qualifications:

• Master Data Management and experience in either an enterprise ERP or CRM programme experience is essential
• Informatica, and either SAP ECC / S/4, or, Salesforce, are essential.
• Veeva CRM is advantageous
• Strong product and/or customer domain experience
• Data Modelling tool experience is essential, sqlDBMS beneficial
• DAMA-DMBOK, TOGAF qualifications or training is an advantage
• Demonstrable experience in creating and managing an enterprise data architecture over a data platform architecture; and detailing out data flows between systems in the context of the data architecture
• Strong demonstrable experience in data design and modelling from conceptual, logical to physical data models and proficiency is using one or more modelling tools
• Strong problem-solving and analytical skills.
• Ability to work cross-functionally in a fast-paced and rapidly changing work environment.
• Knowledge of agile methodologies and experience in using devops board
• Must be able to successfully manage multiple workstreams simultaneously.
• Ability to engage and communicate effectively across all levels of the organisation.
• Broader understanding of a CPG or Consumer healthcare industry and functional understanding of data from one or more business functions.
• Functional familiarity with one or more key master domains such as product, customer, vendor, finance, people, location; and challenges typically involved in managing an enterprise view of the domain.
• Functional familiarity with one or more key transactional data domains such as sales, consumption, or other transactional data for a business function and the challenges typically involved in managing an enterprise view of the domain.