About the role
This is not a marketing-page design role. The product is a workflow: import, agree the shape, write a contract, run it, review what the run was unsure about, curate, publish, deploy. Each of those screens is dense with real data and has to stay legible when a table has five thousand rows and a receipt behind every value.
The design problem is confidence. A customer has to be able to see, at a glance, what is decided, what is unsure, and what is being held back from their agent, and then act on it without reading documentation.
You would own the design system that both the site and the dashboard are built from, working directly in it rather than handing over files nobody can build from.
What you'd do
- Design the dashboard's core workflows end to end, including the empty, loading and error states
- Make dense data legible: tables, receipts, review queues, and the difference between decided and unsure
- Own the design system with engineering: one definition of each component, used by the site and the app
- Design for the phone as a first-class case, not a scaled-down desktop
- Test your designs on someone who has not seen them before, and change them when they fail
What we need
- Four or more years designing software, with at least one complex tool in your portfolio
- You design systems rather than screens, and can show the component library to prove it
- Comfortable with typography, hierarchy and restraint in an interface that cannot be decorative
- You can read and write enough HTML and CSS to be precise with engineers
- Accessibility is part of your process, not a checklist at the end
Nice to have, not required
- You have designed for data-heavy or technical users before
- You build your own prototypes in code
- Experience with a strong visual identity applied to a product surface
How we work
- Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
- Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by a customer.
- Safety-critical means the boring answer usually wins: fail closed, keep the receipt, don't guess.
- We only claim what ships. That applies to the product, the roadmap and the offer letter.
How hiring works
- 1A 30-minute call about something you've built and what was hard about it.
- 2A working session on a real problem from this codebase. You can drive, or we can pair.
- 3A conversation about how you make decisions when the evidence is thin.
- 4References, then an offer. We aim to answer within a week at every stage.