IS WORK OVER?

Automation index

How much of a Parking attendant’s job can AI already do?

A barrier comes earlier. Running the car park without wrecking the person who lost the ticket do not.

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

Task comparison

Parking attendant

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
Barriers, tickets and the count.
Estimate

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

16%40%+6.4
The one who cannot find the car and the one who will not pay.
Estimate

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

18%14%+2.5
Incidents, the down barrier and the jam.
Estimate

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

16%28%+4.5
Shift, cash and cashing up.
Estimate

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

16%32%+5.1
The event, the full house and not blocking the street.
Estimate

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

18%18%+3.2
Run the car park, and not wrecking the lost-ticket person.
Estimate

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

16%12%+1.9
Total100%24%

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

Skills and activities

  • barriers
  • parking tickets
  • space count
  • cashing up
  • stuck barrier
  • events
  • lost cars
  • exit jam

Sources for this job· O*NET 33-9091.00· ESCO/ISCO 5414

Mobile 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
Screens, API and offline state.
Estimate

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

18%52%+9.4
Store review, crashlytics and ANRs.
Estimate

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

16%40%+6.4
Real device, the notch and fragmented Android.
Estimate

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

16%22%+3.5
CI, tests and the week's release.
Estimate

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

16%28%+4.5
Product, the redesign and not breaking what people use.
Estimate

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

18%14%+2.5
That it does not crash, and not ignoring the one-star.
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

  • build apps
  • ship to stores
  • crashlytics
  • offline state
  • ANRs
  • mobile tests
  • fragmented Android
  • store review

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

Analyse my job

Jobs with similar scores

  1. 257Agile coach24%
  2. 258Software architect24%
  3. 259Biochemist24%
  4. 261Probation officer24%
  5. 262Dentist24%
  6. 263Fashion designer24%