UX Designer, Figma

FullTime
Remote
Discussed on the first call, set against experience and location.
Open

One full time designer to turn dense product flows into screens that survive contact with code, in Figma, beside the engineers who build them.

What the role covers

Product design for platforms rather than pages: booking and quoting flows, a lending and ledger back office, dashboards people sit in all day, and a marketing surface that has to carry the same voice. Figma is the working surface, and the handover is a conversation rather than a file thrown over a wall.

What you would design

The hard screens rather than the pretty ones. An operator comparing quotes under time pressure. A loan officer working through a case with a committee waiting. A dashboard somebody has open for eight hours, where one wrong default costs a day.

You would also own the system that holds it together: the components, the states nobody remembers to draw, the empty and error cases, and the dark mode that has to look deliberate rather than inverted.

What we look for

Strong Figma craft, and the judgement to know when a component belongs in the library and when it is one screen pretending. You think in states and edge cases, not in happy paths, and you can defend a layout by naming the decision it makes easier.

You are comfortable sitting with engineers while a design meets the code, and changing your mind in public when the data says so. A portfolio of flows tells us more than a portfolio of dribbles.

How we work

An issue before the work, then one pull request for it, reviewed and merged by a person. Every script that changes data reports what it would do by default and acts only when you pass --execute, inside one transaction, naming the database it reached before it says anything about rows.

Claims are gated on exit codes, not on output that looks right. A merge to main builds and deploys on its own, every image carries a real version, and the way back is written down before the way forward is taken.

The estate runs on its own hardware, so you see the whole path: the schema, the API, the screen, the image, the rollout and the thing that pages someone when it breaks.

How to apply

Use the contact form on this page and attach your CV. Tell us about one thing you built that you are still proud of, and one thing you got wrong and what it taught you. The second answer is the one we read twice.

We reply to everyone who writes a real message. A short note about your own work is worth more here than a cover letter written for anybody.

Apply

Send a short note on what you have built and why this role fits. Applications land in the same inbox as the contact page and are answered within a few days.