How sales engineers are reshaped as AGI capability advances.

Roughly 85% of the work in Sales 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 reported tools fall into IT/software segment 43 (prior=0.85), including Kubernetes and Linux. Top Work Activities focus on information and communication, such as 'Getting Information' (4.40), 'Selling or Influencing Others' (4.32), and 'Working with Computers' (4.19). This is heavily reinforced by a Work Context completely anchored in desk-knowledge surfaces like 'E-Mail' (5.00), 'Telephone Conversations' (4.87), and 'Indoors, Environmentally Controlled' (4.65), pointing to a fully digital knowledge work role.
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 Sales Engineers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Sales 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.
Sales Engineers 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
Sales Engineers is typically employed by 124 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+112 more via typicallyEmploys
Sales Engineers is employed across 111 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+99 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Sales Engineers uses 4 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.
Sales Engineers relies on 103 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.
+91 more via uses
The software Sales 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.
+2 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.