# [Senior/Mid/Junior] data engineer · [city] or remote

We are hiring our [Nth] data engineer. You will own the [X pipeline, currently about Y rows a day]. The team is [N] analysts and [N] engineers. [Who else writes models]. [How the warehouse is used]. [How the on-call rotation works].

## You will be good here if

- You have owned a pipeline in production past v1 and have backfill war stories you can describe with row counts.
- You treat the schema as the contract and can name a time you defended one under pressure.
- [The third trait you actually care about, with a sentence on the behaviour you want].

## What we use

[Warehouse, orchestrator, transformation tool, languages]. We will not retrain you on a stack, but we do not care if you came from [adjacent stack] as long as you can show us a contract you wrote.

## What you will not get

A dashboard backlog you never get to. A warehouse bill nobody owns. An analyst team that treats you as a ticket queue.

## Compensation

[Currency][low] to [high] base. [low] to [high] percent equity. We post the band because we mean it and we will not negotiate against ourselves.

## How we hire

30-second post, screen plus assessment via Picked, 20-minute interview via Picked, one on-site half-day with the team and an analyst. We aim to give a yes or no in 7 days.

## What is the rubric

Pipeline reliability, schema judgement, cost awareness, cross-team comms, honesty about edge cases. Not credentials.

That is the JD. Apply via [link], or just send a paragraph about the last pipeline you owned past launch and what broke first.

[Your name], [your title]