Backend Engineer, Data at Minerva · LumiJobs

Responsibilities

A warehouse full of consumer data does nothing for a marketer until they can sort, filter and chart it in the time it takes to ask the question.
Our data team builds the consumer graph and each brand's first-party models, and our data scientists train scores on top. This seat makes all of it usable in the product: first-party fields that respond instantly, scores on the pages marketers already use, segments that stay current, and an agent that turns a plain-English question into the right query against a brand's own data.
This is an IC or senior IC seat on product engineering, working day to day with data engineering and data science. Your counterpart on the warehouse side is our Staff Data Engineer, who owns the golden model and publishes the semantic views you build on.
Own how first-party data performs in the app. Any field a brand connects can be sorted, filtered and charted without a live warehouse query. You decide what gets precomputed, where it lives and how it stays fresh.
Own how our models reach marketers. Propensity, LTV, churn and product-fit scores on the person, segment and product pages, with full distributions instead of a single number.
Own dynamic segments. Segments that update as new data lands, with stats ready for activation.
Own the in-app agent's query tool, built on the semantic views our data platform team publishes. You own the path from a marketer's question to the right rows.
Own the product side of the sync. What gets precomputed, and the path from Postgres to the synced client. Each hop costs money and time, and you choose on purpose.
Extend the pipelines. You mostly build on what the data team produces. When a feature needs a table that doesn't exist, you write the model or pipeline step yourself.
Ship end to end. One feature can mean a Python Lambda, a Zero schema change and a TanStack Start page. You ship all three.
App: TypeScript, TanStack Start, React 19, Tailwind and Base UI, on Vite and Bun.
Sync: Zero on Postgres, schema in Drizzle. The app reads from a live-synced local copy of the data instead of request-response endpoints.

Backend Engineer, Data

Responsibilities

Benefits

Company

Minerva

More roles at Minerva