2 min read
The unique position of “design engineers”
Adam Bárta

Now more than ever, design and development are tied together very closely.
Designers are in a unique position where they can prompt their way to apps that would be impossible for them to make otherwise. On the other hand, developers still can’t get AI to make actually good, thought-out designs.
And let’s be real, design always has separated the “indie-hacker” apps from the ones that people actually use.
The rise of design engineers
The fact that developing simple apps is now super easy has popularized the term “design engineer”.
If you wanted to call yourself one before it meant experience both in design and in real hands-on coding, often with previous job experience as a developer… but now? Anyone with access to V0, Lovable, or Cursor calls themselves that. And the best/worst part? They can.
AI has made development so easy that anyone with decent computer skills is now an engineer. Sure, not a very good one, but they are.
So what separates the good ones?
The difference is real hands-on experience. Everyone who learned to code by hand understands coding better than those who just prompt their way with AI.
It’s not about being able to read the code; it’s about knowing how to approach the technical side, what security flaws to look for, and how to prompt fixes when they are needed.
“Design engineers” who only ever saw a chat input don’t know any of that.
They don’t know how to properly publish the app, run it, and maintain it.
That’s why we see broken apps all over — especially in the months when AI coding became accessible all of a sudden.

Real design engineer’s advantage
Now, if you actually know what you’re doing, you are in an amazing position right now.
You can bring ANY idea to life and actually do it WELL.
The design stage of the process is the most important one. Starting in Figma, Paper, etc., will already get you ahead of 90% of others. Figure out what you wanna make, how it should work, then bring it to life — not the other way.