How aerospace engineers are reshaped as AGI capability advances.

Roughly 85% of the work in Aerospace Engineers 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 of the tools used by Aerospace Engineers fall into UNSPSC segment 43 (IT/software, prior 0.85), such as FEA and CAD software. This heavily digital tooling aligns perfectly with the top Work Activities, led by 'Working with Computers' (4.88) and 'Analyzing Data or Information' (4.53). The Work Context confirms a desk-based knowledge role, defined by 'E-Mail' (5.00), 'Indoors, Environmentally Controlled' (4.79), and 'Spend Time Sitting' (4.25).
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 Aerospace Engineers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Aerospace Engineers 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.
Aerospace Engineers performs 16 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+4 more via performs
Aerospace Engineers is typically employed by 26 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+14 more via typicallyEmploys
Aerospace Engineers is employed across 42 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+30 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Aerospace Engineers uses 50 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.
+38 more via usesTool
Aerospace Engineers relies on 85 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.
+73 more via uses
The software Aerospace Engineers 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.
No articles yet for this entity.
No capability events for this entity yet.