Skip to content

A designer who stayed for the build.

I started in design: flows, interfaces, the decisions that make a product make sense. The more of it I did, the more I noticed that the interesting questions came before the design brief and after the handoff.

Why are we building this? What will it take to ship? Did it work? I wanted to be able to answer all three myself, so I learned to build what I design, and I'm learning to measure what I build.

That is what Product / Design Engineer means here. One person who can carry a problem from the first conversation to a running product, and tell you afterwards what it changed.

Principles

More of how I think, in writing

  1. The problem comes first.

    A well-built answer to the wrong question is still the wrong answer. I'd like to find that out before the build, not after.

  2. Design isn't finished until it's running.

    A mockup is a claim about how something will feel. The code is where that claim gets tested, so I stay for that part.

  3. Speed is for learning.

    Building faster is only useful if it means finding out sooner. AI lets me try three approaches in the time one used to take.

  4. Outcomes over output.

    The screen was never the point. What changed for the person using it, and for the business behind it, is the point.

Experience

Three kinds of work, and what each one taught me that I still use.

  1. UI/UX AssociateNow

    Designing interfaces and flows for digital products, and working with the people who build them.

    What carries over

    • Interface design
    • User flows
    • Design-to-development handoff

  2. Freelance designer

    Design work delivered directly for clients: scoping the brief, presenting options, and owning the result.

    What carries over

    • Client communication
    • Scoping
    • Working to a business goal

  3. Community leadership and digital campaigns

    Organising people and running campaigns, where the message either lands with a real audience or it doesn't.

    What carries over

    • Audience understanding
    • Clear communication
    • Coordinating people

Capabilities

Product thinking
Problem framing · Prioritisation · Scoping · Outcome metrics
UX
User flows · Information architecture · Prototyping · Usability testing
Interface design
Visual systems · Typography · Layout · Responsive design
Frontend
React · Next.js · TypeScript · CSS architecture · Accessibility
Interaction
Motion design · Microinteractions · State design
Design systems
Tokens · Component libraries · Documentation
AI-assisted development
Agentic coding workflows · Rapid prototyping · Evaluation

Have a problem worth building around?

Start a conversation
Esc