Clara Fairbanks

Process

I design in Figma, in code,and with real people.

I love the craft of product design. The research, the problem-solving, the visual details, and the process of turning something complicated into something that feels simple.

I still sketch, map flows, run research, and spend plenty of time in Figma. But over the past year, working directly in code has changed how quickly I can explore ideas, test them with people, and get them into production.

AI makes the building faster. My design experience helps me decide what to build, how it should work, and when it's actually good.

How I work

Understand the problem

I start by understanding the people, the product, and the business. I talk to users, work closely with product and engineering, dig into technical constraints, and question assumptions about what we should build.

Some of my favorite design work happens before there's an interface to design.

Explore, design, refine

I move between sketches, Figma, and code depending on what I'm trying to figure out.

Figma is still an important part of my process, especially for visual exploration, interaction design, and getting the details right. I care a lot about typography, hierarchy, consistency, and making an interface feel considered.

When the challenge involves complex interactions, dynamic states, or real product behavior, I often move into code much earlier.

Build to learn

I use AI-assisted development and my front-end experience to turn ideas into working prototypes, often directly in the product codebase.

That lets me explore interactions with real behavior, test assumptions, and put something genuinely usable in front of people. I can try an idea, see where it breaks down, and iterate while the problem is still fresh.

It also changes how I collaborate. Working software gives designers, engineers, and product managers something concrete to react to and improve together.

Stay involved through shipping

I like being close to the implementation. I contribute front-end code, work alongside engineers, test the experience as it's built, and keep refining the details.

For me, the ability to move between design and code makes the whole process more immediate. I can spend less time describing an idea and more time exploring whether it actually works.

And that's the part I love most: making something, learning from it, and making it better.

Tools

  • Figma
  • Claude Code
  • React
  • TypeScript
  • Tailwind
  • Astro
  • Next.js
  • Mintlify
  • Git
  • Vercel

Timeline

  1. Jul 2025 –Lead Product Designer, Circle. Arc Studio, Arc Portal, Agent Stack, developer tooling.
  2. 2026 –Design consultant, LayerV.
  3. Jul 2025 – Jul 2026Fractional Head of Design, AbodeMine (stealth). Alongside Circle.
  4. 2022 – 2025Lead Product Designer, Experian Partner Solutions. Senior PD 2022–23.
  5. 2020 – 2022Senior Product Designer, Yesware. Product Designer 2020–21.
  6. 2015 – 2020Product design consultant for early-stage startups.
  7. Before thatWeb designer, developer, founded a startup.

Working on something similar? I'd like to hear about it.

LinkedIn