IS WORK OVER?

Automation index

How much of a Penetration tester’s job can AI already do?

A scan and a template report come earlier. Finding the weird chain, and not taking production down, do not.

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

Task comparison

Penetration tester

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
Recon, scans and enumeration.
Estimate

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

20%42%+8.4
Write the report, evidence and CVSS.
Estimate

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

18%38%+6.8
Exploit with judgment and not break the business.
Estimate

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

18%18%+3.2
Debrief with the client and retest.
Estimate

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

16%15%+2.4
Choose scope, rules and what is off limits.
Estimate

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

14%16%+2.2
Research 0-days, labs and keep the craft.
Estimate

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

14%18%+2.5
Total100%25%

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

Skills and activities

  • Recon, scans and enumeration
  • Write the report, evidence and CVSS
  • Debrief with the client and retest
  • Choose scope, rules and what is off limits
  • Research 0-days, labs and keep the craft
  • pentester
  • ethical hacker
  • pentest

Sources for this job· O*NET 15-1212.00· ESCO/ISCO 2529

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. 250Structural engineer26%
  2. 251Process engineer26%
  3. 252Midwife26%
  4. 254Court-appointed expert26%
  5. 255Chemist26%
  6. 256Copywriter26%