AI exposure: Computer Systems Engineers/Architects

51.3% of this occupation's weighted task load is exposed, which puts Computer Systems Engineers/Architects at the 89th percentile of 923 occupations. The capability is largely there. Its average task scores 3.1 out of 4 on what a current system can produce, and the frictions that hold other jobs in place are comparatively weak here.

What holds the line here is context. Across this occupation's 28 tasks it averages 1.95 out of 3, the highest of the five friction dimensions. In plain terms, the work depends on knowledge the model cannot hold. Much of this job runs on things that were never written down: what this particular organisation does, what happened last week, what the person across the table actually meant. That context is the barrier, and it erodes as systems are given more access.

The most exposed thing this job does is Monitor system operation to detect potential problems, at 80.0%. The least is Perform ongoing hardware and software maintenance operations, at 21.5%. A gap of 58.5% between two parts of the same job is the reason this index publishes at task level. An occupation-wide number would have hidden both.

Within computer and mathematical occupations, this one is less exposed than the median of 57.8% across the group's 36 roles, with 26 scoring higher. Being in an exposed family does not make a particular job exposed, and the reverse holds too.

What would move this score. Of 28 tasks, 27 are currently banded exposed, 0 assisted and 1 untouched. For that distribution to shift materially would take systems being given deeper access to the organisation's own records and history, which is already happening. The score is re-computed every quarter against a fresh capability reference, and the change is published rather than quietly applied.