Product Designer

What you'll own

• —The interface for one or two products, from research through to the built result
• —The design system those products share, and keeping it honest as they grow
• —Sitting with actual users — clerks, nurses, shopkeepers — and watching them work
• —Reviewing the built implementation, because a design that shipped differently didn't ship

What we need

• —A portfolio with dense, data-heavy interfaces in it — not just marketing pages
• —Research you conducted yourself, and evidence it changed your design
• —Fluency with a component-based design system, and how it maps to code
• —Accessibility as a working practice, not an audit at the end

Helpful, not required

• —Front-end code you can read and modify
• —Experience designing for low-bandwidth or older Android devices
• —Regulated-industry work — healthcare, finance, government

What this role isn't

So the wrong candidates can rule themselves out in thirty seconds rather than three interviews.

• ×It isn't a brand or marketing design role.
• ×It isn't a role where you hand off a Figma file and move on.

How we interview

1. 01Portfolio conversation — 45 minTwo projects, in depth. We'll ask what went wrong, not just what shipped.
2. 02Working session — 90 minA real dense-interface problem, worked through together. Not a take-home.
3. 03Conversation with the Head of Design — 45 minCraft, standards, and your questions.

Decision within two weeks of the first call. If it's a no, you get a reason, not silence.