The short answer: AI is not only removing jobs, it is merging them. When a tool can do the routine half of a role, one person can cover two or three roles that used to need separate hires. It has already happened to frontend and backend developers, and it is happening to designers. Over the next three to five years we expect the same pattern in product, marketing, sales, operations and creative work. Most of these merged titles are still rare in job ads. That is exactly why now is the time to grow into one.
| Merged role | What it absorbs | How far along |
|---|---|---|
| Full-stack developer with AI | Frontend + backend | Normal now |
| Design engineer | UI/UX designer + frontend developer | Growing fast |
| Product builder | Product manager + designer + engineer | Early, spreading |
| GTM engineer | Marketing ops + sales development + developer | Early, startups first |
| Forward-deployed engineer | Solutions consultant + engineer + account manager | Early, AI companies first |
| Creative technologist | Creative director + designer + editor + automation | Emerging |
| Agent operations lead | Operations manager + process analyst + automation engineer | Mostly future |
Above all seven sits one more: the company architect, one person who designs a whole business as a system and runs AI as the workforce.
Why are roles merging instead of just disappearing?
Most jobs are a bundle of tasks. Some need judgement: deciding what to build, what good looks like, what a client really wants. Others are execution: writing the boilerplate, resizing the assets, cleaning the spreadsheet, chasing the follow-up.
AI is good at execution and weak at judgement. So when it takes over the execution half of two neighbouring jobs, what's left is two halves of judgement, and those fit in one person's head. The developer who no longer hand-writes every API route has time to own the interface too. The designer who no longer redraws every screen has time to ship it in code.
The World Economic Forum's latest Future of Jobs survey of over 1,000 employers expects about 39% of core job skills to change by 2030. Change on that scale doesn't just reshape jobs one by one. It redraws the lines between them.
The two merges that already happened
1. Full-stack developer with AI. Ten years ago, a frontend developer and a backend developer were two hires. Today most product teams expect one engineer to move across the whole stack, with AI writing a large share of the routine code on both sides. The specialist roles still exist, especially at scale, but the default hire has changed.
2. Design engineer. The handoff between a designer's mockup and a developer's build was always where quality leaked out. Design engineers close that gap: they design in the browser, prototype in real code and ship the polish themselves. We wrote about why we prototype in code now, not Figma. AI made this practical, because a designer can now get working code without spending years learning a framework first.
Five roles that are merging next
3. Product builder (product manager + designer + engineer)
One person who decides what to build, designs it and builds it. Figma's CEO Dylan Field has described a "shifting and merging of roles" and says everyone is becoming a product builder. A 2026 Products That Count report, summarised by Centric Consulting, puts product manager roles down 30% overall and says the number of product builders has nearly tripled. Treat the exact figures with care, but the direction is clear. Product builders come from all three backgrounds: engineers learning product, designers learning code, PMs learning to ship.
4. GTM engineer (marketing ops + sales development + developer)
"Go-to-market engineer" barely existed three years ago. Clay says it coined the term in 2023. The role builds the machinery of selling: data that finds the right prospects, automations that research and personalise outreach, and systems that turn a hunch into a test campaign in a day. Norwest's hiring data ties the rise of these technical marketing roles to a fall in hiring of sales development reps, as manual outbound gets automated. Expect "marketer who can code" to stop being a rare combination and start being the job description.
5. Forward-deployed engineer (solutions consultant + engineer + account manager)
Made famous by Palantir and now common at AI companies, this is an engineer who sits with the customer, understands their mess and builds the solution on site. One 2026 guide describes the role as "half engineering, half product, half consulting". As every business tries to fit AI into its own processes, the person who can both listen and build becomes far more valuable than a salesperson and an engineer passing notes.
6. Creative technologist (creative director + designer + editor + automation)
Today a campaign might need a creative director, a designer, a video editor and a copywriter. Tomorrow it needs one person with taste who directs the idea and builds the pipeline that produces it. We see this in our own work: our script-to-video pipeline turns one written script into finished, branded videos, and every blog cover on this site is directed by a person and produced with AI to a locked style. The craft doesn't disappear. It moves from making each asset by hand to designing the system that makes them, and judging what comes out.
7. Agent operations lead (operations manager + process analyst + automation engineer)
This is the furthest out, and in our view the biggest. Operations managers today manage people doing tasks. As AI agents take on more of those tasks (answering enquiries, processing orders, reconciling payments), someone has to design the workflows, watch the agents, catch their mistakes and decide when a human steps in. That person needs an ops manager's sense of how a business runs, an analyst's eye for where a process breaks, and enough technical skill to fix it. Few companies hire for this today. Most will within a few years.
The role above them all: the company architect
Look at the seven roles together and a pattern appears. Each merged role trades hands-on execution for systems thinking: deciding what should happen, setting the standard, and checking the output.
Take that to its limit and you get one person running a whole company. Anthropic's CEO Dario Amodei has predicted the first one-person billion-dollar company, with AI doing the work of the staff. Whether that arrives this year or later, the shape of the role is already visible: an architect who designs the business as a system, leads AI as the workforce and guards quality, brand and the customer relationship personally.
This is not "the AI runs the company". The architect is the reason the company is any good. AI follows a clear vision brilliantly and invents a good one rarely. The judgement stays human. That's a subject for our next post.
Is everything really merging into one job?
No, and it's worth being honest about this. Atlassian's Sherif Mansour argues that the popular framing, that "these roles are merging into one", leads many teams to the wrong conclusions. Large organisations still need deep specialists: the security engineer, the brand strategist, the database expert.
What we think happens is this. The merge shows up first in startups and small businesses, where one person covering three roles is the difference between affordable and not. Big companies follow later and more slowly, keeping specialists for the hardest problems. That is good news for small businesses in Nigeria and everywhere else. The leverage that used to need a team of ten is now within reach of a team of two.
How do you get ahead of the merge?
- Pick a neighbour. Look at the role next to yours, the one you hand work to or receive work from. Learn enough of it to do the routine parts yourself, with AI.
- Keep the judgement, delegate the execution. Your value is in deciding what good looks like. Let AI do the first draft and spend your time on the decisions it can't make.
- Build systems, not just outputs. A designer who ships one graphic is replaceable. A designer who builds a pipeline that ships a hundred on-brand graphics is not.
- Hire for range. If you're building a team, a person who spans two roles with AI will often outperform two specialists passing work back and forth.
We run Sylva Studio this way: design, engineering and AI pipelines held by a small team, with AI doing the heavy lifting under a clear direction. If you want help designing that kind of workflow for your own business, that's the work we do.
