About
If I see chaos, I organise it. That is most of the job.
I am a UX/UI designer focused on design systems. I like rules, and I like following them — not because process is comforting, but because a system nobody can read stops being a system.
How I work
I work well in Figma: building components, maintaining a design system, designing end-to-end flows, and preparing a handoff a developer can build from without a call. I take my time over small things, because small things are what break at scale.
When I design a new feature I am already thinking about the file six months from now. How will this be used when someone adds the next thing? What will a designer who joins the team see when they open this page — a pattern they can follow, or a puzzle they have to reverse-engineer? I would rather answer those questions before they are asked.
Design systems
So far I have always worked inside systems other people started — renovating them, repairing them, extending them where a flow needed something that did not exist yet. It is a narrower job than authoring one, and it teaches a specific discipline: understand why the existing thing was built that way before you add to it.
It has also made me clear about what I want next — to be in the room when the system is decided, not only when it is maintained.
What I look for
A team that is structured and organised, or one that wants to be. I am useful in both — I am at my best where there is a real system to build and defend, and I am comfortable being the person who introduces one where there is not.
A structure you can read is a structure you can change.