The Journal

Workflow & Career3 min read

The Future of Design Engineering: AI, No-Code, and What Comes Next

AI tools, no-code platforms, and new workflows are reshaping how we build UIs. Here's what's coming for design engineers and the skills you'll actually need.

Every “AI is coming for frontend developers” take misses the same thing. When the cost of writing code drops toward zero, the code stops being the valuable part — deciding what to build and whether it’s any good becomes the whole game. That work is getting more valuable, not less.

Typing gets cheap

AI writes the component. No-code ships the marketing page. Both compress the part of the job that used to eat your week: turning a decision into working pixels. A few years ago that was most of the job. It shrinks every quarter, and it isn’t coming back.

So taste appreciates

When anyone can generate a working UI in minutes, the scarce skill is knowing which UI is worth shipping. Three things get more valuable as typing gets cheaper:

  • Taste: knowing why one version feels right and the other feels cheap.
  • Systems thinking: designing the token, not the button; the pattern, not the page.
  • Judgment: what to cut, what to ship, what isn’t worth building at all.

The roles converge

Designer and engineer stop being two separate chairs. When a designer can prompt a working prototype and an engineer can nail the visual details, the handoff shrinks to a conversation. The people who own both sides at once — design engineers — end up sitting right in the middle of that, which is a good place to be.

Invest here

Keep the AI, and let it write the boring parts. Then spend the hours it gives back on the things that don’t automate: studying interfaces you admire, working out why they feel right, slowly building an eye. Read how I actually use AI day to day if you want the tactical version. In five years, that judgment is the job.

Frequently asked questions

Will AI replace design engineers?
No. As AI drives the cost of writing code toward zero, the code stops being the valuable part, and deciding what to build and whether it's any good becomes the whole game. That work, which is taste, systems thinking, and judgment, gets more valuable, not less.
What skills should design engineers focus on for the future?
Invest in judgment over any specific framework or model, since those age out in a few years. Three skills appreciate as typing gets cheap: taste, or knowing why one version feels right; systems thinking, designing the token rather than the button; and judgment about what to ship or cut.