Sr Manager IC, Merchant & Advertiser Data Marts — Analytics Team (Remote-Eligibl
Sr Manager IC, Merchant & Advertiser Data Marts — Analytics Team (Remote-Eligible) The role
Own the platform substrate behind Capital One Shopping's merchant and advertiser data — the marts that power Retail Media, advertiser reporting, revenue attribution, and every marketing measurement in the business. You set the standards (reference architecture, catalog, access policy, GDPR/audit guarantees) that downstream product teams build on. This is an own-and-build role, not a maintenance seat: you own and operate these marts in production, and in your first six months you ship three net-new systems. You'll report to the Engineering Director for the Shopping data platform as one of two senior IC pillars of the analytics org.
What you'll build
-
A data mart catalog + query-pattern analysis — a single source of truth covering every production mart (owner, SLO, lineage, PII classification, audit trail), plus a Trino-log analysis that shows which raw tables need a mart next. Extends the existing Dataset Registration Scanner, doesn't fork it.
-
Iceberg standardization on a revenue-attached mart — finish the Hive → Iceberg pattern on one high-value merchant/advertiser mart, with PII-masking parity, GDPR deletion-propagation, and schema-change audit baked into a reusable playbook other teams can follow. Bounded standardization, not an open-ended migration.
-
A marts-first access policy, enforced — draft and land a policy that steers consumers off raw event tables when a mart exists, enforced on three high-traffic raw schemas via Trino permissions + CloudSentry, with a full auditable exception log.
The stack
Lakehouse on Iceberg (with legacy Hive tables mid-standardization), dbt at multi-repo scale, Trino/Presto and Spark SQL, Airflow orchestration, Kafka/MSK streaming upstream, on AWS. Data catalog tooling (Amundsen, DataHub, Collibra, OpenMetadata, or home-grown equivalents). GDPR/CCPA governance mechanics throughout.
The day-to-day
"Manager" is the level, not the job — this is an individual-contributor role, and you'll spend most of your day writing migration code and dbt models, not managing a team. Roughly 65% building: writing the Hive → Iceberg migration and its parity tests, coding catalog lineage / PII-classification / audit capture, authoring dbt models and Airflow DAGs, and implementing access enforcement as Trino + CloudSentry policy-as-code. The other ~35% is technical coordination — the weekly Sales / BizOps / Analytics cadence and the PII/access decisions — because governance is cross-functional by nature. The policy work is code and config, not a PDF. You also carry ongoing production support and an on-call rotation for the existing and future marts on this surface — you own what you build, in production. No direct reports — you build.
What we're looking for
-
10+ years engineering experience, 5+ years building shared data platforms / lakehouse infrastructure
-
Hands-on experience leading a Hive → Iceberg (or analogous lakehouse) migration at scale on a revenue-attached system
-
A track record of setting standards that multiple product teams actually adopted (≥3 teams)
-
Experience building or extending a data catalog used across teams
-
Data-access governance under a regulated framework — GDPR/CCPA, SOX, or equivalent — with specific PII-classification, deletion-propagation, or audit-trail work you owned end-to-end
-
A track record of shifting consumers off raw event tables onto curated marts
-
At least one prior role in a regulated data environment (financial services, healthcare, or equivalent)
-
Prior merchant, advertiser, or retail-media data experience (or an analogous B2B customer-facing data product) — strong plus
-
Cross-functional fluency — a hard requirement; weekly cadence with Sales, BizOps, and Analytics, translating business needs into platform work and back
-
Claude Code fluency — daily use, skill authoring, PR-level deliverables (hard requirement)
Basic Qualifications: