AI exposure: Architectural and Engineering Managers

37.9% of this occupation's weighted task load is exposed, which puts Architectural and Engineering Managers at the 67th percentile of 923 occupations. The capability is largely there. Its average task scores 2.6 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 19 tasks it averages 2.19 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 Assess project feasibility by analyzing technology, resource needs, or market demand, at 75.6%. The least is Manage the coordination and overall integration of technical activities in architecture or..., at 6.7%. A gap of 68.9% 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 management occupations, this one is less exposed than the median of 41.4% across the group's 56 roles, with 39 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 19 tasks, 15 are currently banded exposed, 2 assisted and 2 untouched. For that distribution to shift materially would take cheaper ways to verify output, since the cost of checking is currently doing more to hold this work in place than the cost of producing it. The score is re-computed every quarter against a fresh capability reference, and the change is published rather than quietly applied.