A help desk technician resume gets read by someone who has probably worked a queue themselves. They know what a password reset looks like, they know what a messy escalation feels like at 4:55 on a Friday, and they can tell within a few lines whether you actually did the job or just listed the tools. This guide covers how to write an IT support CV that reads like the work, from first line to the step into sysadmin or cloud.
What the person hiring for IT support is checking
Most IT support managers are scanning for three things in a fixed order: which tier you worked at, which environment you supported, and how you dealt with people. The tier tells them how much you can solve alone. The environment tells them how fast you can be useful on their stack.
The people part is where many CVs go quiet. A help desk is a customer-facing role, even when the customers are colleagues in finance who need their VPN back before a board meeting. If your CV reads like an inventory of software, the reader has to guess at the part they care about most.
So before you write a single bullet, answer these for yourself:
- Were you 1st line (logging, triage, quick fixes), 2nd line (deeper troubleshooting, desk-side visits, some admin rights), or 3rd line (infrastructure, vendor escalations, root-cause work)?
- Roughly how many users, sites and devices did your team support?
- What did a normal day look like, and what did a bad one look like?
Those answers become the spine of the experience section.
Name your tier and your environment early
Put the tier in the job line or the first bullet. "IT Support Technician (2nd line)" is clearer than a generic "IT Technician", and it saves the reader from inferring your level from the verbs. If your title was vague, you can add the tier in brackets without changing what your employer called the role.
Then describe the estate in one sentence. Something like: "Supported 350 users across two offices and a remote sales team, mainly Windows 11 laptops, Microsoft 365, Active Directory and a small fleet of iPhones under MDM." That single line does more work than a skills list of thirty logos, because it shows scale and context together.
Tools are still worth naming, but name them as examples of what you handled rather than as a wall of keywords. Common ones in job ads include Windows client and server, Active Directory and Entra ID, Microsoft 365 admin, Intune or another MDM, basic networking (DHCP, DNS, VLANs), printers that never behave, and a ticketing tool such as ServiceNow, Jira Service Management, Freshservice or Zendesk. Match the names to the ad you are answering, and only list what you could talk about for two minutes in an interview.
Describe ticket work honestly
Ticket numbers are tempting because they look like proof. Use them carefully. A figure like "handled around 25 to 35 tickets a day" is fine if it is a fair estimate and you say so; a precise resolution rate you cannot back up is a liability the moment someone asks how it was measured.
Better than volume alone is what the tickets were and what you changed. Compare:
- Weak: "Resolved tickets in a timely manner."
- Stronger: "Handled 1st and 2nd line tickets for 350 users, mostly access, Outlook and laptop issues; wrote 20 knowledge-base articles that let the 1st line team close common printer and MFA requests without escalating."
The second version tells the reader what you touched, who benefited, and that you think beyond the single ticket. If your service desk tracked SLAs, you can mention that you worked to them, and give an example of a time you kept a priority incident moving. Keep any numbers framed as your own estimates unless they came from a report you can point to.
A short sample entry
Here is an invented example of what a full entry might look like.
IT Support Technician (2nd line) - Harbourline Logistics (fictional), 2022 to present
- Supported around 300 users at three depots: Windows 11, Microsoft 365, Active Directory, Intune.
- Took escalations from a two-person 1st line team and owned them through to closure or vendor hand-off.
- Led the rollout of 60 replacement laptops over six weeks, with a checklist that cut setup time per device roughly in half by our own count.
- Wrote and maintained 30 knowledge-base articles; trained new starters on the ticketing tool.
Notice that every bullet has a scope, an action and a result, and that the one number with a claim attached is hedged. For more on structuring bullets like these, see how to write the work experience section.
Certifications, home labs and self-taught routes
Certifications matter more in IT support than in many fields, because they give a recruiter a quick read on baseline knowledge. Examples people often list include CompTIA A+, Network+ or Security+, ITIL 4 Foundation, and vendor certificates such as Microsoft 365 Fundamentals or the Microsoft Endpoint Administrator. Requirements vary a lot between employers and countries, so check the ads you are targeting rather than collecting badges at random. If you are unsure where they belong on the page, this piece on certifications on a CV covers placement and what to drop.
If you are coming in without a support job yet, a home lab is real evidence. A small domain controller in a virtual machine, a couple of joined clients, a Group Policy that maps drives, a test Microsoft 365 tenant: write these up as a project with a sentence on what broke and how you fixed it. Volunteer work counts too, such as keeping the laptops running at a local charity or sports club.
Self-taught candidates should lead with what they can do, not with what they lack. A "Projects" section above education, with two or three concrete builds, usually reads better than an apology for not having a degree.
Moving up from the help desk
Many people use support as a first step, and your CV can show where you are heading without sounding restless. If you want to move into systems administration, highlight the admin tasks you already did: user provisioning scripts, patching, backups, permissions clean-ups. For cloud, point to anything you did in Azure, AWS or Microsoft 365 admin, even if it was small.
If security is the goal, the move from help desk is common, and a cybersecurity analyst CV has its own rules about what to show and what to keep private. For people heading towards automation and reliability work, the DevOps and SRE route is a different document again, with on-call and scale at its centre, so it is worth writing that version separately when the time comes.
A short profile at the top can carry the direction in a single line: "2nd line support technician moving towards Microsoft 365 administration, with hands-on Intune and Exchange Online experience."
Before you send it
Read your CV as if you were the team lead hiring for the seat. Could you tell which tier you worked at within ten seconds? Is there at least one bullet about writing documentation or helping a user who was stressed? Are the tools in your skills list the same ones mentioned in your bullets?
If your LinkedIn profile already lists your roles and certifications, Postulit can turn it into a first CV draft so you start from your real history rather than a blank page. Then edit it hard against the ad: cut anything older than the last two or three roles if it adds nothing, and make sure the job title at the top matches the one you are applying for.
Pick one recent ticket you are proud of tonight, write it as a bullet with scope, action and result, and use it as the model for the rest.