Roles That Are Shrinking
Qa
Manual QA is down. Test automation, AI-assisted QA, and quality engineering are up. Pivot there.
Tech Writer
Generic docs are automated. Technical depth, developer experience, and product docs still need humans.
Support Eng
Tier-1 is shrinking. Tier-2, escalation, and implementation grow. Specialize up.
Roles That Are Shrinking
TL;DR
- McKinsey: up to 30% of work hours automated by 2030. IMF: 40% of jobs affected (60% in advanced economies). WEF: 92M displaced, 170M created—net +78M, but 39% of skills must change.
- Shrinking: generic QA, entry-level dev, routine tech writing, tier-1 support. Repetitive, well-defined work goes first. Shrinking ≠ dead. Transition paths exist.
- Honest assessment helps you plan. Denial doesn't.
We're not dooming. We're mapping. ~55K layoffs in 2025 were blamed on AI—often "AI-washing" of financially motivated cuts. But the vector is real. If you're in a contracting area, shift before you're forced.
Roles With Declining Demand
| Role | Why | Transition Path |
|---|---|---|
| Manual QA | AI writes tests. Automation handles regression. | Test automation, SDET, quality engineering, or move to dev |
| Entry-level generic dev | AI does boilerplate. Juniors who can't direct AI struggle. | Add AI tooling, specialize (frontend/backend/data), show initiative |
| Routine tech writing | AI drafts docs. Generic tutorials are commoditized. | Deep technical docs, API design, developer experience |
| Tier-1 support | Chatbots handle FAQs. | Tier-2, implementation, solutions engineering |
| Pure implementation (no product sense) | AI implements. Humans who only code-to-spec are replaced first. | Product thinking, system design, ownership |
The Pattern
Work that is repetitive, well-defined, and low-context is automating first. Work that is ambiguous, high-context, or requires judgment stays human-longer. Research: >70% of skills employers seek remain relevant; 12% stay entirely human. The shift isn't wholesale—it's selective. Know which side you're on.
Transition Tactics
- Add the adjacent skill. QA → test automation. Support → solutions. Writer → developer experience.
- Own outcomes, not tasks. "I ensure quality" > "I run test cases."
- Get closer to the product or customer. Implementation → product. Support → success or sales eng.
The Timeline Question
Nobody knows exactly when any role will "fully" contract. The point isn't to panic — it's to see the vector. If your role is in the shrinking list, start the transition now. You have more optionality when you're employed and learning than when you're forced.
Manual QA. Run test cases. Entry-level dev doing boilerplate. Tier-1 support answering FAQs. Routine tech writing. Repetitive, well-defined work.
Click "Transition paths" to see the difference →
Quick Check
Your work is repetitive and well-defined. What's the best move?
Do This Next
- Assess your role — Is your work repetitive and well-defined? Or ambiguous and judgment-heavy? >70% of skills stay relevant; 12% stay entirely human. Which side are you on?
- Map one transition — What's the closest "growing" role (lesson 2)? Data Engineer, MLOps, Solutions Architect—what skill do you add?
- Take one step — One project (RAG, automation, quality eng), one course, or one internal move. Start the pivot. You have more optionality when employed.