How hydrologists are reshaped as AGI capability advances.

Roughly 85% of the work in Hydrologists 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: All 30 tools used by Hydrologists fall into segment 43 (IT/software, prior 0.85), including modeling and GIS tools like ArcGIS and AutoCAD. The top work activities are highly analytical, led by 'Analyzing Data or Information' (4.82) and 'Working with Computers' (4.64), and the work context is defined by knowledge-work surfaces like 'E-Mail' (4.96), 'Indoors' (4.00), and 'Spend Time Sitting' (3.86). These signals overwhelmingly point to remotely-doable information and software work.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Hydrologists engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Hydrologists 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.
Hydrologists performs 25 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+13 more via performs
Hydrologists is typically employed by 9 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
Hydrologists is employed across 16 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+4 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Hydrologists uses 70 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.
+58 more via usesTool
Hydrologists relies on 156 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.
+144 more via uses
The software Hydrologists reaches for already exposes 8 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.
+18 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.