Let’s talk about the tech jobs AI is going to eat alive.
Not all of them.
That would be lazy to say, and mostly wrong.
The mistake people make is they argue about job titles. Developer. Designer. Analyst. QA tester. Product manager. Support engineer. Recruiter. Copywriter.
That is the wrong layer.
AI does not eat titles first. It eats tasks.
It eats the parts of a job that are repeatable, low-context, low-trust, easy to check, and already half-automated by templates, dashboards, tickets, spreadsheets, or Jira rituals.
And once enough tasks disappear, the title becomes a costume.
Someone still has the job on LinkedIn. The company still uses the same words. But underneath, the economic reason for that seat has changed.
That is the part people are missing.
There is a person somewhere right now whose entire week is made of small, clean, predictable digital chores.
Take this bug. Reproduce it. Write the ticket. Add the test. Update the docs. Summarize the meeting. Move the card. Pull the report. Check the logs. Draft the email. Clean the data. Rewrite the copy. Compare the vendors. Triage the queue.
None of those things feels like a whole career when you say it out loud.
But for a lot of tech workers, that is the actual job.
And AI is extremely good at that kind of work because that work was already shaped like machine food.
Clean input. Clear pattern. Expected output. Low emotional stakes. Easy review.
The jobs in danger are not “technical jobs.”
The jobs in danger are the ones where the worker has become the integration layer between tools.
Copying from one system into another.
Turning a meeting into bullet points.
Turning bullet points into tickets.
Turning tickets into status updates.
Turning status updates into a slide.
Turning the slide into a message so a manager can feel informed without making a decision.
That is not a profession. That is connective tissue.
And software is coming for connective tissue with a knife.
Start with junior developers.
This is the obvious one, but people still talk about it badly.
AI is not replacing excellent engineers who understand systems, customers, constraints, tradeoffs, failure modes, security, data, deployment, and business risk.
It is replacing the bottom layer of coding work that companies used to give to juniors so they could learn.
Small tickets. Boilerplate. CRUD screens. Test scaffolding. Refactors with obvious patterns. Conversion work. Migration work. Simple API wrappers. Documentation from code.
That work was never worthless. It was how people got good.
That is the dangerous part.
AI may not destroy senior engineering immediately. But it can destroy the training ladder underneath it.
If a company can get one senior engineer plus AI tools to do what three juniors used to do, the spreadsheet will look wonderful for a few quarters.
Then, five years later, everyone will wonder why there are no strong mid-level engineers.
The machine did not just automate work.
It ate apprenticeship.
Next: QA testers who only click through predictable scripts.
If your job is to manually run the same regression checklist, compare expected and actual output, and log obvious bugs, AI and automation are going to make that seat hard to defend.
But the tester who understands risk, weird user behaviour, broken incentives, edge cases, payments, privacy, medical data, security, and the places software lies to itself — that person is not obsolete.
That person becomes more valuable.
The checkbox tester is exposed.
The adversarial thinker survives.
There is a difference.
Support roles are next, especially tier-one technical support.
Password resets. Basic troubleshooting. “Have you tried this?” flows. Status checks. Common integration questions. Refund explanations. Knowledge-base answers.
AI will eat a lot of that.
Not because customers love bots. They mostly do not.
But because companies love reducing queues, and customers have been trained to tolerate bad support for years.
The support people who survive are the ones who can handle ambiguity, anger, context, escalation, trust, and real account ownership.
The person who says, “I see what happened, here is the actual issue, here is what I am doing about it,” is not the same as a chatbot pretending to care.
But the person who pastes template reply number seven into ticket number four hundred and twelve is in trouble.
Then there are data analysts.
This one will hurt because it sounds high-status.
But a lot of analyst work is not analysis. It is report assembly.
Pull numbers. Clean columns. Make a chart. Compare week-on-week. Write three sentences about why the line moved. Put it into a dashboard. Send it every Monday.
AI will eat that alive.
The analyst who survives is not the one who can make a prettier graph.
It is the one who can say, “This number is misleading. The metric is being gamed. The cohort is wrong. The sales team changed behaviour. The data pipeline broke. The customer story does not match the dashboard.”
That is not reporting.
That is judgment.
And judgment is still expensive because it requires context and the courage to say the dashboard is not telling the truth.
Product managers are exposed too, but not in the way they think.
AI will not replace the rare product person who can find a sharp customer pain, make hard tradeoffs, say no, align a team, simplify a mess, and ship something people actually want.
That person is scarce.
AI will replace the product manager whose job is mostly ceremony.
Write the PRD. Summarize the customer calls. Update the roadmap. Rephrase engineering notes. Make priority slides. Host meetings where nothing gets decided. Translate one department’s vagueness into another department’s backlog.
If your leverage is theatre, AI will expose it.
If your leverage is judgment, taste, distribution sense, customer contact, and decision-making, AI becomes a weapon in your hands.
Design has the same split.
AI will eat the production layer first.
Resize this. Generate ten variants. Make the placeholder graphic. Clean the background. Draft the landing page. Mock the app screen. Create the ad concept. Turn this wireframe into something acceptable.
Acceptable is the keyword.
AI is very dangerous to people whose value is “acceptable.”
The designer who survives has taste. Real taste. The ability to feel when something is cheap, crowded, dishonest, boring, confusing, or emotionally dead.
The designer who can shape desire, trust, clarity, and the whole experience is not the same thing as someone producing screens.
Screens are getting cheaper.
Taste is not.
Recruiting will also be hit hard.
Resume screening. Candidate matching. Outreach drafts. Interview scheduling. Job descriptions. First-round summaries. Basic qualification.
That whole layer is automation bait.
But again, the human version that survives is not the admin layer.
It is the recruiter who knows how to read between lines, sell a role honestly, protect a company from false positives, understand team dynamics, and notice when someone looks perfect on paper but will quietly poison the room.
AI can rank candidates.
It cannot yet carry reputational trust in a market.
That matters.
Technical writing is another one.
If the job is mostly turning product notes into clean documentation, AI will compress that work heavily.
It can read code. It can summarize APIs. It can create first drafts. It can turn a messy explanation into a usable guide.
But the technical writer who understands what a confused human actually needs at 2 a.m. when production is broken — that person still matters.
Good documentation is not just accurate.
It is merciful.
It knows where the reader will panic, misunderstand, skip a step, or blame themselves.
AI can generate documentation.
A good human can make it humane.
And then there is the big category nobody wants to name: coordinators.
Project coordinators. Operations coordinators. Marketing coordinators. Engineering coordinators. Customer success coordinators.
Some of these people are excellent. They are the ones who actually know where the bodies are buried, who owes what, which client is angry, which deadline is fake, which vendor is unreliable, and which executive is pretending not to know.
Those people are valuable.
But the role itself is exposed because so much coordination work is status transfer.
Ask for update. Summarize update. Chase missing update. Put update in tracker. Remind everyone about update. Create meeting about missing update.
AI agents are being built exactly for that world.
Not because they are wise.
Because the work is shallow enough to automate.
So what survives?
Not “being human” in a vague inspirational sense.
That is too soft.
What survives is human advantage in places where the work is messy, high-context, relational, risky, physical, taste-driven, morally loaded, or commercially sharp.
People who can sell.
People who can persuade without lying.
People who can understand a customer before the customer has language for the problem.
People who can make hard tradeoffs.
People who can own outcomes, not just outputs.
People who can sit in ambiguity without immediately turning it into a template.
People who can decide what should not be automated.
That last one matters more than people think.
In the next few years, companies will automate plenty of things they should not automate.
They will automate support moments where the customer needed trust.
They will automate hiring steps where judgment mattered.
They will automate creative work until the brand looks like everybody else.
They will automate analysis until nobody notices the metric is lying.
They will automate junior work and then act surprised when the talent pipeline dries up.
This is the trap.
AI makes cheap work almost free.
But cheap work was sometimes where humans learned, relationships formed, trust was repaired, and taste developed.
If we remove every small human step because the spreadsheet says it is inefficient, we may end up with companies that are faster, cheaper, and strangely hollow.
Very efficient machines with nobody inside who knows why the work matters.
That is the line WE ARE STILL HUMAN keeps coming back to.
The question is not whether AI can do the task.
Many times it can.
The question is what disappears when the human is removed from that task.
Does trust disappear?
Does apprenticeship disappear?
Does accountability disappear?
Does taste disappear?
Does the customer become a ticket instead of a person?
Does the worker become a prompt operator with no path to mastery?
That is the real danger.
Not that AI takes every job.
That is too crude.
The danger is that it hollows out the bottom, compresses the middle, rewards the top, and leaves millions of people with job titles that sound familiar but no longer contain the same ladder, dignity, or bargaining power.
So yes, beware.
If your job is mostly moving information between systems, writing predictable first drafts, summarizing what other people said, checking boxes, producing acceptable variants, or maintaining the theatre of coordination, AI is coming straight at you.
Not eventually.
Now.
But if your work is rooted in judgment, trust, taste, responsibility, courage, customer contact, and real ownership, the machine is not your replacement.
It is pressure.
It will expose the parts of your work that were weak.
It will make the average version of your job cheaper.
And it will force the strong version to become sharper.
The future will not be divided between technical people and non-technical people.
It will be divided between people who merely process work, and people who can be trusted with consequences.
That is the job AI cannot eat so easily.
The person who carries consequences.
The person who knows what the work is for.
The person who can look at the machine, use it well, and still say:
No. Not there.
A human needs to hold this part.