IT Pros All articles
Career & Certifications

Who Trains the Next Engineer When the Tickets Disappear?

IT Pros
Who Trains the Next Engineer When the Tickets Disappear?

Photo: Oompje, CC BY-SA 4.0, via Wikimedia Commons

For most of the past two decades, the entry-level help desk functioned as enterprise IT's apprenticeship in the truest sense. A new hire learned the shape of the environment by answering the phone: resetting credentials, mapping a printer, chasing a mailbox that had quietly hit its quota. The work was repetitive and often thankless, but it was also the curriculum. Six months of it produced an employee who could describe, unprompted, how a dozen systems connected and which team to call when one of them misbehaved.

That curriculum is being rewritten in production right now. Agentic systems—the kind that do not merely suggest a resolution but execute one: pull the account state, check the entitlements, apply the fix, close the request—have moved out of vendor demonstrations and into the queue at a meaningful share of US enterprises. The tickets they absorb are, almost without exception, the ones that used to fall to a technician in their first year.

The Quiet Thinning of the First Rung

No organization sent a memo declaring the end of Tier 1. What happened instead was incremental. Queue volume at the front dropped, at first in a way managers could attribute to seasonality and then in a way they could not. Password resets, MFA re-enrollment, group membership changes, software install requests, and the long tail of "my access does not work" tickets began resolving before a human ever opened them.

The deflection rates vendors quote should be treated with suspicion, and the honest range across the enterprises we have spoken with sits somewhere between a quarter and half of that first-line volume, depending on how much of the identity stack is consolidated. But the direction is not in dispute, and the composition matters more than the percentage. What is disappearing is not the easy work—it is the foundational work, the repetitive exposure that taught a junior technician how identity, endpoint management, and ticketing systems actually interlock.

The Risk Is Not Unemployment. It Is a Missing Cohort.

It is tempting to frame this as a job-loss story. The more accurate framing is a pipeline story. Enterprises are not, by and large, eliminating Tier 1 headcount this year. They are slowing hiring into it, holding requisitions open, and reassigning the people already in seats to supervision and exception handling. The consequence will not appear in this quarter's numbers. It will appear in 2029 and 2030, when hiring managers go looking for candidates with three years of broad troubleshooting experience and find a market that never produced them.

That gap has a name in workforce planning circles: a missing cohort. Once formed, it takes the better part of a decade to close, because the only remedy is to hire and train people who were not hired and trained during the lean years.

What Agentic Triage Is Actually Good At

Practitioners who have deployed these systems describe a consistent division of labor. Agents handle anything with a deterministic path and a reliable source of truth: account state changes, entitlement grants tied to an approved role, device compliance nudges, and first-pass diagnosis on a known error signature. They struggle, predictably, with ambiguity—the request that is technically satisfiable but substantively wrong, the user who asks for access they should not have, the ticket whose real problem is three systems downstream.

The lesson for a technician is straightforward: the value of knowing how to execute a task has fallen. The value of knowing whether the task should be executed has risen sharply.

The Skills That Compound

The people who will thrive in this environment are not the ones who can recite keyboard shortcuts. They are the ones who can do four things well:

Redesigning the Junior Role

Managers who want to keep the pipeline intact have to restructure the first two years deliberately rather than letting them hollow out. Three practices appear repeatedly among teams that are managing this well.

First, they change the metric. Junior technicians stop being measured on tickets closed and start being measured on documented learning—rotations completed, systems understood, agent failure modes catalogued. Second, they assign agent supervision to juniors early, with genuine escalation authority, so the technician is reviewing machine output rather than competing with it. Third, they attach every junior to a senior engineer for a project rotation within the first year: a migration, a monitoring build, a security remediation. The ticket queue can no longer be trusted to provide breadth on its own.

A Twelve-Month Path for the Technician Reading This

If you are two years into a help desk role and watching your queue shrink, treat the next twelve months as a deliberate transition. Complete one automation project end to end, even a small one. Learn the identity platform your organization runs, not just the password reset screen. Get comfortable in the command line for your organization's endpoint tooling. Then take on a visible piece of ownership: the accuracy report on the resolution agent, the runbook library, the quarterly access review. Ownership of an outcome is what separates a technician from an engineer, and it is the one credential no automation will issue on your behalf.

The queue was never the job. It was the classroom. The profession now has to build a new one.

All Articles

Related Articles

The Job Description That Never Got Written: IT's Accidental AI Administration Role

The $95K Plateau: What Really Happens When a Sysadmin Career Hits Year Twelve

The $95K Plateau: What Really Happens When a Sysadmin Career Hits Year Twelve

Trading the Terminal for the Toolbelt: Where Enterprise IT's Veterans Are Going Instead

Trading the Terminal for the Toolbelt: Where Enterprise IT's Veterans Are Going Instead