Skip to content

Open nowPosted 154 days ago

Staff Data Engineer

Minerva17 open roles

Pay
$237,000 – $265,000 a year
Where
New York City
Work mode
On site
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowStaff Data EngineerMinerva · New York City
  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Minerva's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

13.7% of postings close within 7 days. Measured by our own scanner across the market. Minerva postings stay open a median of 39 days.

Share of postings closed within
  1. 2.2%1 day
  2. 4.7%3 days
  3. 13.7%7 days
  4. 22.1%14 days
  5. 37.8%30 days
  6. 59.1%60 days
This job: posted 154 days ago

Minerva median: 39 days open

The 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.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Minerva's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.
  3. We apply on Minerva's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.
  4. Every reply, sorted

    Minerva's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.
  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.