Frame your support tier, environment and channels
Open with a short summary that states your support model—L1 or L2 help desk, desktop support, service desk, field or on-site support, or remote workplace IT—and the environment you know, such as a corporate office, clinics, classrooms or retail sites. Mention the platforms you support (Windows, macOS, mobile), identity or VPN access, and after-hours or walk-up coverage when accurate.
Mirror posting language only when it matches work you have done. Claiming production incident command, CI/CD ownership, threat hunting or application development without examples belongs on a DevOps, cybersecurity or software engineer CV, not here. Point readers to the queues, images, access requests and device work that prove the skills the job emphasizes. Leave CX product-support queues, CSAT-for-customers and billing macros on a customer support CV unless the role truly mixes both.
Write bullets that connect tickets to SLAs, imaging and access
Strong IT support bullets name the queue or issue type, what you did and the result. Include first-response or resolution time, first-contact resolution, internal satisfaction scores, backlog reduction, imaging or hardware-refresh throughput, access-request turnaround, or MDM compliance when they clarify impact. Prefer measured outcomes—tickets handled to standard, desk-ready time reduced, access grants completed on a documented path—over vague claims that you are “great with people and computers.”
The fictional examples below illustrate wording only. They are not Make.CV performance claims and should not be copied as your own. Replace every figure with results you can support from your ITSM or inventory reports. If volume or SLA numbers are confidential, use approved ranges or describe the process you improved without naming restricted systems, credentials or internal security details.
Show endpoint, identity and ITSM tools without a product dump
Group skills into readable categories such as ticketing and ITSM, endpoints and imaging, identity and access, MDM or directory, and on-site or remote support. Prioritize tools named in the posting when you have genuine experience. A short accurate list of ServiceNow or Jira Service Management, Intune or Jamf, Entra ID or Okta, and the operating systems you actually support beats a long inventory of every printer model or programming language you once touched.
Tie important tools back to experience bullets. Saying you work in ServiceNow is more convincing when a bullet explains views, SLA policies, a runbook you documented and what changed for first-contact resolution. Endpoint security agents you support as part of desktop work can appear briefly; deeper SOC, GRC or detection-engineering claims belong on the cybersecurity CV. Keep system names at a professional level of detail and leave passwords, secrets and unpublished architecture off a public CV.
Choose a clean layout and review the export
Use a readable template with standard headings so SLA metrics, tools and environment stay easy to find. Keep dates consistent and leave room for quantified bullets. Browse Make.CV templates if you want to compare layouts before writing.
Build your CV in the free maker with live preview, then download a PDF with no watermark. Check that tool names, queue labels and certification initials wrap cleanly. Confirm the exported text remains selectable before you submit.
Frequently asked questions
How is an IT support CV different from customer support, DevOps, cybersecurity or software engineering?
An IT support CV emphasizes tickets, imaging, identity and device support for workplace systems. A customer support CV emphasizes CX product or billing help, not endpoint engineering. A DevOps CV emphasizes infrastructure and reliability. A cybersecurity CV emphasizes security operations or GRC. A software engineer CV emphasizes building product. Use the guide that matches the job you want.
Should I list tickets handled per day?
Only if the figure is accurate and does not hide quality. Pair volume with first-contact resolution, SLA attainment or satisfaction scores so it does not look like speed at any cost.
Which certifications belong on an IT support CV?
List current, relevant credentials you can discuss—for example CompTIA A+ or Network+, a Microsoft endpoint or identity certification, Google IT Support, or ITIL Foundation. Skip expired or unrelated certificates, and do not substitute a long cert list for evidence of ticket and device work.
What if SLA or inventory numbers are confidential?
Use approved ranges, relative changes or non-sensitive process outcomes such as a documented image, runbook or access path you introduced. Never invent metrics or share restricted system, credential or security details.