Back to jobs

Staff Data Engineer

New York City · New York City, New York, United States

Open 3 months, first seen by us 97 days ago
Pay
$237,000–265,000/year · BaseAnnual period assumed — pay source
COMPENSATION $237,000–$265,000 base salary, commensurate with experience. Meaningful equity. Medical, dental and vision. WHERE WE WORK
Read the full posting
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Research & Development › Engineering — team source
Department: Research & Development › Engineering
From the employer’s posting

What you’ll work on

Full posting

We run a multi-tenant transformation platform that unifies a portfolio of customer brands into a single golden data model across Shopify, HubSpot, Klaviyo, Google/Meta Ads and more.

You'll be the technical owner of this part of our broader data platform: the person who designs for the regime we're growing into rather than the one we're in.

  • Design tenant onboarding so adding a tenant is config-and-metadata work, not bespoke engineering

  • Build contracts, audits and CI gates that prove every tenant and model is fully represented

  • Own org-identity and access layer: tenant provisioning, routing, isolation and RBAC

  • Manage schema evolution and versioning of the ontology across hundreds of tenants

  • Build MCP servers, vector search and metrics layers so AI agents can safely query the data

From the employer’s posting
We run a multi-tenant transformation platform that unifies a portfolio of customer brands into a single golden data model across Shopify, HubSpot, Klaviyo, Google/Meta Ads and more.
You'll be the technical owner of this part of our broader data platform: the person who designs for the regime we're growing into rather than the one we're in. The defining question of the role is how to make the cost of the next tenant (and the next data source, the next entity in our ontology, the next golden model) flat instead of linear, while correctness, isolation and freshness hold as the system fans out.
Design the tenant-onboarding model so adding the Nth tenant is a config-and-metadata operation, not bespoke engineering
Build the contracts, audits and CI gates that turn "is every tenant fully represented?" into something the build answers, not a person
Own the org-identity and access layer (tenant provisioning, source-to-tenant routing, multi-tenant isolation and RBAC)
Own how the ontology is represented, versioned and propagated: schema evolution, contract migration and backward compatibility across hundreds of tenants and the models built on them
Build the systems that expose Minerva's data product to internal and external AI agents (MCP servers, vector search, semantic and metrics layers)

About Minerva

Minerva builds AI for marketing leaders.

In the employer’s words · Read in context · Company website ↗

Apply at Minerva

Posting record

Report an error

Open 3 monthsWe first saw this posting 97 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.

Status in our records
Live
First seen by us
Aug 12, 202697 days ago
Recorded sightings
73
Last seen by us
Nov 17, 2026
Employer says posted
Jun 9, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

Higher than most similar jobs

$237K–$265K against $127K–$190K, the middle half of what similar US postings state.

From 2,383 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 97

Up longer than most. Similar jobs usually come down between day 6 and day 56.

From 14,041 similar postings that came down. Coming down is not always a hire.

Minerva is hiring

6 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • BigQuery
  • dbt
  • Elasticsearch
  • Kafka
  • MySQL
  • Redshift
  • Snowflake
  • Airflow
  • PostgreSQL
Where the posting names them
- 5+ years in data/software engineering in a data-heavy context, with real ownership of a production data platform at scale (many sources, many consumers) - Expert Python and SQL, fluent enough that ingestion and modeling are reflexes, not projects - Deep experience with transformation and orchestration tooling (SQLMesh, dbt, Airflow or equivalent) and a point of view on where they break and what comes next
- Deep experience with transformation and orchestration tooling (SQLMesh, dbt, Airflow or equivalent) and a point of view on where they break and what comes next - Strong grasp of analytical warehouses (Snowflake/Redshift/BigQuery) and how they interplay with transactional stores (Postgres/MySQL) - A track record of multi-tenant design: isolation, governance and secure access patterns as tenant count climbs
- Expert Python and SQL, fluent enough that ingestion and modeling are reflexes, not projects - Deep experience with transformation and orchestration tooling (SQLMesh, dbt, Airflow or equivalent) and a point of view on where they break and what comes next - Strong grasp of analytical warehouses (Snowflake/Redshift/BigQuery) and how they interplay with transactional stores (Postgres/MySQL)
- Lead the evaluation and migration of our orchestration and transformation stack as throughput, concurrency and latency demands outgrow what today's tooling is built for, incrementally, without halting the business running on top of it - Architect the path to real-time: keeping the analytical warehouse in sync with the Postgres/Elasticsearch product backends and standing up the infrastructure for the CDP (streaming audiences, identity resolution, reverse-ETL to ad platforms and CRMs) - Define how pipelines are built, tested, deployed and governed as the team and tenant count grow: isolation, privacy/opt-out enforcement and data-quality SLAs as first-class platform properties
- Strong communication skills, preferably has interfaced with enterprise customers before - Data lineage and reactive-propagation systems; streaming (Kafka/Flink/Snowpipe) - Backend or ML/AI-eng exposure; feature engineering and training infra are adjacent to this role

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

ABOUT MINERVA

Minerva builds AI for marketing leaders. We work together with marketers to automate and accelerate their workflows with AI agents. Our agents augment the end-to-end workflow of the marketer by automating analysis, campaign planning, activation, measurement and reporting.

Customers like the NBA, Ramp, Wander, Hard Rock Stadium Group and Luxury Presence use Minerva to develop a better understanding of their customers and introduce AI specifically built to understand the customer into their commercial organizations. Our campaigns outperform other tools because we built the entire stack: from identity to enrichment to data integration as well as agents to action and report on the analysis.

We've raised $20M from The General Partnership, 8VC, Lingotto, NBA Investments, Topology Ventures, Future Positive, Background Capital and many others. Our team brings together operators and investors from Citadel, Dentsu, Bridgewater, Meta Superintelligence, Growthloop, Amazon and Lazard, alongside engineers and researchers from Berkeley, MIT, Stanford and Cambridge.

ABOUT THE ROLE

We run a multi-tenant transformation platform that unifies a portfolio of customer brands into a single golden data model across Shopify, HubSpot, Klaviyo, Google/Meta Ads and more.

You'll be the technical owner of this part of our broader data platform: the person who designs for the regime we're growing into rather than the one we're in. The defining question of the role is how to make the cost of the next tenant (and the next data source, the next entity in our ontology, the next golden model) flat instead of linear, while correctness, isolation and freshness hold as the system fans out.

Increasingly, that platform isn't operated only by people. In partnership with OpenAI, our Agentic Data Engineer (ADE) already standardizes bespoke client data into golden records, and downstream agents like our Agentic Data Scientist (ADS) build models on top of it. You own the substrate they stand on (the contracts, the golden model, the access layer) and the systems that expose our data to internal and external AI agents (MCP, vector search) as a first-class channel. We believe agentic access to our data is just as important as the traditional API and ETL paths, if not more, and this role builds for that.

This is a build-from-strength role. We expect data cleaning, modeling and warehouse fluency to be second nature so your thinking is free for architecture and large-scale initiatives, especially given how much leverage modern AI coding tools give a strong engineer.

WHAT YOU'LL DO

  • Design the tenant-onboarding model so adding the Nth tenant is a config-and-metadata operation, not bespoke engineering, driving source routing, transformation, model membership and per-tenant view generation from a single source of truth rather than hand-assembly

  • Own correctness guarantees across a wide fan-out of tenants and models: the class of problem where coverage gaps, contract drift and partial rollouts can hide unless the system makes them structurally impossible. Build the contracts, audits and CI gates that turn "is every tenant fully represented?" into something the build answers, not a person

  • Own the org-identity and access layer (tenant provisioning, source-to-tenant routing, multi-tenant isolation and RBAC) so it holds at hundreds of tenants without per-tenant special cases

  • Build the platform machinery that lets our data ontology grow (new entities, attributes and behaviors) without breaking everything downstream. Own how the ontology is represented, versioned and propagated: schema evolution, contract migration and backward compatibility across hundreds of tenants and the models built on them

  • Partner with the field as our FDEs and customers surface the new concepts a customer needs, making adding them to the canonical model a safe, repeatable operation rather than a risky one-off

  • Build the systems that expose Minerva's data product to internal and external AI agents (MCP servers, vector search, semantic and metrics layers) so agents can query, reason over and act on our data safely. Treat agentic access as a first-class delivery channel alongside API, batch ETL and CRM integrations

  • Own the substrate our agentic workflows depend on: the golden-record contracts ADE produces and ADS consumes. Build the guardrails, validation and observability that let agent-generated transformations be trusted in production at scale. You build the reliability layer under the agents

  • Lead the evaluation and migration of our orchestration and transformation stack as throughput, concurrency and latency demands outgrow what today's tooling is built for, incrementally, without halting the business running on top of it

  • Architect the path to real-time: keeping the analytical warehouse in sync with the Postgres/Elasticsearch product backends and standing up the infrastructure for the CDP (streaming audiences, identity resolution, reverse-ETL to ad platforms and CRMs)

  • Define how pipelines are built, tested, deployed and governed as the team and tenant count grow: isolation, privacy/opt-out enforcement and data-quality SLAs as first-class platform properties

WHAT YOU HAVE

  • 5+ years in data/software engineering in a data-heavy context, with real ownership of a production data platform at scale (many sources, many consumers)

  • Expert Python and SQL, fluent enough that ingestion and modeling are reflexes, not projects

  • Deep experience with transformation and orchestration tooling (SQLMesh, dbt, Airflow or equivalent) and a point of view on where they break and what comes next

  • Strong grasp of analytical warehouses (Snowflake/Redshift/BigQuery) and how they interplay with transactional stores (Postgres/MySQL)

  • A track record of multi-tenant design: isolation, governance and secure access patterns as tenant count climbs

  • Demonstrated judgment on the stability vs. speed of development tradeoff: you've kept a platform reliable for its users while still letting a team ship fast on top of it, and you can articulate how you decided where each belonged

  • Experience evolving a schema, data model or ontology in production (versioning, migration and backward compatibility) without breaking downstream consumers

  • Interest in (or experience) exposing data to AI agents (MCP, vector search, semantic layers, retrieval) and a conviction that agentic access is a first-class way to deliver a data product

  • Comfort owning ambiguous, cross-cutting initiatives end-to-end in a lean, fast-changing environment. Willing to work onsite in NYC (relocation provided)

NICE TO HAVES

  • Lakehouse or Spark experience and comfort handling very large datasets

  • Built or operated a CDP, identity graph or reverse-ETL/activation system

  • Strong communication skills, preferably has interfaced with enterprise customers before

  • Data lineage and reactive-propagation systems; streaming (Kafka/Flink/Snowpipe)

  • Backend or ML/AI-eng exposure; feature engineering and training infra are adjacent to this role

  • Heavy and efficient use of AI coding tools (Claude Code, Cursor, etc.) as a force multiplier

  • Built infrastructure for agentic or LLM workflows on top of data (OpenAI Agents SDK, MCP servers, vector DBs, retrieval and eval harnesses)

  • Prior early-stage startup experience

Counterpart roles: you own the technical side of evolving the ontology and platform. Our Backend Engineer, Data owns the product side: what gets precomputed and how it reaches the app, built on the semantic views you publish. Our forward deployed engineers sit with the customer, expand the ontology from the field and feed you the patterns worth productizing.

COMPENSATION

$237,000–$265,000 base salary, commensurate with experience. Meaningful equity. Medical, dental and vision.

WHERE WE WORK

We work in person from our office at 300 Kent Avenue in Williamsburg, Brooklyn.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 861, the most 1,353, and the latest week had 1,022.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay
COMPENSATION $237,000–$265,000 base salary, commensurate with experience. Meaningful equity. Medical, dental and vision. WHERE WE WORK
Location & working pattern

New York City, New York, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.