How to write it
Numbers are how you stand out in a volume-hired role
Support resumes are the most interchangeable in tech, because the duties genuinely are similar everywhere. Ticket volume, user count, resolution time and satisfaction score are the fastest way to become specific, and they're all sitting in a system you already use.
"Sole tier-2 support for 1,200 users, resolving 60 tickets a week at 97% satisfaction" tells a hiring manager the scale you can handle, the autonomy you're used to, and how users experience you. Three facts, one sentence, and almost nobody writes it.
- Tickets per week or month, and the tier
- Users, sites and devices supported
- First-contact resolution rate
- Average or median resolution time, before and after
- Customer satisfaction score
Fixing the cause is what promotes you
Every support technician closes tickets. The ones who move into systems administration, engineering or security are the ones who made tickets stop happening — self-service password reset, a knowledge base, a script, a fixed image, a policy change.
This is the single most valuable framing available to you, and it's usually true of work you've already done. "Cut password-reset tickets 70% by deploying self-service reset" is the same effort as "handled password resets", described at the level that gets noticed.
Name the stack the way postings name it
Support requisitions are keyword-dense and often screened by someone non-technical, so the specific strings matter: Active Directory, Entra ID, Microsoft 365, Intune, ServiceNow, Windows 11, macOS, VPN, DNS.
Write them as the posting writes them, including both names where a product has been renamed. Being the candidate whose resume contains the exact term the recruiter searched for is a large part of getting shortlisted in this field.
Projects, not just the queue
A rollout is a project, and projects read as capability beyond day-to-day support. An OS migration, a device refresh, a move to a new ticketing system, an office build-out, an onboarding process you redesigned — each of these is worth a bullet with scale and outcome.
"Led the Windows 11 rollout to 900 devices via Intune with no missed deadlines" is the bullet that gets you interviewed for a systems administrator role rather than another help desk one.
Say that you're good with people, by showing it
Support is a service job wearing a technical badge, and hiring managers know that patience under pressure is harder to find than knowledge of Group Policy. But "excellent communication skills" convinces nobody.
A satisfaction score does. So does documentation written for non-technical users, training you delivered, or the fact that you're the person the executives ask for. Any of those is worth more than the adjective.