Associate Distinguished Engineer - Senior Data Leader

Nagarro•New York City, NY

11d•Hybrid

About The Position

We are looking for a senior data leader who has built enterprise data platforms, master data management and semantic layers at real scale — more than once — and who can sit across the table from client data leadership as a thinking partner in the morning and be in the modelling detail with the delivery team that afternoon. This is not an advisory role with a delivery team attached. It is a hands-on leadership role with a seat at the strategy table.

Requirements

15+ years in data, with the last several in senior architecture or data leadership roles.
At least two MDM programs taken to production, with genuine accountability for match, merge and survivorship decisions.
At least three enterprise data platform builds delivered end to end at large, complex organizations.
Demonstrable experience designing and landing a semantic layer or shared business ontology that survived contact with more than one business unit.
Experience in environments where data arrived through acquisition and accretion rather than design.
Deep, current, hands-on depth in Cloud Data Platform Snowflake (architecture, performance, cost, governance, data sharing).
Experience with MDM Reltio in production, or equivalent enterprise MDM (Informatica, Stibo, Tamr).
Experience with Governance & Catalog Collibra (catalog, lineage, policy, workflow).
Experience with Data Quality tools like Soda, Great Expectations, implemented as enforced controls in the pipeline.
Hands-on experience with both Cloud AWS and Google Cloud.
Experience with Dimensional and data-vault modelling.
Experience with dbt.
Experience with Orchestration, Streaming and batch processing.

Nice To Haves

Experience retiring legacy systems (e.g., legacy warehouse, duplicate MDM stack, reporting layer).
Ability to explain how organizational agreement was reached for system retirement.
Ability to explain the difference between a data catalog and a semantic layer to a CFO in terms of business impact.
Experience turning down or deferring use cases due to data readiness and being proven correct.
Ability to articulate why second domain, market, or use case was meaningfully faster than the first.

Responsibilities

Build enterprise data platforms, master data management, and semantic layers at scale.
Act as a thinking partner to client data leadership.
Engage in modeling details with the delivery team.
Take a hands-on leadership role with a seat at the strategy table.
Make the case for foundation work to executive stakeholders and hold that sequencing when the pressure is to jump straight to use cases.
Manage data environments where data arrived through acquisition and accretion rather than design.
Drive adoption of data governance and catalog tools.
Implement data quality controls in the pipeline.
Make survivorship decisions for entities defined differently by business owners.
Explain the difference between a data catalog and a semantic layer to a CFO in terms of business impact.
Turn down or defer use cases when underlying data is not ready.
Improve the speed of subsequent data projects through lessons learned.