Senior MDM Engineer

Hike2•Remote, PA

1d•$125,000 - $175,000•Remote

About The Position

HIKE2 is hiring a senior Master Data Management Engineer for its data and integration practice. You will architect and build resolved identity and relationship foundations for financial services clients. Own the end-to-end MDM and relationship-graph architecture on an engagement, from data modeling through integration, data quality, and governance. Design and configure match and merge logic, survivorship and trust rules, validation rules, and golden-record management. Build entity resolution, the golden record, and the graph, along with the pipelines that feed them and syndicate trusted master data back to consuming systems. Establish the data-quality baseline and the survivorship and stewardship operating model, including steward workflows and issue queues. Define the identity seam between the client identity platform and the MDM layer, turning an authenticated claim into a resolved party. Set engineering standards, document a repeatable delivery approach, and mentor and grow a small team. Collaborate with data governance, CRM and source-system owners, and business stakeholders, and translate complex MDM concepts for both technical and non-technical audiences.

Requirements

Strong SQL and proficiency in Python, with Java or .Net as needed to extend MDM platforms and build services.
Hands-on with at least one enterprise MDM platform (Informatica MDM, Reltio, Semarchy, Ataccama, or Profisee) and the judgment to weigh build-lite on the existing stack against a packaged product.
Comfortable with data governance and quality tool (for example Ab Initio or Collibra) and with workflow tooling.
Ten to fifteen years in enterprise data engineering and architecture, with master data management delivered in production, not just designed.
Demonstrated ability to both architect and build, having designed the system and then implemented it, not a design-only background.
Financial services required, private and commercial banking strongly preferred, where a client is at once a person, an entity, a household member, and a borrower, and where party is a regulated, first-class concept.
Proven physical MDM design with a party model, and experience resolving duplicated or unresolved entities upstream in identity.
Familiarity with enterprise identity platforms, including Ping, and how digital identity binds to data identity.
Experience building for audit in a regulated industry, having survived a real audit or examination.
A track record of mentoring or leading a small engineering team, and consulting or client-facing delivery experience.
All applicants must reside in the U.S. and hold US Citizenship to be considered for employment.

Nice To Haves

AI-assisted MDM: intelligent match scoring, automated survivorship suggestions, and anomaly flagging, kept governed, auditable, and validated before promotion to master.
Experience with the systems common to banking estates: core banking (for example Fiserv), CRM (for example Salesforce), loan origination and servicing (for example Broadridge), and client due diligence (for example Fenergo).
Exposure to externalized authorization or relationship-based access control, where the graph supplies context and a decision point applies policy.
Informatica: Professional or Practitioner certification in MDM, MDM SaaS or Cloud, or Informatica Data Quality (IDQ), and related Intelligent Data Management Cloud (IDMC) credentials.
Reltio Certified Professional, for the Reltio Connected Data Platform.
Semarchy xDM certification (Discovery or Practitioner).
Ataccama ONE certification.
Profisee certification, particularly for teams on the Microsoft and Azure stack.
Microsoft Azure: Azure Data Engineer Associate (DP-203) or Azure Solutions Architect Expert, given our Azure-preferred stack.
Databricks or Snowflake certification where the client stacks calls for it.
Neo4j Certified Professional, or an equivalent graph credential, for the relationship graph work.
Data governance or quality credentials such as Collibra Ranger, or the DAMA CDMP (Certified Data Management Professional).
A recognized cloud security or privacy certification is a plus given the regulated setting.

Responsibilities

Own the end-to-end MDM and relationship-graph architecture on an engagement, from data modeling through integration, data quality, and governance.
Design and configure match and merge logic, survivorship and trust rules, validation rules, and golden-record management.
Build entity resolution, the golden record, and the graph, along with the pipelines that feed them and syndicate trusted master data back to consuming systems.
Establish the data-quality baseline and the survivorship and stewardship operating model, including steward workflows and issue queues.
Define the identity seam between the client identity platform and the MDM layer, turning an authenticated claim into a resolved party.
Set engineering standards, document a repeatable delivery approach, and mentor and grow a small team.
Collaborate with data governance, CRM and source-system owners, and business stakeholders, and translate complex MDM concepts for both technical and non-technical audiences.
Design and implement deterministic and probabilistic match logic, configuring match rules, thresholds, and trust scoring, and tuning them over time to balance false merges against missed matches.
Weight strong identifiers such as tax ID and date of birth above shared attributes like name and address, and handle nicknames, transliteration, and address standardization.
Build and maintain crosswalks between each source system's local key and the canonical party identifier.
Design golden, or best, record construction with attribute-level survivorship and trust rules that define which source wins per attribute and why, with full lineage.
Implement merge, unmerge, split handling, and manage record consolidation safely in production.
Establish validation rules and the golden-record lifecycle: create, update, retire.
Model the party domain across person, legal entity, household, and account, with relationships, hierarchies, crosswalks, and reference data.
Design the relationship graph ontology: households, beneficial ownership (UBO) chains, advisor-to-client, entity-to-account, collateral, and exposure, with effective dating so relationships are time-valid.
Define measurable data-quality metrics and the minimum required attributes for each domain.
Build automated data profiling and a measured baseline for completeness, accuracy, consistency, and duplication.
Implement data-quality rules, validation logic, and exception handling, and design steward workflows, issue queues, and dashboards that make stewardship efficient.
Partner with governance to define master data policies, standards, and the stewardship operating model, and maintain data dictionaries per domain.
Design inbound and outbound integration patterns to ingest source data and syndicate trusted master data back to operational, analytical, and reporting systems.
Build ingestion and integration jobs, implement change data capture, and stand-up real-time resolve-and-lookup services with acceptable latency.
Consume an authenticated claim from the identity platform and translate it to a resolved party identifier through the orchestration and integration layer.
Build on a modern cloud data stack, Azure preferred, using the medallion or lakehouse pattern across bronze, silver, and gold.
Manage multiple environments (development, test, QA, production) with performance tuning, monitoring, and cost awareness.
Implement the relationship graph on a property-graph store (Neo4j with Cypher, or Cosmos DB with Gremlin), keyed strictly on the canonical party identifier.
Build graph queries and traversals for multi-hop questions such as UBO chains and advisor-to-borrower authorization, returning explainable, evidenced assertions with effective dates.
Build for audit and regulatory review: full lineage, decision logs, and traceable survivorship.
Apply KYC, AML, and beneficial ownership requirements under the Bank Secrecy Act and USA PATRIOT Act, and handle PII, tokenization, and access controls appropriately.