Automation index

How much of a Blockchain developer’s job can AI already do?

A contract comes earlier. It not taking the money without deploying without an audit do not.

This percentage does not predict how many people will lose their jobs.

Task comparison

IS WORK OVER?

27%

AI can already do 27% of this job.

#152 / 763

Blockchain developer

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

Task	Share	AI	Points
Contract, the test and the invariant. Estimate No public source provides a precise figure. This is our estimate.	18%	48%	+8.6
Gas, the path and the one that spikes. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
Audit, the finding and not deploying anyway. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
Key, the multisig and not leaving it on a laptop. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
The client, the rush and not selling cheap immutability. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
That it does not take the money, and not deploying without an audit. Estimate No public source provides a precise figure. This is our estimate.	16%	12%	+1.9
Total	100%		27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low

IS WORK OVER?

27%

#151 / 763

Backend developer

Task weights are our estimates based on O*NET frequency data, not time shares published by O*NET.

The time saving for each task is estimated separately.

Task	Share	AI	Points
Endpoint, the contract and the test. Estimate No public source provides a precise figure. This is our estimate.	18%	48%	+8.6
Spike, the queue and the one that drops. Estimate No public source provides a precise figure. This is our estimate.	16%	40%	+6.4
Key, the secret and not leaving it in the repo. Estimate No public source provides a precise figure. This is our estimate.	16%	22%	+3.5
Migration, the rollback and not improvising in prod. Estimate No public source provides a precise figure. This is our estimate.	16%	28%	+4.5
Product, the deadline and not cutting the one that matters. Estimate No public source provides a precise figure. This is our estimate.	18%	14%	+2.5
That it takes the spike, and not leaving the key. Estimate No public source provides a precise figure. This is our estimate.	16%	12%	+1.9
Total	100%		27%

Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low