Automation index
How much of a Database administrator’s job can AI already do?
An explain plan and a backup script write. Recovering a corrupt database on a Sunday does not.
This percentage does not predict how many people will lose their jobs.
Task comparison
IS WORK OVER?
Database administrator
28%
AI can already do 28% of this job.
#76 / 763
View rankingDatabase administrator
Where the time goes
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 |
|---|---|---|---|
Tuning, indexes and execution plans.EstimateNo public source provides a precise figure. This is our estimate. | 22% | 48% | +10.6 |
Backups, jobs and docs.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 42% | +7.6 |
Incidents, locks and restores.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 20% | +3.2 |
Schema changes with development.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 15% | +2.4 |
Permissions, audit and PII.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 18% | +2.5 |
Capacity, cost and engine choice.EstimateNo public source provides a precise figure. This is our estimate. | 14% | 16% | +2.2 |
| Total | 100% | 28% |
Modelled workweek: 100% · Public evidence: 0% · Estimate: 100% · Confidence: Low
Skills and activities
- Tuning, indexes and execution plans
- Backups, jobs and docs
- Incidents, locks and restores
- Schema changes with development
- Permissions, audit and PII
- Capacity, cost and engine choice
- dba
- administrador de base de datos
- oracle dba
Sources for this job· O*NET 15-1242.00· ESCO/ISCO 2521
IS WORK OVER?
Backend developer
27%
#151 / 763
View rankingBackend developer
Where the time goes
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.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 48% | +8.6 |
Spike, the queue and the one that drops.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 40% | +6.4 |
Key, the secret and not leaving it in the repo.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 22% | +3.5 |
Migration, the rollback and not improvising in prod.EstimateNo public source provides a precise figure. This is our estimate. | 16% | 28% | +4.5 |
Product, the deadline and not cutting the one that matters.EstimateNo public source provides a precise figure. This is our estimate. | 18% | 14% | +2.5 |
That it takes the spike, and not leaving the key.EstimateNo 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
Skills and activities
- endpoints
- API contracts
- queues
- secrets
- migrations
- rollback
- backend tests
- write server code
Sources for this job· O*NET 15-1252.00· ESCO/ISCO 2512