I design it, I build it, and I argue about what it is for.
UX designer, visual designer, and the person who ends up writing the frontend. San Francisco.
Three disciplines, and I keep refusing to pick one. I design the interaction and the visual language, I build the frontend, and I do enough product management to know which third of the roadmap is worth designing at all. A decision that is painful to build is usually a design problem too, and you only find that out if you have sat in both chairs.
I am at my best when the brief does not exist yet. Somebody has a rough shape of a problem, a deadline, and four teams who disagree, and the first job is turning that into something you can actually draw. Zero to one is the part I like. Most of my work has been on systems that are complicated underneath. Health records mid-migration. Hundreds of hospital sites. Agents doing work on someone's behalf. The job in all of them is the same: make it feel simple without hiding the parts a person needs in order to trust it.
Right now I lead frontend at Harco, building the interface for agents that apply to jobs on your behalf.
approach
What I do
Find the problem before designing the solution, then design interactions that feel obvious and build them. Clear states, honest empty and error cases, and accessibility treated as part of the work rather than a pass at the end.
What I avoid
Appearance ahead of purpose. If an element is not carrying weight it comes out. In high-stakes products, clarity stops being taste and becomes a safety requirement.