IS WORK OVER?

Automation index

How much of a Data architect’s job can AI already do?

A lake diagram comes earlier. Data that can be used, and does not rot, do not.

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

Task comparison

Data architect

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.

TaskShareAIPoints
Models, lineage and the catalogue.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Pipelines, quality and the data contract.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
The analyst who finds nothing and the mess.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Privacy, retention and the field you cannot keep.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
The business, shadow IT and not building another lake.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it gets used, and not letting raw data rot.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%28%

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

Skills and activities

  • model data
  • lineage
  • data catalogue
  • data contracts
  • pipeline quality
  • retention
  • data lakes
  • privacy

Sources for this job· O*NET 15-1243.00· ESCO/ISCO 2511

Technical writer

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.

TaskShareAIPoints
Structure, API docs and the tutorial.
Estimate

No public source provides a precise figure. This is our estimate.

18%52%+9.4
Screenshots, versions and not leaving the old shot.
Estimate

No public source provides a precise figure. This is our estimate.

16%40%+6.4
The engineer who will not write, and extracting the how.
Estimate

No public source provides a precise figure. This is our estimate.

16%22%+3.5
Legal review, i18n and the changelog.
Estimate

No public source provides a precise figure. This is our estimate.

16%28%+4.5
Support, the tickets and what the doc misses.
Estimate

No public source provides a precise figure. This is our estimate.

18%14%+2.5
That it can be installed, and not documenting thin air.
Estimate

No public source provides a precise figure. This is our estimate.

16%12%+1.9
Total100%28%

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

Skills and activities

  • document APIs
  • product tutorials
  • screenshots
  • changelogs
  • extract knowledge
  • docs i18n
  • version review
  • support tickets

Sources for this job· O*NET 27-3042.00· ESCO/ISCO 2641

Analyse my job

Jobs with similar scores

  1. 80SOC analyst28%
  2. 81Architect28%
  3. 82Cloud architect28%
  4. 84Barista28%
  5. 85Bank teller28%
  6. 86Waiter28%