Support & Operations

Help Desk Technician

Be the first person who hears about every problem — and the reason it gets solved.

This is genuinely reachable as a first role in IT.

What you actually do

  • Take a vague description of a problem and turn it into something diagnosable
  • Reproduce the issue, isolate the cause and fix or escalate it
  • Set up accounts, machines and access for new people
  • Work through password, printing, connectivity and application problems
  • Document what you did so the next person does not start from zero

Technologies you may touch

Nobody uses all of these. Which ones depends entirely on the employer.

  • Windows Server The Microsoft server platform running file, directory, application and print services in most enterprises.
  • Active Directory The Microsoft system that holds every user, group and computer account in most organisations, and decides what each can open.
  • Intune / SCCM Tools that configure, patch and control every laptop and phone in an organisation from one console.
  • DNS & DHCP The services that hand out addresses and translate names into them — when they break, everything looks broken.
  • Linux The operating system most servers, network devices and cloud workloads run on, driven from a command line.

Concepts you will learn

These transfer between employers and outlast any particular product.

  • Structured troubleshooting
  • Ticketing and SLAs
  • Escalation
  • Remote support
  • Basic networking

Where this work happens

Every organisation with employees Managed service providers Schools and universities Retail and healthcare

You may enjoy this if…

  • You like solving something and seeing the relief immediately
  • You are patient with people who are frustrated and not technical
  • You want to see the entire IT estate before deciding where to specialise

The honest downside

A lot of it is repetitive, and metrics pressure is real. It is sometimes treated as low-status by people who forget they started there. Level 1 phone work is also the most exposed to automation — treat it as a launch pad, not a destination.

What it pays

Pay is the thing people most often get misled about, so here is where every number comes from — including the ones that are not really numbers.

Official occupation

Median for the occupation

$60,340

Computer User Support Specialists (15-1232)

What you actually start on

~$38,000–$47,000 to start (level-one service desk)

Where it leads

The value here is the exit — most people move to systems, networking or security within two years

Outlook

−3% for the group, but roughly 50,500 openings a year from turnover — churn is why the door stays open

This role maps cleanly onto a published government occupation, so the median below is a real statistic you can go and check.

Maps to Computer User Support Specialists (15-1232). Treat this as a launch pad rather than a destination: level-one phone work is also the most automation-exposed part of IT.

A median is the midpoint of everyone employed in that occupation, including people decades into their careers — so starting pay runs materially lower. Verify against the live BLS page before making a decision.

Source: U.S. Bureau of Labor Statistics · BLS OES, May 2024 release · figures are national and United States–specific; pay varies substantially by region and employer. Nothing here is adjusted for cost of living.

CertBlueprint earns affiliate commission on some study resources. It earns nothing from Help Desk Technician salaries, and no role is ranked, recommended or presented more favourably because of what it pays.

Where this leads

IT careers are a graph, not a ladder. These are the moves people actually make from here — each one reuses most of what you already know.

See where Help Desk Technician sits on the whole map →

Systems Administrator

The standard next step once you know the environment.

NOC Technician

If the network problems are the ones you enjoy.

SOC Analyst

A realistic route into security within two years.

Often confused with

Titles overlap heavily in IT and tell you very little. Each of these puts Help Desk Technician beside another role on the same dimensions, with the practical differences underneath.

vs Systems Administrator vs Network Administrator vs NOC Technician vs Field / Infrastructure Engineer vs SOC Analyst

Try it this weekend, before you spend anything

Reading about work and doing it are different. Each of these is free, runs on the machine you already have, and takes under an hour and a half. Finding out you dislike it is a genuinely useful result — and far cheaper here than after an exam voucher.

Try the work · 45–70 minutes

Follow a packet

Free

Find out where your own traffic actually goes on its way out of the building — and what it looks like when it stops arriving.

Nothing to install · no account · open the steps

Before you start

Everything here runs against your own machine and connections you already make. Do not trace, scan or probe networks you do not own or have written permission to test — in many countries that is a criminal offence, not a grey area.

Built-in commands only. Nothing to install, no account, nothing to sign up for.

  1. Watch a name turn into an address

    Every connection starts by looking up a name. Run this against a site you use daily, then against a site in another country. Notice you get different addresses — sometimes several.

    Windows
    nslookup bbc.co.uk
    macOS
    dig bbc.co.uk +short
    Linux
    dig bbc.co.uk +short

  2. Trace the path out

    This lists every router your traffic passes through to reach that address. Read the hostnames down the left — you can usually see it leave your house, reach your provider, and cross into a backbone network.

    Windows
    tracert bbc.co.uk
    macOS
    traceroute bbc.co.uk
    Linux
    traceroute bbc.co.uk

  3. Find where the time goes

    Look at the millisecond figures. Somewhere there is a jump — 8ms to 90ms between two hops. That jump is usually the moment your traffic goes long-distance. Now trace somewhere far away and compare where the jump happens.

  4. Break it on purpose, then put it back

    Add a line to your hosts file pointing a site you use at 127.0.0.1, and try to load it. Watch how the failure looks from the browser — the error will not tell you what you just did. Then delete the line. This is the single most useful thing on this list: you have now seen a name-resolution fault from the user's side, which is what half of all "the internet is down" tickets actually are.

    Windows
    notepad C:\Windows\System32\drivers\etc\hosts   (run as Administrator)
    macOS
    sudo nano /etc/hosts
    Linux
    sudo nano /etc/hosts

  5. Optional — watch the actual conversation

    If you want to go further, install Wireshark, capture for ten seconds while loading one page, and filter for "http" or "dns". You will see the individual messages between your machine and the server. This is the one step that needs an install, which is why it is last.

This suits you if…

  • You kept going past step three without being told to
  • The latency jump made you want to know exactly where that hop was
  • You found the deliberate breakage satisfying rather than pointless
  • You wanted to know why a hop showed asterisks instead of a time

If you disliked it

If this felt like tedious bookkeeping, take that seriously. Networking and network security roles involve a great deal of exactly this — patient, methodical narrowing down, often at 2am. Finding it dull here is genuinely useful information, and it is much cheaper to learn it now than after a CCNA.

Try the work · 60–90 minutes

Make the computer do it

Free

Do a genuinely boring task by hand, then arrange never to do it by hand again.

Nothing to install · no account · open the steps

Before you start

Work on a COPY of a folder, never your only copy of anything. Every step below dry-runs first and shows you what would happen before anything changes. If a step ever refuses to show you a dry run, that is the step to be suspicious of.

PowerShell ships with Windows; bash ships with macOS and Linux. You already have everything you need.

  1. Pick a real chore

    Not a toy problem — something that genuinely annoys you. Sorting a Downloads folder full of four hundred files. Renaming photos to a consistent format. Finding every file over 500MB. It has to be real, or the payoff at the end will not land.

  2. Do it by hand once, and time it

    Actually time it. Write the number down. This is the figure you are going to beat, and it is also how you will one day justify automation work to a manager who wants to know why it is worth your afternoon.

  3. Make a copy to work on

    Duplicate the folder. Everything from here runs against the copy. This is not caution for beginners — it is what people do professionally, because the cost of being wrong is asymmetric.

    Windows
    Copy-Item -Path .\Downloads -Destination .\Downloads-copy -Recurse
    macOS
    cp -R ~/Downloads ~/Downloads-copy
    Linux
    cp -R ~/Downloads ~/Downloads-copy

  4. Ask what it WOULD do, before it does anything

    Run the operation in preview mode first. Nothing changes; it just tells you what it intends. Read that output properly. This habit is the single biggest difference between someone safe to give automation to and someone who is not.

    Windows
    Get-ChildItem .\Downloads-copy -File | Group-Object Extension | Format-Table Name, Count
    macOS
    find ~/Downloads-copy -type f | sed "s/.*\.//" | sort | uniq -c | sort -rn
    Linux
    find ~/Downloads-copy -type f | sed "s/.*\.//" | sort | uniq -c | sort -rn

  5. Now let it run

    Sort every file into a folder named after its extension. Five lines or so. It will not work first time — read the error, change one thing, run it again. That loop, repeated, is the actual job.

    Windows
    Get-ChildItem .\Downloads-copy -File | ForEach-Object { $d = ".\Downloads-copy\" + $_.Extension.TrimStart("."); New-Item -ItemType Directory -Force -Path $d | Out-Null; Move-Item $_.FullName $d }
    macOS
    cd ~/Downloads-copy && for f in *.*; do d="${f##*.}"; mkdir -p "$d"; mv "$f" "$d"/; done
    Linux
    cd ~/Downloads-copy && for f in *.*; do d="${f##*.}"; mkdir -p "$d"; mv "$f" "$d"/; done

  6. Compare it to your number

    You wrote down how long it took by hand. It now takes under a second, and it will take under a second every time from now on. Sit with that for a moment — that gap, multiplied across an organisation, is the entire economic argument for automation as a career.

This suits you if…

  • The moment it worked felt genuinely good
  • You immediately thought of a second chore to do this to
  • Fighting the syntax felt like a puzzle rather than an obstacle
  • You wanted to make it handle the awkward edge cases properly

If you disliked it

If twenty minutes of wrestling with quoting and syntax was pure frustration with no compensating satisfaction, that is a real signal. Automation, DevOps and platform roles are that experience repeatedly, and enjoying the puzzle is most of what makes them bearable. Plenty of excellent infrastructure people are not wired for it — they go deep on architecture or operations instead.

Try the work · 60–90 minutes

Fix someone’s problem

Free

Take a vague, badly-described complaint from a real human being and turn it into something you can actually diagnose — then fix it and write it down.

Nothing to install · no account · open the steps

Before you start

You are working on someone else’s device, so ask permission explicitly and stay inside the problem you were asked to fix — do not browse their files, their messages or their history. Never ask for or type their password: have them enter it themselves, every time. If a fix would delete or move their data, stop and get their agreement first, in words, before you do it. These are the same boundaries a professional support role holds you to, and practising them now is part of the trial.

Needs one other person who is not technical, and a real problem they actually have. That is the only requirement, and it is the hard part.

  1. Find a real complaint

    Ask a family member, housemate or friend what annoys them about their computer or phone. Do not accept a technical description — you want the raw version. "It's slow." "The printer never works." "It keeps logging me out." That vagueness is the actual starting condition of the job.

  2. Resist fixing it for ten minutes

    This is the discipline the whole trial is built around. Ask questions instead. When did it start? What changed around then? Does it happen every time, or sometimes? Show me. Watch them do it — you will almost always see something they did not mention, because they did not know it mattered.

  3. Reproduce it yourself

    Make the problem happen on demand, with your own hands. If you cannot reproduce it, you cannot know you have fixed it — you can only know it has stopped happening for now, which is not the same thing and will come back.

  4. Halve the problem, repeatedly

    Is it that app or all apps? That network or all networks? That account or all accounts? Each answer eliminates half of what it could be. Keep going until only one thing is left. Notice how few questions this actually takes when you choose them well.

  5. Fix it — then explain it without jargon

    Make the fix. Then tell them what was wrong in language they understand, without being condescending and without pretending it was harder than it was. Watch their face. This skill is worth more to an early IT career than any certification, and almost nobody practises it deliberately.

  6. Write the runbook

    Five lines: the symptom, how to confirm it is this and not something else, the fix, and how to tell it worked. Written so someone else could follow it at 3am without ringing you. This is the artefact that turns a fix into an asset.

This suits you if…

  • Their relief when it worked genuinely felt good
  • The ten minutes of questions was interesting rather than frustrating
  • You enjoyed narrowing it down more than you enjoyed the fix itself
  • You wanted to go and fix the three other things you noticed

If you disliked it

If the human part drained you — the vagueness, the explaining, the patience — that is important and completely legitimate. It does not mean IT is wrong for you; it means the front-line support route may not be the right door. Networking, systems and data roles all reach the same industry with far less of this, though almost all of them still involve some.

Try the work · 60–75 minutes

Audit your own access

Free

Work out exactly what your own accounts can reach, what could take them over, and how far the damage would spread if one fell — the same exercise, at smaller scale, as securing an organisation.

Nothing to install · no account · open the steps

Before you start

Your own accounts and nobody else’s — not a partner’s, not a parent’s, not an employer’s, even with informal permission. Accessing an account that is not yours is an offence in most jurisdictions regardless of intent or relationship, and "I was learning security" has never once worked as a defence.

Uses the account settings pages you already have. Nothing to install. You will likely also improve your own security materially, which is a decent side effect.

  1. Find the account that owns all the others

    Start at your main email. Now list every service that would send a password reset there. That is not a list of accounts — it is a list of things someone gets for free the moment they take that one. Security people call this blast radius, and it is the single most useful concept in identity work.

  2. Check what is actually guarding it

    Look at the security settings of that email account. Is there a second factor? Is it SMS — which is interceptable — or an app or hardware key? Now check the recovery options: an old phone number or a disused backup address is a back door that bypasses everything else you just checked.

  3. Review what you have handed out

    Find the third-party access page on your Google, Microsoft or Apple account — the list of apps you signed in to using it. Most people have twenty to eighty entries and recognise perhaps half. Read what each was granted. Some will have read access to your entire mailbox from a service you used once in 2019.

    Any
    Google:    myaccount.google.com/permissions
    Any
    Microsoft: account.microsoft.com/privacy → apps and services
    Any
    Apple:     appleid.apple.com → Sign in with Apple

  4. Revoke, and notice how that feels

    Remove everything you do not currently use. Notice the hesitation — "what if something breaks?" That exact hesitation, multiplied across ten thousand employees and twenty years, is why organisations accumulate permissions nobody dares remove. You are feeling the central problem of identity engineering firsthand.

  5. Check the sessions still open

    Most services list active sessions and signed-in devices. Look for a device you no longer own or a location you do not recognise. Sign them all out. Note how many services do not offer this at all — that absence is itself a finding.

  6. Write the one-page assessment

    What is your most valuable account? What is the weakest path into it — is it the password, the second factor, the recovery method, or an app you granted access to years ago? What would you fix first if you had one hour? That prioritised write-up is exactly the deliverable an identity or GRC role produces, and doing it for yourself is the cheapest possible practice.

This suits you if…

  • The blast-radius idea in step one genuinely landed
  • You found at least one granted permission that alarmed you
  • You enjoyed the systematic sweep more than you expected
  • You started thinking about how this would scale to ten thousand people

If you disliked it

If this felt like fussy admin — a checklist with no puzzle in it — that is a real signal about identity, access and governance work, which is substantially careful, repetitive, high-consequence bookkeeping. People who want the adversary and the chase are usually better suited to detection, response or offensive roles, where the same rigour is applied to a moving target.

Certifications that fit this path

These come last for a reason. A certification is evidence for a direction you have already chosen — it is not the direction itself.

Start here CompTIA A+ The recognised entry credential for support roles. Alternative Google IT Support A gentler, cheaper start if A+ feels like a big first step. Level up CompTIA Network+ What moves you out of level 1 fastest. Adjacent Microsoft MS-900 Most support work touches Microsoft 365 constantly.
See the full step-by-step roadmap for this path →

Not sure whether this is actually you?

Reading about a role and enjoying the work are different things. The scenarios show you the problems instead of describing them, and tell you which ones you keep reaching for.

Try the scenarios →