LO
Network engineer — how we know
The page itself gives the judgements. This one gives what they rest on: which technologies bear on the work, how the estimate moved since language models reached the public, and the method behind both.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
—— this stretch contains a verified event- - - no event in this stretch — reconstruction only0 = no task exposed, 100 = every task exposed
● 8 verified events for this occupation, plotted at the date it happened — the parts of the line near a marker are anchored to something checkable.
Starts at 38 because network management systems, scripted changes and monitoring were already standard before this chart begins. It climbs steadily as carriers put closed-loop automation and AI agents into configuration and fault handling, and stays below the top because complex repairs still defeat language models in benchmarks and design work is projected to grow.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Written about this#
These pieces argue from the same records this page holds, and each of their sections names what it rests on.
Method and sources#
- Assessment date
- 2026-09-30
- Basis of the task judgements
- 4 evidence-backed · 1 platform inference · 0 not enough evidence
- Verified events
- 9