How computer systems analysts are reshaped as AGI capability advances.

Roughly 90% of the work in Computer Systems Analysts is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: The occupation's toolset is purely digital, with all 30 tools falling into UNSPSC segment 43 (IT/software/telecom, prior 0.85). This is strongly reinforced by top work activities like 'Working with Computers' (4.96) and 'Processing Information' (4.43), alongside entirely desk-bound work contexts such as 'E-Mail' (5.00) and 'Spend Time Sitting' (4.18). These signals collectively define pure information and software work with no physical value-delivery step.
grounded in the economy graph · digital scalar 0.90 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Computer Systems Analysts engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Computer Systems Analysts involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Computer Systems Analysts performs 38 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+26 more via performs
Computer Systems Analysts is typically employed by 313 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+301 more via typicallyEmploys
Computer Systems Analysts is employed across 268 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+256 more via employs
Computer Systems Analysts is linked from 1 entity via `performedBy` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Computer Systems Analysts uses 11 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
Computer Systems Analysts relies on 347 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+335 more via uses
The software Computer Systems Analysts reaches for already exposes 10 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
No articles yet for this entity.
No capability events for this entity yet.