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

We are hiring our [Nth] frontend engineer. You will own [the X app, currently used by Y users a month]. The team is [N] engineers and [N] product designer(s) who pair on most surfaces. [Who else writes frontend code]. [How you ship].

## You will be good here if

- You have shipped a customer-facing interface past v1 and have layout-shift war stories you can tell over a coffee.
- You think about accessibility before the ticket is filed and reach for the keyboard before the mouse when testing.
- [The third trait you actually care about, with a sentence on the behaviour you want].

## What we use

[Framework, design system, build chain]. We will not retrain you on a stack, but we do not care if you came from [adjacent stack] as long as you have shipped to real users.

## What you will not get

A Friday production push. A waterfall sprint plan. A design partner who hands you a JPEG and disappears.

## 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

Component thinking, accessibility instinct, performance attention, design literacy, curiosity. Not credentials.

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

[Your name], [your title]