When I say “I’m a designer who builds AI products” — people hear two different things.
Some think I design interfaces for ChatGPT wrappers. Others — that I’m a programmer who occasionally opens Figma.
Neither is true.
The New Role
I don’t write code by hand. And I don’t pass mockups to developers through Jira. I orchestrate AI — formulate tasks, decompose architecture, manage agents that write code, and assemble working products from the results.
This isn’t the future — it’s already happening. The only question is who does it: a designer who understands the product, or a developer who doesn’t think about UX.
What This Changes
The old path:
- Designer draws → developer codes → QA tests → PM manages
Now another path is possible:
- One person designs + orchestrates AI + deploys + iterates
This doesn’t mean teams aren’t needed. It means the speed from idea to prototype has shrunk from weeks to hours.
What You Need to Know
- Prompt engineering — not “asking ChatGPT a question,” but a systematic approach with testing
- Understanding architecture — to decompose tasks for AI
- Product thinking — to know what to build
- Design — to make it usable
This is what I call AI Product Builder.