Why Redesigning Tier-1 Work Fixes the Technician Shortage

The technician shortage most MSPs describe out loud isn't really a hiring problem. Kaseya's 2026 State of the MSP Report shows the share of providers struggling to hire skilled technicians nearly doubled year over year. The deeper issue is what tier-1 work now requires and whether the people already on staff have a reason to stick around.

Is the Shortage Really About Too Few Applicants?

No, and the data says so directly. Entry-level openings haven't disappeared. What's changed is the match between who applies and what the job now demands.

Kaseya's report puts a number on that mismatch. The share of MSPs reporting difficulty hiring skilled technicians climbed from 9 percent to 16 percent year over year, and MSPs are reporting wider gaps in technical expertise among the people who do apply. Applicants are showing up. Fewer of them arrive with the mix of troubleshooting judgment and AI-tool fluency the role now assumes on day one.

The heaviest competition for talent tends to sit in the middle of the career ladder, not at the entry-level rung, which is exactly where an MSP loses a technician it spent a year training if there's nowhere internal left for that person to climb.

What the 2026 Numbers Actually Show

Zoom out and the labor market itself isn't shrinking. CompTIA projects net tech employment will grow 1.9 percent in 2026, adding roughly 185,000 jobs and pushing the national tech workforce toward 9.8 million people. Replacement demand alone is expected to open about 323,000 tech positions a year through 2036. That's a tight market, not a collapsing one.

What is collapsing, per Kaseya, is MSPs' confidence in training what they hire. Challenges tied to training and upskilling existing staff are climbing too. Read that alongside the hiring difficulty numbers above and a pattern emerges. Hiring is harder, expertise gaps are wider, and internal training pipelines are falling further behind. That's a workforce-development problem wearing a staffing-shortage costume.

What Does AI-Assisted Tiering Actually Change for Junior Techs?

It doesn't erase tier-1. It removes the repetitive floor of the job and pushes judgment work down to people earlier in their careers than it used to. Fifty-three percent of MSPs are already using AI to automate ticketing, patching, and monitoring, and Kaseya's report frames that adoption explicitly as the path to scaling operations without proportionally growing headcount, with providers reporting gains in technician efficiency and reduced burnout.

That reframes what a tier-1 hire is actually for. When routine ticket volume gets absorbed by automation, the entry-level job stops being defined by how fast someone can close a queue and starts being defined by triage judgment, client communication, and knowing when to escalate with the right context attached. CompTIA's workforce research makes the same point from the hiring side, noting that AI and digital transformation are continuously reshaping job roles and forcing constant upskilling rather than a one-time credential check at hire.

For an MSP owner, that's an operating-model decision, not just a tooling decision. If tier-1 techs spend less time on password resets and basic provisioning, the hours have to go somewhere deliberate: structured skill-building, documentation work, or client-facing shadowing, not just a smaller roster doing the same job faster.

That shift changes what you're actually training for. A curriculum built around ticket-closing speed no longer maps to the job. One built around triage judgment, communication, and knowing the limits of what automation can safely resolve does.

Why Isn't Pay Enough to Keep Technicians From Leaving?

Because most attrition isn't really about the paycheck. It's about whether someone can see a next step. ISACA's Tech Workplace and Culture Survey, a global study of more than 7,700 technology professionals, found that one in three tech professionals switched jobs in the past two years, leaving 74 percent of employers worried about retention. When ISACA asked what actually blocks a career, the top answers were not having an upward path (30 percent), limited career opportunities (24 percent), and lack of mentors (19 percent). Eighty-three percent of respondents said mentorship matters. Only 22 percent actually have a mentor.

MSSP Alert's reporting on retention lines up with that finding at the service-delivery level. Its analysis of MSP and MSSP retention points to workload, predictable schedules, funded training, and clear career paths as the levers that hold onto technical staff, with compensation acting as one factor among several rather than the deciding one. Combine that with the ISACA numbers and the operational lesson is specific. If you free up a tier-1 tech's time by automating the repetitive floor of the job but never build a visible next rung, you've reduced ticket backlog and left the retention problem exactly where it was.

Certification-backed career tracks are one of the more testable ways to build that rung, which is part of why staffing-and-training programs built around defined skill checkpoints, like Forge University's technician certification tracks, matter more than another round of raises for MSPs trying to hold onto the people they finally hired. A technician who can point to a certificate, a mentor, and a named next tier has a concrete reason to stay through the next slow quarter. One who can only point to a slightly higher hourly rate does not.

Building a Career Ladder That Holds

A career ladder only works if it's specific enough that a technician can point to where they are on it. That means naming what tier-1 owns once automation absorbs the routine floor, attaching a certification or skill checkpoint to every promotion milestone rather than a vague tenure requirement, and assigning a named mentor at hire instead of leaving pairing to chance.

CompTIA's Workforce and Learning Trends 2026 research shows why this is worth doing deliberately: a net 83 percent of firms place a high priority on addressing skill gaps, yet only 34 percent of organizations have a formal, company-wide reskilling program. A growing share of employers have already dropped degree requirements, which widens the door for apprenticeship-style entry paths built on demonstrated skill rather than a diploma.

None of that works if a growing tier ladder also means each promoted technician has to learn a new disconnected tool just to do the next-level job. Consolidating the platforms a technician actually touches, day to day, is worth auditing before you build a training curriculum around them. A short stack consolidation exercise tends to surface how much of a tier-2 promotion is really just learning to operate more tools rather than more skill.

• Name what tier-1 owns today, after automation, not what it owned two years ago
• Tie each tier promotion to a specific certification or demonstrated skill, not tenure alone
• Assign a mentor at hire and check the pairing quarterly, not once
• Review the ladder itself on the same cadence as your service catalog

What This Means for Service Delivery Right Now

The numbers don't support cutting tier-1 headcount just because AI closes tickets faster. They support redesigning what tier-1 does and reinvesting the hours automation frees up into skill-building and an actual career conversation. Applicants exist, per CompTIA. The expertise gap and the retention risk are both real and both growing, per Kaseya and ISACA. Treating this as a pure hiring problem misses where the leverage actually sits, and it's an expensive miss. Every technician you retrain and lose to a competing offer within a year is a client relationship, an onboarding investment, and a training budget line you fund again from zero.

Most of the tooling decisions that make this practical, from provisioning automation to a defined technician training path, live in the same stack an MSP is already running or reselling. Browsing the full product catalog is a reasonable starting point if you're deciding what to fix first.

Get the operating model right before you add another req to the job board. See the full stack to see what a redesigned tier-1 role actually runs on.