Master Data Management; MDM) Lead

Master Data Management (MDM) Lead By clicking “Accept Cookies”, you agree to the storing of cookies and similar technologies on your device for functional, third-party analytics, and advertising purposes. Use of this Website confirms your acceptance of our Terms of Use. To view more details, please refer to our
* privacy policy*.### Master Data Management (MDM) Lead Apply:
Lincoln, NE:
Centennial, CO:
Full time:
Posted Today:
R23181

Nelnet Business Services (NBS), a division of Nelnet, Inc., provides payment technology and education services to more than 1,200 higher education institutions, nearly 12,000 K-12 schools, and millions of individual students, families, and supporters across the globe. Our culture of service enables us to form long-lasting and trusted partnerships, while our focus on creativity and innovative solutions empowers our customer communities to thrive.

The Master Data Management (MDM) Lead owns the definition of customer, institution, and payment identity  across Nelnet Business Services systems, including CRM platforms, enterprise payment and enrollment systems,  and the Snowflake data platform. The role authors the match rules, thresholds, and survivorship logic that  determine which record is authoritative when systems disagree, owns the canonical identifier architecture those  rules produce, and independently validates that production pipelines enforce the standard as written.

It sits  within Data Governance and remains independent of the teams that build and operate the pipelines, preserving  the separation between defining what “correct” means and executing against it, while working daily alongside  data engineering, system owners, and implementation partners through CRM migration and consolidation  efforts.

The Master Data Management (MDM) Lead owns the definition of customer, institution, and payment identity across Nelnet Business Services systems, including CRM platforms, enterprise payment and enrollment systems, and the Snowflake data platform. The role authors the match rules, thresholds, and survivorship logic that determine which record is authoritative when systems disagree, owns the canonical identifier architecture those rules produce, and independently validates that production pipelines enforce the standard as written.

It sits within Data Governance and remains independent of the teams that build and operate the pipelines, preserving the separation between defining what “correct” means and executing against it, while working daily alongside data engineering and system owners.

JOB RESPONSIBILITIES:

• Author, document, and maintain the match rules, thresholds, and survivorship logic that define golden records for customer, institution, and payment identity across NBS systems.
• Own the canonical identifier architecture, including canonical institution and customer IDs, and define where those identifiers are assigned, stored, and enforced across the system landscape.
• Establish formal entity resolution between business unit CRM records, replacing informal name and tax  with documented, repeatable, business-approved match logic.
• Define system of record and ownership rules for master data attributes, and adjudicate conflicts where multiple systems claim authority over the same entity or field.
• Partner with data engineering to translate the match rulebook into production pipelines, and independently validate that pipeline output conforms to the approved standard.
• Establish match quality thresholds and monitoring, including false positive and false negative review, and define manual stewardship workflows for records that cannot be resolved automatically.
• Direct remediation of duplicate, conflicting, and orphaned master records at production…