The interface is the easy part. The real work is the thinking underneath it: how a system holds up with messy data, rushed users, and decisions nobody wants to make twice.

I have spent five-plus years designing for early stage startups where the brief is usually one sentence and the constraints are real. Small teams, tight runway, and users whose day does not pause because your product is confusing. That taught me to design for the system rather than the demo: who has to act next, what happens when they do not, and what the product owes them when something goes wrong.

I work across the whole arc. I sit in the commercial conversation, run the research, frame the problem, build the flows, define the tokens and components, write the interface copy, and stay through handoff and iteration. On multi sided products like DeliverEat and OSSHNG that range is the point, because the hard work is deciding once what an order or a patient record is, then making four very different audiences agree with that definition.

Two things sit outside the usual designer profile and make me more useful early. I am trained in law and called to the Bar, so I can read the contract, spot the regulatory risk in a flow before legal does, and design consent and compliance moments that are honest rather than defensive. And I build automation, mostly in n8n, which means I can take the repetitive operational work around a product and turn it into a workflow instead of another dashboard nobody opens.

I am looking for a team where design has a seat in the strategy conversation and the work reaches people at scale. Open to relocation.