AI exposure: Database Architects

Database Architects sits in the top 3% of every occupation measured. 63.4% of what this job consists of, weighted by how important each task is to the role, is work current AI systems can produce with little standing in the way. Very few occupations score this high. The ones that do tend to share a trait: the output is a document, a calculation or a message, and nobody has to be in a particular room for it to count.

What holds the line here is context. Across this occupation's 25 tasks it averages 1.90 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 Identify and evaluate industry trends in database systems to serve as a source of information..., at 83.3%. The least is Work as part of a project team to coordinate database development and determine project scope..., at 26.7%. A gap of 56.7% 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 more exposed than most. The median across the 36 roles in the group is 56.7%, and only 9 of them score higher than this. Occupational families are not uniform, and the spread inside them is often wider than the gap between them.

What would move this score. Of 25 tasks, 25 are currently banded exposed, 0 assisted and 0 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.