From Pixels to Prompts: My Journey from UX Designer to AI Product Designer
For years, my job had a shape I could describe in one breath: understand the user, sketch the flow, wireframe the screens, polish the pixels, hand off to engineering. It was a craft built on control. I decided where the button went. I decided what happened when you tapped it. Every state was mine to design.
Then AI started showing up in the products I was designing for, not as a feature bolted onto a screen, but as the thing generating the screen’s content, sometimes even deciding what the screen should be in the first place. And I noticed something uncomfortable: my usual toolkit didn’t quite fit anymore.
A few shifts have already started rewiring how I approach design work:
From screens to systems. I used to think in flows and states. Now I’m learning to think in inputs, prompts, guardrails, and fallback behaviors, designing for a system that has a personality and a failure mode, not just a layout.
The biggest unlock, though, has been learning to actually build, not just design on top of what engineers hand me. Through the bootcamp, I got hands-on with creating AI agents for the first time, figuring out how to give a model a role, a set of tools, and boundaries for what it should and shouldn’t do on its own. It’s a strange feeling, designing behavior instead of designing a screen.
I also started using Cursor and Claude Code, and that alone shifted something in how I see myself.
I’m not a developer, and I’m still not pretending to be one, but being able to prototype an idea in code instead of just Figma to see an actual working flow instead of a static mockup has changed how fast I can test whether an idea is even worth pursuing.