How technical writers are reshaped as AGI capability advances.

Roughly 85% of the work in Technical Writers 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 tool usage for Technical Writers is entirely software-driven, with all 30 tools falling into UNSPSC segment 43 (IT/software) carrying a digital prior of 0.85. Work activities heavily emphasize knowledge work and information transformation, particularly 'Working with Computers' (4.61) and 'Analyzing Data or Information' (4.00). Finally, the work context confirms a pure desk-based environment defined by 'E-Mail' (4.74) and 'Spend Time Sitting' (4.55), placing this occupation firmly in the digital band.
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 Technical Writers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Technical Writers 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.
Technical Writers performs 15 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+3 more via performs
Technical Writers is typically employed by 133 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+121 more via typicallyEmploys
Technical Writers is employed across 140 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+128 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Technical Writers uses 6 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.
Technical Writers relies on 78 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.
+66 more via uses
The software Technical Writers reaches for already exposes 12 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.
+39 more problems on the graph
No articles yet for this entity.