BridgeWorks
When I joined BridgeWorks four years ago, our IT track ended with a CompTIA A+ certification, a resume workshop, and a placement pipeline of about thirty regional employers hiring junior helpdesk and tier-one support. That program worked. Graduates got jobs. Employers were happy.
Almost every part of that program has been rebuilt in the past eighteen months. Some of the rebuild is good news for our graduates. Some of it is sober. I want to share what we changed and why, both for transparency with our community and because the question of how workforce training adapts to AI is one that every program in our space is wrestling with.
What Actually Changed in Entry-Level Tech Work
The shift is uneven across roles, but the pattern is consistent enough to describe.
Tier-one helpdesk. A meaningful share of password resets, account provisioning, and routine ticket triage now flows through AI-assisted self-service systems before reaching a human. Many of our employer partners report a 30 to 50 percent reduction in tier-one ticket volume reaching live agents over the past two years. Helpdesk roles still exist, but they are fewer, and the work that remains skews toward harder problems.
Junior software development. Code generation tools have absorbed a substantial portion of routine implementation work. Senior engineers who used to need junior developers to write boilerplate now write it themselves with AI assistance, faster than a junior developer could. Our placements into entry-level developer roles dropped by half last year. Some of that is broader sector consolidation. A meaningful share is AI-driven.
Data entry and routine document processing. This was already declining for years. AI-assisted document understanding has accelerated the trajectory. Roles that paid $18 to $22 an hour two years ago are increasingly automated.
On the other side of the ledger: demand has held up or grown for IT roles that involve physical infrastructure (network technicians, on-site support), security operations, and any role that pairs technical skills with industry-specific domain knowledge.
What We Rebuilt in the Curriculum
Based on these shifts, we restructured our IT track over the past year. Three of the changes are worth describing in detail.
We added a security operations track. This is now our largest IT enrollment cohort. Coursework covers Security+, basic incident response, and supervised hands-on time in a sandboxed SOC environment we built with one of our employer partners. Placement outcomes have been stronger here than in any other tech subfield we offer.
We expanded the network and infrastructure track. Physical-presence work — pulling cable, configuring switches, troubleshooting on-site — has held up well against automation. We doubled the lab time in this track and added a CCNA preparation pathway.
We changed how we teach the helpdesk track. The remaining helpdesk roles require people who can handle the harder problems that AI triage cannot. Our updated curriculum emphasizes troubleshooting methodology, customer communication under pressure, and AI-assistant fluency itself. Graduates leave able to operate the AI tools their employers are deploying, not just operate around them.
We also embedded AI-tool fluency across every IT track, not as a separate course but as part of how the work gets done. Participants learn to use AI assistants the way previous cohorts learned to use search engines or documentation: as a tool that amplifies a competent worker and exposes an incompetent one.
What We Are Still Figuring Out
Some questions do not have clean answers yet, and I want to name them honestly.
The career ladder problem. Many traditional tech career paths started with a few years in a role that AI can now do faster and cheaper. If those entry-level rungs disappear, how do people get to the senior roles where the work still requires humans? Nobody in our industry has a confident answer. Apprenticeships, employer-sponsored training, and longer guided early-career programs all seem to be part of the answer. None of them are at the scale that the displacement requires.
Wage compression. When AI tools make individual workers more productive, in theory wages should rise. In practice, in many of the segments we track, wages have stayed flat or fallen as employers capture the productivity gains. We do not have a curriculum response to that. It is a labor-market and policy question, and we say so plainly to participants.
The pace of change. Our curriculum revision cycle used to be 18 to 24 months. We are now reviewing IT curriculum every six months and adjusting between cycles. That works for a small program. It is not sustainable forever. We are exploring partnerships with larger training networks to share curriculum updates more efficiently.
What This Means for Prospective Participants
If you are reading this and thinking about an IT or tech-adjacent path, a few honest observations.
The fastest entry points right now are security operations, network and infrastructure work, and on-site support roles. They pay reasonably well, the demand is durable, and the work cannot be done remotely by an AI assistant.
The harder entry points right now are generalist software development, traditional helpdesk, and routine data work. These are not closed paths, but they require either higher specialization, an existing network, or a willingness to relocate to where the demand still concentrates.
If you are interested in the field but not sure which direction makes sense, schedule an advising appointment. We are not in the business of selling people into programs that will not lead to work. Our advising team will be honest with you about what we are seeing in placements, even when the honest answer is "this might not be the right path for you right now."
Workforce development is a moving target. It always has been. The pace of the move has changed, and we are doing our best to keep up alongside the people we serve.
