IS WORK OVER?

Automation index

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

A layout and a store listing come earlier. It not crashing on a real phone do not.

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

Task comparison

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

Site reliability engineer

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
SLOs, alerts and the runbook.
Estimate

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

18%52%+9.4
Incident, war room and not making it worse.
Estimate

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

16%22%+3.5
CI/CD, capacity and the error budget.
Estimate

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

16%40%+6.4
Postmortem, toil and automating the repeated.
Estimate

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

16%28%+4.5
The product that wants to ship and the SLO that will not allow it.
Estimate

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

18%14%+2.5
Not taking production down, and signing the change.
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

  • SLOs
  • runbooks
  • handle incidents
  • error budget
  • autoscale
  • postmortem
  • reduce toil
  • reliability CI/CD

Sources for this job· O*NET 15-1244.00· ESCO/ISCO 2512

Analyse my job

Jobs with similar scores

  1. 89Compliance officer28%
  2. 90Logistics coordinator28%
  3. 91Retail salesperson28%
  4. 93Fleet dispatcher28%
  5. 94Flight dispatcher28%
  6. 95Graphic designer28%