A prophecy landed on my desk
A few days ago someone sent me one of those long, confident predictions about the future of our industry. You've seen the genre: AI destroys design and development jobs, year by year, with dates and percentages. Frontend 70–80% automated by 2027. Software creation 100% democratized by 2029. The screen disappears by 2031.
It was well written. It was brutal. It was built to go viral.
And here's the uncomfortable part: half of it deserves to be taken seriously. The other half is science fiction wearing a spreadsheet.
I spend my days embedded in an agentic AI initiative inside one of the largest retailers in the world, designing how autonomous systems and humans share decisions worth real money. So this isn't theory for me. It's my Tuesday. Let me separate the signal from the theatre.
The half that's true
The core mechanism of the prophecy is correct, and pretending otherwise is cowardice.
AI doesn't take your job. It multiplies someone else's. The real threat was never a robot sitting in your chair. It's a senior designer or engineer who, armed with agents, produces what a team of three produced two years ago. Companies don't need the work to disappear to cut headcount. They just need output per person to double. It already has.
The junior freeze is real. Hiring for entry and mid-level roles in design and frontend has been quietly frozen across the industry. The tasks juniors used to learn on (production UI, layout variants, component documentation, boilerplate code) are exactly the tasks AI eats first. We are burning the bottom rungs of our own ladder, and nobody has designed the replacement.
So far, the prophecy and I agree. Now for the fiction.
The half that's fiction
Fiction #1: the decimals. "Frontend will be 70–80% automated by 2027." Where do those numbers come from? Nobody has them. Not the labs building the models, not the analysts, certainly not a blog post. Generating code is not shipping software. Integration with legacy systems, security, compliance, maintenance, the archaeology of ten-year-old databases: that's where most of the cost of software actually lives, and it automates slowly and painfully. AI writes code at superhuman speed; making that code survive inside a real organization is still stubbornly human.
Fiction #2: "software creation democratized at 100%." I've heard this one before. No-code was going to democratize software in 2015. WYSIWYG editors were going to do it in 2005. Visual Basic was going to do it in the nineties. What actually happens when building gets cheaper is the opposite of extinction: we build more software, and the bottleneck moves from producing to deciding what deserves to exist. That decision (what to build, for whom, and why) is not a technical skill. It's the core of product design. The cheaper the execution, the more expensive the judgment.
Fiction #3: the death of the screen. This one is personal. Years ago I co-founded a voice-based social network, working alongside the Google Assistant team. Back then, the same prophets told us voice would kill the screen within three years. It didn't. Screens survived because they are the highest-bandwidth channel between a machine and a human brain: nothing transmits more information faster. What agents will kill is the operational screen: the dashboard you babysit, the form you fill for the tenth time. The visual interface as a concept isn't dying; it's being promoted from workspace to control tower.
When someone predicts your extinction with decimals, they're not forecasting. They're marketing.
Where the role actually goes
The UX role isn't facing extinction. It's facing relocation. And relocations kill the people who refuse to move.
For over a decade the job was designing how people operate software. The new job is designing how software acts on people's behalf: what an agent may do alone, when it must ask, how its actions stay legible, how it fails without taking you down with it, and, above all, whether the thing should be built at all. Less choreography of screens, more constitution of behavior.
What transfers across that move is not your Figma velocity. It's the fundamentals: user psychology, information architecture, research discipline, the ability to ask what problem are we actually solving? before anyone opens a tool. Tools rot. Fundamentals compound.
In summary
The honest version fits in two sentences. The risk to your career isn't artificial intelligence; it's standing still while the role relocates. And the surest sign that a prediction is selling you something is that it comes with decimals.
The future doesn't come with percentages. It comes with homework.
If you're navigating this same relocation, my inbox is open: hello@mveiga.com