AI's Impact on Tech Jobs: The Paradox of 8/10 Exposure and +25% Growth

A senior engineer at a mid-sized SaaS company told me something last month that stuck. He'd just read that software developers score 8 out of 10 on AI exposure. His first thought: "I'm cooked." His second thought, when he checked the BLS outlook: "Wait, +25% growth through 2032?"

Both facts are true. That's the problem.

Most conversations about AI tech jobs collapse into one of two camps: "AI will take everything" or "AI just creates more jobs." Neither camp is wrong. Both are incomplete. The data tells a more precise, more uncomfortable story.

A 10-point exposure score doesn't mean your job disappears. It means your job transforms. And transformation has winners and losers inside the same title.

Here's the one that makes people uncomfortable.

You think your degree protects you. You think your salary signals safety. The data says the opposite. Jobs paying $100K+ average an AI exposure score of 6.7. Jobs under $35K average 3.4. The higher your income, the more of your work is already automatable.

The plumber isn't worried. The HVAC technician isn't worried. They score 0-2. They work in physical space, with their hands, in non-repeatable conditions. AI can't unblock a drain or replace a condenser coil. 42% of Gen Z is already routing toward trades, and this data tells you why.

Meanwhile, the software developer AI growth story hides a second-order effect that's more immediate. Look one level below the title.

A VP of Sales scores 6. The SDRs under them score 8. The tasks AI takes first are the ones at the bottom of the org chart: the outreach, the qualification, the pipeline building. The manager's job survives. The entry-level path into that manager job gets restructured before you ever get there.

The global average AI exposure score is 5.3 out of 10. That's not a crisis number. It's a pressure number. Enough to reshape careers. Not enough to eliminate most of them. The window is still open. But it's narrowing at different speeds for different roles.

The tech career AI question isn't "will I be replaced?" It's "what does my role look like in 3 years, and am I building toward that version or the version that gets restructured away?"

Here's what the data points toward, practically:

• AI skills command a 56% salary premium right now. The leverage is available to anyone willing to develop it. That premium exists because supply of AI-fluent workers is still behind demand.
• Score 7-8 means 2-3 years of runway. Not urgency measured in weeks. Urgency measured in the career decisions you make this year and next. That's still actionable time.
• Score 9-10 is a different conversation entirely. Medical transcription, basic data entry, templated writing. If your core value is doing the thing AI now does faster and cheaper, the runway is shorter than 2 years.
• Move toward judgment, not just execution. The tasks that survive automation are the ones that require context, ambiguity, accountability. The developer who can architect. The analyst who can present to the board. The clinician who makes the call.

Software developers score 8-9 on AI exposure. They also face +25% job growth. Both facts are true. The paradox resolves when you understand that high exposure plus expanding demand equals restructuring, not elimination.

The score tells you how much AI touches the work. It doesn't tell you what happens to demand for the work when it does. Those are two completely different questions.

Medical transcriptionists score 10 and the outlook is -8%. Software developers score 8-9 and the outlook is +25%. Same high exposure. Opposite futures. The difference is whether AI is a cost-cutter or a capacity-expander for the work you do.

Know your score. Then ask the harder question: when AI handles more of the routine work, does the world need more or fewer people doing your job?

The score is the map. The demand question is the territory.