Lead Analyst, Master Data Management (MDM)

The Lead MDM Analyst supports the analysis, validation, and documentation activities required to ensure that data flowing from MDM 360 (Customer 360 / Reference 360) into downstream systems is accurate, consistent, and fit for purpose.

This is an analyst not a developer — role. Rather than building pipelines or writing production code, the Junior MDM Analyst interprets data flows, documents findings, validates data quality, supports requirements gathering, and assists with UAT and reconciliation reviews across consumption and reporting workstreams.

This role is an excellent entry point into MDM programme delivery, offering exposure to:

MDM 360 APIs / Batch Snowflake Financial Reporting UI Consumption

Key Responsibilities

1. MDM Data Understanding & Documentation

• Develop a working understanding of MDM golden record structures and how data flows from MDM 360 to downstream systems
• Document data flows, field mappings, and transformation logic under the guidance of the P4 Analyst or BA Lead
• Maintain and update data mapping registers, attribute lists, and business rule logs as requirements evolve
• Assist in maintaining the MDM data dictionary — recording field definitions, data types, and ownership
• Note and escalate data anomalies or gaps in documentation identified during analysis activities

2. Data Validation & Quality Checking

Supporting validation across the consumption data flow — from MDM through to reporting:

• Run and review data validation checks across:

• MDM golden records vs. API payload outputs

• Batch pipeline outputs vs. expected source data

• Snowflake consumption layer vs. MDM source records

• UI-displayed data vs. MDM and Snowflake outputs

• Use SQL (with guidance) to query datasets, identify discrepancies, and validate attribute-level accuracy

• Apply data quality checks across key dimensions — completeness, accuracy, consistency — and document outcomes

• Log and track data quality issues in agreed tooling (e.g. JIRA, SharePoint, Excel trackers)

• Escalate unresolved or high-impact data discrepancies to the P4 Analyst or BA Lead promptly

3. Downstream Reporting & Financial Data Support

• Support validation of MDM data used in financial and regulatory reporting layers

• Assist in reconciliation activities between:

• MDM golden records and Snowflake reporting datasets

• Reporting outputs and expected business values for key financial attributes and hierarchies

• Document reconciliation results clearly — noting matched records, mismatches, and volumes

• Assist in investigating data breaks and reporting discrepancies by gathering relevant data and preparing findings for P4 review

• Track and follow up on outstanding reconciliation items through to resolution

4. Requirements Support & Analysis Documentation

Supporting the P4 BA in translating business needs into clear, documented requirements:

• Attend requirements workshops, take structured notes, and circulate agreed actions and decisions
• Assist in drafting user stories, acceptance criteria, and data mapping specifications under senior guidance
• Review and cross-check requirements documents for completeness, consistency, and alignment with MDM data standards
• Maintain up-to-date requirements logs and traceability matrices for the consumption workstream
• Raise questions and clarification points with the P4 Analyst when requirements are unclear or ambiguous

5. API & Batch Pipeline Validation Support

From an analysis — not development — standpoint:

• Review API payload structures (JSON) and validate that field mappings match agreed data specifications
• Use API testing tools (Postman, Swagger) under guidance to inspect responses and document findings
• Monitor batch job outcomes and validate data completeness and successful execution against expected results
• Log pipeline validation findings and assist in drafting defect descriptions for technical teams
• Track open pipeline issues through to resolution, providing status updates to the P4 lead

6. UAT Support & Defect Tracking

• Support UAT activities across API, batch, Snowflake, and reporting validation scenarios
• Execute test cases defined by the P4 Analyst or BA Lead — validate data movement accuracy and business rule adherence
• Log defects clearly and completely in agreed defect tracking tools — including steps to reproduce, observed vs. expected results, and data evidence
• Track defects through to resolution and retest fixes as required
• Assist in preparing UAT summary notes and test evidence for sign-off activities

Required Skills & Experience

Analytical Skills

• Strong attention to detail — able to spot discrepancies in data across multiple systems
• Structured thinking and ability to organise findings clearly in written form
• Comfortable working with large datasets and identifying patterns, gaps, or anomalies
• Ability to ask the right questions and escalate issues appropriately

Data & Technical Acumen

• Intermediate SQL — able to write and run queries for data validation, comparison, and reconciliation (joins, filters, aggregations)
• Familiarity to some expertise in API concepts (REST/JSON) — able to read and interpret payloads with guidance
• Basic exposure to Snowflake or similar cloud data platforms (querying and exploring data)
• Understanding of data quality concepts — completeness, accuracy, consistency, and timeliness
• Comfortable using tools such as Excel, JIRA, Confluence, Postman, or Swagger for analysis and tracking tasks

MDM & Data Knowledge

• Basic understanding of Master Data Management concepts — what MDM is, why golden records matter, and how data flows between systems
• Awareness of how downstream systems (Snowflake, reporting tools, UI applications) consume MDM data
• Exposure to Informatica Customer 360 / Reference 360 is a plus, but not required

Soft Skills

• Proactive learner — eager to build MDM and data analysis knowledge on the job
• Clear written communication — able to document findings, defects, and notes in a structured, readable format
• Reliable and organised — able to manage assigned tasks, track progress, and meet deadlines
• Collaborative team player — works effectively in an offshore delivery model with onsite and P4 colleagues
• Comfortable asking for help and working under senior guidance without needing full autonomy

Preferred Qualifications

• Bachelor's degree in Business, Information Systems, Data Analytics, or a related field with 7-10 years experience
• Exposure to banking or financial services data environments
• Familiarity with Agile delivery — experience attending stand-ups, sprint reviews, or retrospectives
• Exposure to data reconciliation tasks in a reporting or analytics context
• Interest in or awareness of data governance, data cataloguing, or MDM frameworks

What Good Looks Like in This Role

Activity

Junior Analyst Does

Escalates To P4 When...

Data validation

Runs checks, logs results, flags mismatches

Root cause is unclear or impact is high

Reconciliation

Executes reconciliation steps, documents findings

Unexplained volume differences or systemic breaks

Requirements

Takes notes, drafts user stories, checks completeness

Conflicting requirements or scope ambiguity

Defect logging

Logs full defect detail, retests fixes

Defect is disputed or requires architectural decision

UAT

Executes test cases, logs results

Business sign-off decisions or critical failures

SQL queries

Writes and runs validation queries with guidance

Complex multi-system queries or performance issues

Key Success Measures

• Accuracy and completeness of data validation outputs and reconciliation documentation
• Quality of defect logs — clear, reproducible, and fully evidenced
• Timely escalation of data issues and discrepancies to P4 leads
• Reliable completion of assigned UAT test cases within sprint or release timelines
• Growing confidence and independence in SQL-based validation and data analysis tasks over time
• Positive feedback from Senior Leads on quality of support and documentation

Role Positioning at a Glance

Primary Focus:

Data validation, reconciliation support, and requirements documentation across MDM consumption workstreams

Analyst — Not Developer:

Interprets, documents, and validates data flows — does not build pipelines or write production code

Key Strength:

Attention to detail + growing MDM data knowledge + structured documentation and communication

Supports:

P4 Senior MDM Analyst and Product Lead across all consumption and reporting workstreams