Associate Distinguished Engineer - Senior Data Leader

Nagarro•New York, NY

12d•$190,000 - $240,000•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 — multi-business-unit, multi-region, heterogeneous source estates.
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 experience with Snowflake (architecture, performance, cost, governance, data sharing).
Deep, current, hands-on experience with Reltio in production, or equivalent enterprise MDM (Informatica, Stibo, Tamr) with a clear view on where Reltio fits.
Deep, current, hands-on experience with Collibra (catalog, lineage, policy, workflow, and how to drive adoption rather than shelfware).
Deep, current, hands-on experience with Soda, Great Expectations or equivalent, implemented as enforced controls in the pipeline.
Hands-on experience with both AWS and Google Cloud, with a view on when each is the right answer.
Experience with dimensional and data-vault modelling.
Experience with dbt.
Experience with streaming and batch orchestration.

Nice To Haves

Ability to explain how you got an organization to agree to retire a legacy system.
Ability to explain the difference between a data catalog and a semantic layer to a CFO.
Experience turning down or deferring a use case due to readiness of underlying data.
Ability to explain why a 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.
Drive adoption of data governance tools and processes.
Make the case for foundation work to executive stakeholders and hold that sequencing when the pressure is to jump straight to use cases.
Retire legacy systems (e.g., legacy warehouses, duplicate MDM stacks, reporting layers).
Land survivorship decisions when different business owners define the same entity differently.
Explain the difference between a data catalog and a semantic layer to a CFO in terms of what each one changes about their week.
Turn down or defer a use case because the underlying data was not ready.
Ensure subsequent domain, market, or use case implementations are meaningfully faster than the first.