full-stack-engineer.md
283 words · 3 min read
# [Senior/Mid/Junior] full-stack engineer · [city] or remote
We are hiring our [Nth] full-stack engineer. You will own product features end-to-end (next on the roadmap: [feature X and feature Y]). The team is [N] engineers and [N] product designer(s). [Who else writes code]. [How you ship]. [How decisions get made across the stack].
## You will be good here if
- You have closed a feature end-to-end past v1, including the change-log, the metric, and the support handover.
- You can hold judgement about UI, API, and storage in the same conversation without flinching.
- [The third trait you actually care about, with a sentence on the behaviour you want].
## What we use
[Languages, frameworks, datastores]. We will not retrain you on a stack, but we do not care if you came from [adjacent stack] as long as you can talk us through the trade-offs.
## What you will not get
A handoff culture where each layer throws over a fence. A roadmap that ignores the database. A product manager who treats engineering as a vending machine.
## 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 a product designer. We aim to give a yes or no in 7 days.
## What is the rubric
Range of judgement, shipping instinct, system breadth, comms, curiosity. Not credentials.
That is the JD. Apply via [link], or just send a paragraph about the last feature you closed end-to-end and what broke first.
[Your name], [your title]