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 (63;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:
Bachelors Degree
At least 6 years of experience in software engineering (Internship experience does not apply)
At least 1 year experience with cloud computing (AWS, Microsoft Azure, Google Cloud)
Preferred Qualifications:
Masters Degree
9+ years of experience in at least one of the following: JavaScript, Java, TypeScript, SQL, Python, or Go
4+ years of experience with AWS, GCP, Microsoft Azure, or another cloud service
4+ years of experience in open source frameworks
1+ years of people management experience
2+ years of experience in Agile practices
Capital One will consider sponsoring a new qualified applicant for employment authorization for this position.
The minimum and maximum full-time annual salaries for this role are listed below, by location. Please note that this salary information is solely for candidates hired to perform work within one of these locations, and refers to the amount Capital One is willing to pay at the time of this posting. Salaries for part-time roles will be prorated based upon the agreed upon number of hours to be regularly worked.
Remote (Regardless of Location): $209,000 - $238,500 for Sr. Lead Software EngineerMcLean, VA: $229,900 - $262,400 for Sr. Lead Software Engineer
Candidates hired to work in other locations will be subject to the pay range associated with that location, and the actual annualized salary amount offered to any candidate at the time of hire will be reflected solely in the candidates offer letter.
This role is also eligible to earn performance based incentive compensation, which may include cash bonus(es) and/or long term incentives (LTI). Incentives could be discretionary or non discretionary depending on the plan.
Capital One offers a comprehensive, competitive, and inclusive set of health, financial and other benefits that support your total well-being. Learn more at theCapital One Careers website. Eligibility varies based on full or part-time status, exempt or non-exempt status, and management level.
This role is expected to accept applications for a minimum of 5 business days.