Lead Semarchy xDM Engineer

If you know the difference between an MD_ and a GD_ row without looking it up, keep reading.

Plenty of people can set up a matcher. We need someone who can explain why it made the decision it did.

Problems you might find yourself working on

• A fuzzy-matched entity is over-merging. Is it the binning expression, a match rule threshold, or an enricher normalizing two different legal entities into the same string upstream of the match?
• A golden record’s survivorship looks right in the stepper, but downstream consumers see something else. Do you trace it through the publisher, the integration job, or the consumer’s own logic?
• An external load completes but fails validations at scale. Do you fix it in the SemQL, in the source, or in the contract between them?
• A party hierarchy built on references needs to survive merges, splits and re-parenting without orphaning accounts that something downstream depends on.
• The model has drifted for years. How do you re-architect entities, rules and integration patterns without stopping the data flowing?

The terrain

• Semarchy xDM:
• modeling (basic, ID-matched and fuzzy-matched entities)
• matchers and consolidation rules
• enrichers and validations
• stewardship apps, workflows and duplicate managers
• load APIs and REST integration
• SQL: profiling, anomaly hunting and root cause, done directly against the SD/MD/GD layers rather than only through the UI
• Pipelines: Snowflake, Azure / ADF, dbt, Fivetran, Python and APIs on both sides of the hub, with production-grade reliability
• Domains: client, party, organization, contact and account data. Salesforce integration and financial services experience carry a lot of weight.

What “lead” means here

You review designs, data models, SQL and code for onshore and offshore engineers, and you’re the person who settles the hard technical call. You can also explain that call clearly to data stewards, product owners and senior technology leaders. You’re interested in using AI to automate data quality work, not just pleased that the hype exists.

Probably not you if:

• your mastering experience is mostly Informatica or Reltio with only light Semarchy, or
• you’ve moved away from the keyboard into architecture, governance or management.

Baseline: 10+ years in data engineering and MDM, with multiple end-to-end xDM implementations in production.

To apply, message me with the hardest match/merge or survivorship problem you’ve solved in xDM and how you solved it. That tells us more than a resume.