From Product Designer to AI Design EngineerFrom Product Designer to AI Design Engineer

I changed my job title before anyone gave me permission to. For most of my career the words product designer carried everything I did. Research, flows, interface, the long arguments about spacing, then the handoff to engineering and the slow erosion of intent that happened on the other side of it. Somewhere in the last two years the work itself shifted under me, and the title stopped describing what I actually do all day. So I started calling myself an AI Design Engineer, and the honest part is that the work had already decided. I was just catching up to it.

What changed is simple to say and harder to live through. Building got cheap. The thing that used to separate a designer from a shipped product, the engineering, the time, the queue, all of that compressed into an afternoon with the right tools. I design a flow and I ship the React for it the same day. When the cost of building collapses, the rare thing is no longer the ability to make something look right. It is the judgment to know what is worth making, plus the ability to put it into production yourself.

The prototype is not a picture of the argument anymore. It is the argument, running in the browser, with real state and real edge cases.

The market is already pricing this in, quietly, before it has agreed on a name for it. The Bureau of Labor Statistics projects graphic design roles to barely move this decade, around two percent, and in the same paragraph it names AI as a reason companies will lean on fewer of them. The roles that pay more and grow faster are the ones sitting closer to code. That gap is not about talent. It is about proximity to the thing that actually ships.

I want to be careful here, because the easy version of this story is that AI replaces designers, and the data says something more interesting. When Figma surveyed a few thousand designers and developers in 2025, the overwhelming majority said design matters as much or more for AI products, not less. More than eight in ten on both sides called AI literacy essential to staying relevant in their field. So the demand for design did not fall. The demand for a specific kind of designer fell, the one who stops at the comp and hands the intent to someone else to interpret.

There is a trust gap underneath all of this that almost nobody is talking about honestly. In Stack Overflow's 2025 developer survey, more than eight in ten developers said they use AI in their daily work, while fewer than a third said they actually trust what it produces. Read that twice. The people closest to the code are using a tool they do not believe, every day, because the speed is impossible to refuse. That gap is the whole opportunity. Someone has to sit between raw AI output and a thing you would actually ship to a customer, with the taste to catch what is wrong and the technical understanding to fix it. That person is not a pure designer and not a pure engineer. That is the role I have been doing for two years without a clean word for it.

None of this means the craft I spent a decade building stopped mattering. It means the craft moved up a layer. I spend less time pushing pixels and more time deciding which of five AI generated directions is the one that respects the research, the brand, and the business, and then I take that one all the way down into production code. The execution did not disappear. It got automated, which means owning the outcome end to end is finally possible for one person. The designers I watch thriving right now are not the ones fighting the tools. They are the ones who picked up the part of the stack that used to be off limits and refused to give the outcome to anyone else.

So I am not waiting for a recruiter to invent the title and bless it. The work already changed. The number on the offer letter is already following the people who can both decide and build. Calling myself an AI Design Engineer is not a prediction about where the field is going. It is a description of the job I already have.