AI exposure: Blockchain Engineers

53.0% of this occupation's weighted task load is exposed, which puts Blockchain Engineers at the 91th percentile of 923 occupations. The capability is largely there. Its average task scores 3.2 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 17 tasks it averages 1.97 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 Evaluate blockchain processes or risks based on security assessments or control matrix reviews, at 73.3%. The least is Update client and server applications responsible for integration and business logic, at 26.7%. A gap of 46.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 less exposed than the median of 57.8% across the group's 36 roles, with 22 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 17 tasks, 16 are currently banded exposed, 1 assisted and 0 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.