product-designer.md
291 words · 3 min read
# [Senior/Mid/Junior] product designer · [city] or remote
We are hiring our [Nth] product designer. You will own [the X surface, currently at Y users / Z events per day]. The product team is [N] PMs and [M] designers, plus an engineering pod of [N]. [Who runs critique, and on what cadence]. [How you ship]. The work is the work: you will run the research, sketch the screen, defend the type ramp, read the engineer's PR, and own the second use of every component.
## You will be good here if
- You have killed one of your own components because the system was paying for it, and you can name the cost of the kill.
- You bring work to critique that is still cheap to change, and you walk out with three notes that survive the night.
- [The third trait you actually care about, written in the same voice].
## What we use
[Stack: Figma, prototyping, analytics]. We do not care which tool you used last; we care that you read the engineer's PR and that the system you ship has a documented second use for every component.
## Compensation
[Currency][low] to [high] base. [low] to [high] percent equity. We post the band because we mean it.
## How we hire
30-second post, screen + assessment via Picked, 20-min interview via Picked, one on-site half-day with the PM, an engineer, and a design critique session. We aim to give a yes or no in 7 days.
## What is the rubric
Visual judgement, system thinking, research instinct, engineering literacy, critique-readiness. Not your portfolio cover page.
That is the JD. Apply via [link] or just send a paragraph about the component you most recently killed.
[Your name], [your title]