IS WORK OVER?

Automation index

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

A development model comes earlier. Putting the building up and selling it without rows do not.

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

Task comparison

Property 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
Land, licence and the model.
Estimate

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

18%48%+8.6
Works, the builder and the one who is late.
Estimate

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

16%40%+6.4
Sell, the plan and the one who reserves.
Estimate

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

16%22%+3.5
Bank, the facility and the one that is cut.
Estimate

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

16%28%+4.5
Neighbours, the objection and not hiding the impact.
Estimate

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

18%14%+2.5
Put it up and sell without rows.
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

  • land
  • licences
  • development model
  • sell units
  • development finance
  • objections
  • reservations
  • the build

Sources for this job· O*NET 11-9021.00· ESCO/ISCO 3334

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. 207Teacher27%
  2. 208Driving instructor27%
  3. 209Driving theory instructor27%
  4. 211CAD designer27%
  5. 212Revenue manager27%
  6. 213School secretary27%