Memorisely
AI Product Design

The product builder emerges

A new hybrid role spanning product strategy, UX, UI and frontend engineering.

Zander Whitehurst

10 min read

Every few years, our industry invents a new job title and everyone argues about whether it is real. UX designer, product designer, design engineer. I have watched each one go from a slightly awkward label to something people proudly put on their LinkedIn.

The latest one I keep seeing is the product builder. A person who can take an idea from a fuzzy problem all the way to a working product, spanning product strategy, UX, UI and frontend engineering. A year or two ago I would have said that was a unicorn. Now I meet them every week, many of them former students. Here is what the role is, why it exists now, and how you might grow into it.

What is a product builder?

A product builder is someone who owns the whole arc of a feature. They work out what to build and why. They design how it should work and how it should look. Then they build it, in real code, and ship it to real users.

They are not experts in everything. A good product builder knows where their depth runs out and when to bring in a specialist. But they are fluent enough in each area to move an idea forward without waiting on a handover at every step.

Product builders work across the whole arc, from fuzzy problem to working code.

Why AI made this possible

The product builder has always been theoretically possible. A few rare people have always been able to do it all. What held most of us back was time. Learning to write production frontend code on top of a design career took years, and keeping up with both was exhausting.

AI tools have changed that. Claude Code, Cursor and similar tools let a designer describe what they want and get working code back, then refine it in conversation. The gap between knowing what good looks like and being able to build it has shrunk dramatically.

That does not mean the skills no longer matter. It means the cost of crossing between disciplines has dropped. A designer who understands components, state and data can now build alongside an agent. A PM who understands users and flows can produce a real prototype instead of a slide.

Product strategy

The first area is deciding what to build. Product builders spend time understanding the problem, the users and the business before they touch a tool. They write short PRDs, talk to customers and make calls about scope.

This matters more than ever, because AI makes building cheap. When you can build almost anything quickly, the expensive mistake is building the wrong thing. Product builders protect against that by starting with the problem.

UX

The second area is how the product works. Flows, information architecture, states, edge cases and the small moments that make something feel considered. This is where research and empathy meet structure.

Product builders often do their UX thinking inside a working prototype rather than a static diagram. They click through real behaviour, notice where it breaks and fix it. That tight loop catches problems that would otherwise surface weeks later.

UI

The third area is how the product looks and feels. Hierarchy, typography, spacing, colour and motion. Good product builders have taste, and they care about craft even when the deadline is tight.

They also work closely with the design system. Because agents build with whatever components they are given, a product builder who knows the system well can produce consistent, polished work quickly. They still use Figma when a problem needs careful visual exploration, then bring the decision back into code.

Frontend engineering

The fourth area is building it for real. Components, state, data fetching, accessibility and performance. Product builders do not need to be senior engineers, but they need to understand enough to direct an agent well and to review what it produces.

That means reading code, spotting when something is wrong and knowing when to ask an engineer for help. It also means opening pull requests, responding to review and seeing work through to production.

How it differs from design engineer and PM

The roles overlap, so it helps to be clear about the differences:

  • Design engineers sit between design and engineering. They are usually deep in UI and frontend, often focused on design systems, interaction quality and prototyping. They tend to work on problems someone else has framed.
  • Product managers own the why and the what. They set direction, prioritise and coordinate across teams, but they rarely design or build the product themselves.
  • Product builders span both. They frame the problem like a PM, design like a product designer and build like a design engineer. Their breadth is the point.
The product builder spans the ground that used to be covered by handovers.

None of these roles is better than the others. Most teams need all three. The product builder simply fills a gap that used to be covered by handovers.

What a week looks like

A typical week for a product builder might go something like this:

  • Monday. Talk to a couple of customers, review feedback and write a one page PRD for the next feature.
  • Tuesday. Build a rough working prototype with Claude Code, then click through it to find the gaps.
  • Wednesday. Take the tricky parts into Figma, explore a few directions and decide.
  • Thursday. Bring those decisions back into code, polish states and motion in the browser, then open a pull request.
  • Friday. Respond to engineering review, ship behind a flag and share what was learned with the team.
Short loops between thinking, designing and building, with very little waiting.

Not every week is this tidy. Mine certainly are not. But the shape is right: lots of short loops between thinking, designing and building, with very little waiting.

A few months ago, one of our team took a feature request from a customer call on a Monday and had it live by Friday. No tickets passed between three people, no handover documents. When I asked what had been hardest, she said it was deciding what to leave out. That is a product builder answer.

How to grow into it

If you are a designer, you probably already have the UX and UI foundations. The gaps are usually strategy and code. Practise writing short PRDs before you design anything. Then build small things with an AI coding tool, starting with a personal project where nothing is at stake.

If you come from engineering, the gaps are usually taste and user empathy. Spend time with designers, sit in on research sessions and study why good interfaces work.

If you are a PM, start prototyping. Turn your next spec into something clickable. You will learn more from one working prototype than from a dozen review meetings.

Each starting point has its own gap, so stretch into one area at a time.

Whatever your starting point, pick one area to stretch into at a time. Trying to learn everything at once is a quick route to burnout. I speak from experience. My first attempt at learning React involved four tutorials open at once and a strong desire to lie down.

What it means for teams

Product builders change how teams are shaped. Smaller groups can own larger areas because fewer handovers are needed. Specialists become more valuable, not less, because product builders lean on them for depth in the places that matter.

Teams that adapt well tend to invest in strong design systems, clear quality bars and good engineering review. Those are the guardrails that let product builders move fast without making a mess.

The opportunity

The product builder is not replacing designers, engineers or PMs. It is a new option, made possible by tools that finally make crossing disciplines practical. For anyone who has ever felt frustrated waiting for their idea to be built, it is an invitation to build it yourself. Our AI Design Training Path brings all six AI design bootcamps together for anyone who wants to make that move.

Keep reading

View all
View all

Optimize your AI for better experiences, not AI slop.

View all

AI Prototyping Skills

Prototype with AI using clean UI patterns and guardrails so flows feel product-grade, not generic template slop.

$99

AI UI Motion Skills

Motion and micro-interaction patterns that make AI-built UI feel designed, polished, and trustworthy in real products.

$99

Fix AI Slop Skills

Spot AI slop early and fix type, spacing, and components so your product looks intentional, not like a template.

$99

AI Responsive Design Skills

Responsive layout patterns for rails, sidebars, and breakpoints so AI-generated UI adapts cleanly from narrow to wide.

$99

AI Dark Mode Skills

Dark theme tokens, contrast, and surfaces that keep AI-generated UI readable and product-grade, not flat gray on black.

$99

AI Color Token Skills

Neutral and primary ramps with clear steps so AI palettes stay systematic, not a random set of accent hex codes.

$99
View all