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

We are hiring our [Nth] backend engineer. You will own a service end-to-end (currently: [the X pipeline, about Y events a day]). The team is [N] engineers. [Who else writes code]. [How you ship]. [How the on-call rotation works].

## You will be good here if

- You have owned a backend service in production past v1 and have war stories you can talk through in plain English.
- You reach for the boring, working answer first and can defend the choice in one paragraph.
- [The third trait you actually care about, with a sentence on the behaviour you want].

## What we use

[Languages, datastores, infra]. 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 post-mortem.

## What you will not get

A microservice for every noun. A four-hour standup. A CTO who avoids the on-call schedule.

## 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. We aim to give a yes or no in 7 days.

## What is the rubric

Systems thinking, reliability instinct, pragmatism, cost awareness, communication. Not credentials.

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

[Your name], [your title]