Sr MDM Engineer (Informatica MDM SaaS)

Experience - 9–14 years total; 5+ years hands-on Informatica MDM, of which a minimum of 2–3 years must be extensive hands-on delivery on IDMC / MDM SaaS

• MDM — Informatica MDM SaaS / Business 360 — business entity models, Business 360 Console, match and survivorship configuration, Hierarchy Manager, Reference 360 
  

• Integration — Cloud Data Integration (CDI), Cloud Application Integration (CAI), Secure Agent runtime, Salesforce / ERP / file / object-store connectors 
  

• Data quality — Cloud Data Quality (CDQ) — rule specifications, profiles, scorecards, cleanse and standardise transformations 
  

• APIs — Business Entity REST APIs, Business 360 ingress/egress services, IDMC platform APIs, OAuth2 / JWT authentication 
  

Role Summary 

Owns the technical design and configuration standards for the product master on Informatica MDM SaaS. Hands-on across business entity modelling, match and survivorship, hierarchy and reference data design, and the API and integration contract with downstream systems. Accountable for the model holding up under production data volumes and for the platform decisions the rest of the build depends on. 

Technical Responsibilities 

• Data model — Design the canonical product model and implement it as business entities, field groups, nested structures and relationships in the Business 360 Console. Define product-to-SKU cardinality, variant modelling, versioning and effective dating. 
  

• Match and merge — Author match models and match rule sets — exact and fuzzy rules, match fields and tokenisation, thresholds and clustering behaviour. Define auto-merge versus manual review boundaries and tune against production-representative data. 
  

• Survivorship — Configure the trust and survivorship framework — source trust scores, decay, field-level survivorship strategies and the resulting golden record behaviour. Define cross-reference and unmerge handling. 
  

• Hierarchies and reference data — Design hierarchy structures and relationship types in Hierarchy Manager; define reference data domains and code value mappings in Reference 360, including dependent and cascading lookup configuration. 
  

• APIs and contracts — Define the Business Entity REST API surface exposed to consumers, including read, write and search patterns, payload contracts, authentication and pagination. Set the ingress and egress design with the integration lead. 
  

• Validation and governance — Specify field-level and cross-field validation, attribute-level security, role and privilege model, and the workflow and stewardship task design. 
  

• Environments and release — Define asset promotion across IDMC environments, export and import strategy, version control of exported metadata, and the regression approach for model changes. 
  

• Extension boundary — Determine where platform configuration ends and custom extension begins; specify any user exits or external service calls and review their implementation. 
  

• Performance — Size and tune batch load, match and publish jobs; define incremental processing and reprocessing strategy. 
  

Mandatory Technical Skills 

• IDMC / MDM SaaS — mandatory — Minimum 2–3 years of extensive, hands-on delivery on Informatica MDM SaaS / Business 360, including business entity modelling and Business 360 Console configuration. This is a hard requirement. On-premise MDM Hub experience does not substitute for it, though it is valuable in addition. 
  

• Implementation track record — Two or more end-to-end MDM implementations, at least one of them on IDMC. 
  

• Match and survivorship — Demonstrable configuration and tuning of match rules and survivorship, with an understanding of how threshold and trust changes propagate to golden records. 
  

• APIs — Working knowledge of Business Entity REST APIs and Business 360 ingress/egress services, including auth and error semantics. 
  

• Data modelling — Able to derive a canonical model from business requirements, not only implement a model handed over. Familiar with packaged accelerator models and their structural implications. 
  

• SQL and data — Strong SQL; able to profile and reason about real data rather than rely on specification. 
  

Preferred Technical Skills 

• Product / PIM domain modelling — taxonomy, offer structures, pricing attributes, product-to-SKU decomposition. 
  

• Product master structures in ERP, CRM and CPQ systems, and their publication patterns. 
  

• Informatica CLAIRE, or AI-assisted matching and stewardship features. 
  

• Java or JavaScript for platform extension points. 
  

• Large-scale migration and remediation — profiling, mapping and cleansing legacy attribute values. 
  

• Informatica MDM certification.