EXPOSED
This is a residual bucket — cloud and platform engineers, automation and scripting specialists, cybersecurity-adjacent analysts, ERP and integration specialists, technical writers of system documentation. The modal worker spends most of the day in configuration files, dashboards, ticket queues, scripts, and documentation, all of which current models draft, translate, and troubleshoot at usable quality. What holds is ownership of production systems under ambiguity: deciding what to change, when, and who is accountable when it breaks — plus some on-site work in data centers and lab environments.
Mixed — a routine tier and a judgment tier. Writing Terraform modules, Ansible playbooks, glue scripts between SAP and Salesforce, and runbook documentation is exactly the text-in-text-out work models already do at draft quality, which pins the bulk of the day below the line — the 10 rather than a 5 comes from change management under load: reading a flapping alert against a half-documented legacy integration and deciding whether to roll back at 2am is not a prompt.
Fully desk- and screen-based. Racking and cabling in a colo, swapping a failed drive, or bench-testing a device in a hardware lab shows up for a minority of these roles and is scheduled rather than improvised, so the 4 reflects occasional badge-in facility work on top of an otherwise laptop-and-VPN job.
No licence, no signature requirement. No state licence gates any of this work — CISSP, AWS Solutions Architect, or a Microsoft cert may be in the job posting, but nobody's signature is on a filing and no board can strike you off after an outage; the employer's contract and E&O policy absorb the consequence, which is why this sits at 2 and not in certification territory.
Some relationship component. The 7 comes from being the person business stakeholders call by name about their ERP interface or their pipeline — that internal reputation makes you hard to swap mid-project — but the artifacts you ship are pull requests and tickets that are reviewed on their merits, not sold on your relationship.
Meaningful discretion. Deciding what gets deployed Friday, which IAM permission is too broad, which technical debt to eat and which legacy integration to rewrite are calls made with incomplete information and real production consequences, but they run through change-advisory boards, peer review, and an architect or manager who signs off — genuine discretion inside a chain of approval, not sole ownership of the outcome.
Producers and Directors EXPOSED
Has AI actually changed your work?