The Task Exposure Indexv2026.Q3
Occupation · SOC 15-1243.01 · Job Zone 4

AI exposure: Data Warehousing Specialists

Design, model, or implement corporate data warehousing activities. Program and configure warehouses of database information and provide support to warehouse users.

Reading this score

computed

Data Warehousing Specialists sits in the top 2% of every occupation measured. 65.2% 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 18 tasks it averages 2.01 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 Develop data warehouse process models, at 73.3%. The least is Implement business rules via stored procedures, middleware, or other technologies, at 35.4%. A gap of 37.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 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 7 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 18 tasks, 18 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.

Task by task

18 tasks, O*NET 31.0
TaskExposedAssistedUntouchedImportanceBand
Develop data warehouse process models, including sourcing, loading, transformation, and extraction.73.3%26.7%0.0%4.43exposed
Verify the structure, accuracy, or quality of warehouse data.73.3%26.7%0.0%4.43exposed
Map data between source systems, data warehouses, and data marts.73.3%26.7%0.0%4.22exposed
Develop and implement data extraction procedures from other systems, such as administration, billing, or claims.73.3%26.7%0.0%4.13exposed
Design and implement warehouse database structures.73.3%26.7%0.0%4.09exposed
Develop or maintain standards, such as organization, structure, or nomenclature, for the design of data warehouse elements, such as data architectures, models, tools, and databases.73.3%26.7%0.0%3.95exposed
Design, implement, or operate comprehensive data warehouse systems to balance optimization of data access with batch loading and resource utilization factors, according to customer requirements.73.3%26.7%0.0%3.86exposed
Create supporting documentation, such as metadata and diagrams of entity relationships, business processes, and process flow.73.3%26.7%0.0%3.78exposed
Create or implement metadata processes and frameworks.73.3%26.7%0.0%3.71exposed
Select methods, techniques, or criteria for data warehousing evaluative procedures.73.3%26.7%0.0%3.59exposed
Prepare functional or technical documentation for data warehouses.73.3%26.7%0.0%3.32exposed
Perform system analysis, data analysis or programming, using a variety of computer languages and procedures.69.3%22.4%8.3%3.83exposed
Write new programs or modify existing programs to meet customer requirements, using current programming languages and technologies.57.4%25.9%16.7%3.91exposed
Test software systems or applications for software enhancements or new products.55.0%20.0%25.0%3.15exposed
Provide or coordinate troubleshooting support for data warehouses.50.0%25.0%25.0%3.91exposed
Review designs, codes, test plans, or documentation to ensure quality.45.0%30.0%25.0%3.64exposed
Create plans, test files, and scripts for data warehouse testing, ranging from unit to integration testing.45.0%30.0%25.0%3.61exposed
Implement business rules via stored procedures, middleware, or other technologies.35.4%27.1%37.5%3.55exposed

Task text and importance ratings sourced from O*NET 31.0. Shares computed. The occupation score is the importance-weighted mean.

Where the score comes from

judged

Every task is scored through the standardised work activities it maps to. These are this occupation’s averages on the six rubric dimensions. Capability is what AI can do; the other five are what stands in the way.

DimensionMeanScale
Capability3.640-4
Embodiment0.140-3
Presence0.030-3
Accountability1.000-3
Context2.010-3
Verification cost1.260-3

What this means in practice

Where most of a role's weighted task load is exposed, the work that survives is usually the part of the job nobody wrote into the job description: deciding what should be produced rather than producing it, and being answerable for the result. The tasks lowest on this page are a better guide to where to spend your time than any general advice about the future of work.

Occupations either side of this one

The four closest scores in the same occupational family, then the four closest anywhere in the index.

Read this carefully. Exposure is not displacement. A high score means current AI systems can produce this work, not that anyone will stop paying a person to do it. Adoption depends on economics, regulation and inertia that this index deliberately does not model. How the score is built.