IT Help Desk: 48,700 Openings a Year and a Foot in Tech's Door

The short answer: help desk is how people without degrees get into tech. Federal data projects about 48,700 computer support openings every year this decade, nearly all from turnover, and employers fill many of them with certifications and demonstrated skill rather than diplomas.

The numbers, with their limits

Per the Bureau of Labor Statistics, computer user support specialists earned a median $61,860 in May 2025. Overall employment of computer support specialists is projected to decline about 3 percent from 2025 to 2035 as AI and self-service tools handle more routine tickets. Replacement demand from workers retiring or moving to other roles still produces about 48,700 openings per year, on average, over the decade. BLS describes two tiers within this occupation. Computer network support specialists typically need an associate's degree. Computer user support specialists, the help desk role most entry-level hires start in, are commonly hired with some college coursework or a high school diploma plus relevant IT certifications. That certification-based route is the one our program is built around.

The median is a midpoint across the whole occupation, including experienced technicians. A first help desk job at a small company will usually pay below it. We cite the figure because it is the most authoritative number for the field, not because a graduate should expect it on day one.

What the role does day to day

Help desk work is a mix of technical troubleshooting and customer communication.

• Ticket triage. Logging incoming issues in a ticketing system (Zendesk, Freshdesk, ServiceNow, and Jira Service Management are common), prioritizing by urgency and impact, and routing anything beyond the technician's level.
• Hardware and software troubleshooting. Diagnosing why a device, application, or connection is not working, often by walking a non-technical user through steps over the phone or in a remote session.
• Account and access support. Password resets, permissions issues, and basic account administration in Microsoft 365, Google Workspace, and Active Directory or Entra ID.
• Remote support. Using tools such as TeamViewer, AnyDesk, or the remote-assist features built into Windows and Intune to see and control a user's screen and fix an issue directly.
• Basic networking troubleshooting. Diagnosing Wi-Fi and connectivity problems, understanding IP addressing at a working level, and knowing when a problem needs escalation to network engineering.
• Documentation. Writing up what was wrong and how it was fixed, both for the ticket record and for a knowledge base that speeds up the next similar issue.

The customer-service half of the job matters as much as the technical half. A frustrated user calling about a broken laptop needs to be walked through a fix calmly, in plain language, without jargon.

A typical day

A tier-one technician at a mid-sized company starts by checking the queue that built up overnight and anything marked urgent. The morning is usually password resets, a printer that dropped off the network, a new hire who needs accounts created and a laptop imaged, and someone who cannot open an attachment. Each one gets a ticket, a few notes, and a resolution or an escalation. Midday might bring a walk-up from a manager whose projector will not connect before a meeting. The afternoon is often follow-ups on tickets waiting for a user to reply, a hardware order, and closing out the day's documentation. The pace varies by employer. A managed service provider supporting many small clients runs faster and more varied. An internal help desk at a single company is steadier and lets you learn one environment deeply.

How a ticket moves

Understanding the ticket lifecycle is most of what an interviewer means by "process." A user reports a problem by phone, email, chat, or portal. The technician creates or claims the ticket, confirms the user's identity, and records the symptoms in the user's own words plus what the technician observed. The technician reproduces the problem where possible, checks the knowledge base for a known fix, and tries the least disruptive solution first. If it works, the technician confirms with the user, documents the fix, and closes the ticket. If it does not, the technician escalates to tier two with everything already tried, so the next person does not repeat it. Tickets have service-level targets for first response and resolution, and part of the job is keeping the queue inside those targets or flagging early when one will slip.

What our program covers

The IT help desk track runs about 20 weeks, roughly 15–20 hours a week, fully online, with volunteer educators and one-to-one mentorship. Coursework covers help-desk fundamentals, business software setup and support, account and access troubleshooting in common productivity suites, basic AI automation for support tasks, and documentation and ticketing practice, alongside the customer-service and communication skills the role depends on. Participants work tickets in a practice environment and write up each one the way an employer would expect. The curriculum is built around the knowledge areas covered by industry-standard entry certifications such as CompTIA A+ and the Google IT Support Professional Certificate, since those are the credentials employers most commonly recognize for this role. Exam costs, scheduling, and eligibility are outside our control, so we advise students individually on certification timing as they near completion rather than promising a specific exam date or outcome.

How the track maps to the job

Each part of the curriculum lines up with a task in the job description. Account and access troubleshooting is the password reset and permissions work that fills most mornings. Business software setup is the new-hire onboarding ticket. Documentation and ticketing is the knowledge base and the closed ticket that a manager reads to evaluate you. Customer-service practice is the frustrated caller. AI automation basics is the part that keeps a technician useful as chatbots absorb the simplest tickets, covered below.

What an entry-level interview asks

Expect a mix of technical scenarios and behavioral questions. Common technical prompts include "A user says their computer is slow. What do you ask, and what do you check?", "Walk me through resetting a password in Microsoft 365 and what you verify first," "A laptop cannot connect to Wi-Fi but the phone next to it can. Where do you start?", and "Explain the difference between an IP address and a MAC address to someone who is not technical." Behavioral prompts include "Tell me about a time you had to explain something technical to someone who was upset," and "What do you do when you do not know the answer?" The right answer to the last one is to say what you would try, when you would escalate, and how you would document it. Mentors rehearse these with participants before introductions to employers.

Why it is a ladder

Help desk is a common entry point for people who go on to systems administration, network engineering, or cybersecurity roles, because it is where you learn how organizations use and break technology in ways a classroom does not teach. A young person who spends time resolving tickets, earning certifications, and working alongside experienced technicians has a foundation to grow from. How far and how fast that leads to further roles depends on the individual, the employer, and the market. We do not promise a specific trajectory.

How AI is changing the ticket queue

Self-service chatbots and AI-assisted troubleshooting now resolve a growing share of the simplest, most repetitive tickets, such as a password reset walkthrough or a "how do I connect to Wi-Fi" question, before they reach a human technician. That is one factor behind BLS's projected decline in this occupation's overall employment. What is left for the human technician is the harder half of the queue. Problems that do not match a known pattern. Users frustrated enough that a bot response makes things worse. Situations that require judgment about what is broken versus what the user thinks is broken. Technicians who use AI tools to speed up their own diagnosis, search a knowledge base faster, and draft clear documentation, while still owning the parts of the job that require a person, are the ones who stay valuable as routine tickets get automated. That is the skill mix our program aims for.

Frequently asked questions

Do I need a computer science degree?
No. BLS reports that for computer user support specialist roles, employers commonly accept a high school diploma plus relevant IT certifications, or some college coursework, rather than requiring a four-year degree.

What if I've never worked in IT before?
That is the expected starting point. The program builds troubleshooting, account support, and ticketing skills from fundamentals, with mentorship for anyone new to the field.

Is the program free, and is it online?
Yes to both. Azgari Foundation is a 501(c)(3) public charity, and the IT help desk track is tuition-free and delivered fully online, like our other tracks.

Do I have to pass a certification exam to finish the program?
No. The curriculum builds the knowledge base that certifications like CompTIA A+ test, but exam registration, fees, and scheduling are handled individually with each student based on readiness and circumstances. Program completion is not contingent on passing an external exam.

Will I need to work nights or weekends?
Some help desks run extended hours or on-call rotations, and some are strictly business hours. Ask in the interview. It is a normal question and the answer varies by employer.

For employers

Status, September 2026: our first cohort is in training. The first graduates are expected in late 2026. Employers can register interest now.

Support roles turn over constantly, and every vacant seat means slower responses and frustrated users. Our graduates arrive trained on troubleshooting fundamentals and mentored, at no placement fee. Talk to us about your support bench.