IS WORK OVER?

Automation index

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

A diagram and an ADR come earlier. A system that holds, and a team that gets it, do not.

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

Task comparison

Software 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
Diagrams, ADRs and proofs of concept.
Estimate

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

18%40%+7.2
Review PRs, APIs and boundaries.
Estimate

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

16%32%+5.1
Team, product and trade-offs.
Estimate

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

18%22%+4
Big incidents and technical debt.
Estimate

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

16%18%+2.9
Security, cost and observability.
Estimate

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

16%16%+2.6
Not designing a castle nobody can run.
Estimate

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

16%14%+2.2
Total100%24%

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

Skills and activities

  • write code
  • programming
  • software development
  • coding
  • debug code
  • building plans
  • renders
  • sign a project
  • Diagrams, ADRs and proofs of concept
  • Review PRs, APIs and boundaries

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

Backend 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.

TaskShareAIPoints
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
Total100%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

Analyse my job

Jobs with similar scores

  1. 301Property manager24%
  2. 302Community health worker24%
  3. 303Agile coach24%
  4. 305Biochemist24%
  5. 306Parking attendant24%
  6. 307Probation officer24%