Is 30 Too Old to Switch Into Tech in the AI Era?
Five years ago this article would've written itself: do a bootcamp, build a portfolio, get a junior dev job, double your salary. Thousands of people ran exactly that play and it worked. If you're reading advice like that today — and the internet is still full of it — you're reading a trail map for a mountain that's been renovated.
What actually changed
Companies freezing entry-level hiring due to AI: 21%, another 15% expected
The classic target of that freeze: junior developer roles — the exact rung career-changers used to land on
Tech layoffs Q1 2026: ~80,000, roughly half attributed to AI
The honest sentence: the "learn to code, get a junior job" pipeline is the single most AI-damaged career path in the economy. AI writes competent junior-level code, so companies buy fewer juniors. Anyone selling you the 2019 bootcamp dream without mentioning this is selling expired inventory.
Why this isn't a character flaw — and isn't the end
If you spent your late twenties building toward a switch that just got harder, nothing about that was stupid; the rules changed mid-game, again, as they have for this generation approximately every five years. But notice what the data above actually says: the junior rung broke. Not the industry. Tech still hires — it's hiring different shapes of people. And "30 with a decade of domain experience" happens to be one of the shapes.
The current map (three honest routes)
- Route 1 — Domain + tech, not tech instead of domain. The most defensible seat in the AI era is "person who deeply knows an industry AND can wield the tools." A logistics manager who can build AI workflows beats a 24-year-old CS grad in logistics, every time. Your 8 years in healthcare/finance/retail/ops — the thing you were about to write off — is the moat. Add the technical layer on top of it, don't trade it in.
- Route 2 — The AI-adjacent roles that are growing while coding shrinks. Implementation, integration, AI operations, data work inside non-tech companies, prompt-and-workflow engineering for actual business processes. Less glamorous than "software engineer," less crowded, and hiring from exactly your profile: adults who can talk to both the machine and the VP.
- Route 3 — Classic engineering, eyes open. Still possible — but the bar is higher and the differentiator is shipped, real projects (not portfolio to-do apps) plus the network. Choose this only if you'd build things anyway on a Saturday. Passion covers the harder road; salary math alone no longer does.
Write one sentence: "I know [your industry] and I'm learning to automate it." That's your positioning — now fund it with the 90-day test: one structured, credential-bearing course aimed at Route 1 or 2 (Coursera*'s AI and data certificates from Google/IBM/universities fit exactly this), five hours a week, plus one build that solves a real problem at your current job. Solving a real problem where you already work is the cheat code the 22-year-olds can't use: it's a portfolio piece, a promotion case, and an escape pod, all in one artifact.
Too old? You're arriving precisely when the industry stopped paying for youth and started paying for judgment. Terrible time to be 22. Interesting time to be 30.
*Affiliate link — commission to us, no cost to you. Free curricula exist (and are good); the certificate mostly buys structure and a line recruiters recognize.