EXPOSED
The reporting layer of this job — status decks, budget variance write-ups, vendor comparison matrices, incident postmortems, capacity forecasts, ticket-trend analysis — is already drafted well by AI, and that is a real share of an IT manager's week. What persists is owning consequential calls under ambiguity: which platform bet to make, whether to accept a security risk, who to hire and fire, and standing in front of executives when a migration or breach goes badly. No license protects the role, and as AI compresses the engineering teams below them, the layer of managers needed to coordinate those teams thins too.
Headcount grew steadily across the period.
Median pay $146,360 → $175,140 -4.3% in real terms
This line is counted by the Bureau of Labor Statistics — the one figure on this page that isn't a judgement of ours. Headcount moves on demand, offshoring, demographics and the business cycle, and automation is one term among several, often not the loudest.
So a falling line is not evidence that AI did it, and a rising one is not evidence that it won't. Both happen in this register: some occupations resist automation and shrink anyway, others are highly automatable and keep growing. The marked year is 2020.
BLS projection, 2024–2034
+15.2% 667,100 → 768,700 on the projections basis
Exposed, but growing
AI can already do a lot of these tasks, and the BLS still expects +15.2% more of these jobs by 2034. Demand for the output is growing faster than the work is being automated away — the mechanism BLS gives for software developers, and the combination people most often misread as an error.
Different clocks. The score is what current AI could do to this work today. The projection is how many of these jobs will exist in 2034. Everything between the two — how fast employers actually adopt, whether demand grows in the meantime — is why they can point opposite ways without either being wrong.
~55,600 openings a year on average, including replacing people who leave.
Network ManagerNetwork DirectorKnowledge ManagerTechnical DirectorData Center ManagerDevelopment ManagerTechnology DirectorData Systems ManagerCyber Workforce ManagerData Processing ManagerProduct Support ManagerData Operations DirectorSoftware Project ManagerComputer Security ManagerProduct Solutions ManagerSystem Development ManagerTechnical Services ManagerComputer Operations ManagerComputing Services DirectorInternet Technology ManagerSystems Engineering ManagerComputer Programming ManagerInformation Security ManagerInformation Services Manager
Holding it up: judgment & accountability . Weakest point: embodiment .
Mixed — a routine tier and a judgment tier Roadmap prioritization, vendor negotiation, and headcount decisions still need a human in the room, but the surrounding load — SLA reporting, change-advisory-board documentation, on-call rotation planning, sprint summaries, RFP response scoring — is enough of the calendar to hold this at 11 rather than the mid-teens.
Fully desk- and screen-based The 3 reflects the rare walk to a data center or wiring closet during an outage; racking, cabling, and hardware swaps belong to the infrastructure staff, and this job is Slack, Jira dashboards, and executive meetings.
No licence, no signature requirement No state license gates the title — a CISSP or PMP is a hiring signal, not a legal barrier — and when SOX or HIPAA controls fail, the signature on the attestation is the CFO's or CISO's, leaving the 4 to reflect only that large enterprises still prefer credentialed candidates.
Exists to be accountable for ambiguous calls Accepting a documented security risk, killing a mid-flight ERP migration, deciding whether an incident is disclosable, and firing an underperformer are calls made with incomplete data where the manager's name is on the decision record — the 16 stops short of higher only because board-level capital allocation sits above them.
The verdict above describes this occupation as a whole. Almost nobody does the typical version of a job — tick what's actually in your week and see how your own mix sits.
Your task mix speaks to task resistance (11/20 here) — how much of the day's work current AI already does. That is the dimension the boxes above are about.
It cannot move the other three. Liability shield (4/20) is whether the law requires a licensed human to sign. Trust premium (10/20) is whether buyers specifically pay for a person. Judgment and accountability (16/20) is whether the role exists to own consequential calls. Those are facts about the occupation's standing, not about which tasks are in your week — a paralegal who does only trial exhibits still holds no licence. Together they are 30 of this occupation's 44 points (68%).
Embodiment (3/20) is also a property of the work rather than the worker, but we don't tag individual tasks as physical or not, so the picker can't tell you anything about it. That's a limit of this tool, not a claim.
Did we get the list right? Tell us what's missing — the tasks are written from the outside, and you're reading this from the inside.
No occupation passed every test: close enough to computer and information systems managers on skills and subject matter, at least 10 points more resistant, no big jump in training, no new licence, no pay cut, and not shrinking on its own. That happens for 223 of the 654 occupations here that aren't SAFE, and it is worth stating plainly rather than leaving the section off.
The usual reason is that exposure travels with the skill profile. The jobs most similar to yours tend to be exposed for the same reasons yours is, so the near neighbours don't clear the gap — and the ones that do are a different kind of work, not a transfer of what you already know. Read that as a limit of this method, not a verdict that you're stuck: it only compares whole occupations, and it cannot see specialisation, industry, or anything you'd bring that isn't in a federal skill survey.
Here is that claim on your own job rather than in the abstract. These are the three occupations closest to this one by skill and subject matter — the places the work would most naturally transfer — with what the register scores them:
That is the whole problem in three lines. The nearest work is not meaningfully safer, so there is no move here that trades a similar skill set for a better verdict. This is not us running out of ideas — it is what the neighbourhood looks like.
The moves above are yours to make. This is the other half: what would have to change in the world for the occupation itself to score higher. None of it is in any one person's gift, but it is where the floor actually comes from. Scores here are not a one-way ratchet. Only two of the five dimensions — task resistance and embodiment — track what machines can do. The other three track law, what buyers will pay for, and who is answerable, and those move in both directions, often in response to the same pressure AI creates. If every lever below landed, this occupation would score around 56/100, still EXPOSED.
SEC cyber disclosure rules (Item 1.05, effective Dec 2023) already force a named accountable officer for materiality determinations; if state or federal rules push personal attestation down from CISO/CFO to named systems managers — as NYDFS Part 500 amendments (Nov 2023) do by requiring a senior officer certification of compliance with documented sign-off from responsible IT leadership — the role acquires a genuine signature requirement
Genuine two-tier job: if the deck-and-variance-report tier is fully automated, the residual week is vendor negotiation, risk acceptance, headcount decisions, and incident command under executive pressure — none of which current models can perform because they require authority, not analysis. Watch for the manager-to-IC ratio and whether reporting duties disappear from job postings
EU AI Act obligations for high-risk system deployers (human oversight, logging, post-market monitoring) becoming contract-flowed requirements naming an internal accountable deployment owner, plus cyber-insurance underwriters requiring a named IT manager attestation on change-control and MFA posture as a condition of payout
Already near ceiling; would rise only if AI-agent governance (approving autonomous agents with production write access, owning their blast radius) becomes a formal named-owner duty under an internal control framework such as an updated COBIT/SOX ITGC scope
The limit. The structural risk is quantity, not per-role defensibility: judgment_accountability is already 16 and cannot carry the score if the number of manager slots halves as engineering teams compress. No plausible route to a higher trust_premium — buyers of internal IT management are executives who do not pay a premium for a human coordinator, only for someone who can be held responsible.
| New York-Newark-Jersey City, NY-NJ | 62,430 | $215,300 +23% |
| Dallas-Fort Worth-Arlington, TX | 30,690 | $173,810 -1% |
| Chicago-Naperville-Elgin, IL-IN | 24,950 | $173,760 -1% |
| San Francisco-Oakland-Fremont, CA | 23,830 | $232,890 +33% |
| Los Angeles-Long Beach-Anaheim, CA | 23,180 | $204,370 +17% |
| Washington-Arlington-Alexandria, DC-VA-MD-WV | 20,800 | $195,190 +11% |
| Boston-Cambridge-Newton, MA-NH | 20,530 | $214,960 +23% |
| San Jose-Sunnyvale-Santa Clara, CA | 19,070 | $291,660 +67% |
| San Jose-Sunnyvale-Santa Clara, CA | 19,070 | $291,660 +67% |
| San Francisco-Oakland-Fremont, CA | 23,830 | $232,890 +33% |
| New York-Newark-Jersey City, NY-NJ | 62,430 | $215,300 +23% |
We have no reported case of a named organisation automating this occupation. Not one deployment, not one announcement.
That is worth saying out loud next to a score of 44. The verdict above is about what the work exposes — what current AI could do to these tasks. It is not a claim that anyone has done it. For this occupation those two things have come apart completely: the capability argument is on this page, and the evidence column is empty.
Has AI actually changed your work? One tap, anonymous, and the running tally is public. Nothing else is asked of you.
Rather than check back: get the digest and we'll tell you what changed — or watch a single occupation from its own page.