IT support hiring runs on three proofs: ticket volume with resolution rates, the exact systems you administer (not "various software"), and certifications. A specialist who writes "resolved 30-40 tickets weekly at 92% first-contact resolution, admin for Microsoft 365 across 600 users" has answered the screener's whole checklist in one line. Everything else on the page exists to support and extend that line.
This is also a field where the ladder matters: help desk to sysadmin to cloud runs through the skills you name today. The example below plants the keywords (Intune, Entra ID, PowerShell) that pull your resume into the next tier's searches. Recruiters filling a tier-2 or junior sysadmin seat query those exact strings, and a tier-1 tech whose resume already carries them gets pulled upward by the search itself, before any human decides anything.
The screening pipeline is predictable. First pass: an applicant tracking system or a recruiter keyword search matches certifications by official name ("CompTIA A+", not "A+ certified"), the ticketing system ("ServiceNow", "Jira Service Management", "Zendesk"), the identity and device stack ("Entra ID", "Intune", "Active Directory"), and OS coverage. Second pass: an IT manager reads the shortlist doing capacity math (users supported, tickets per week, resolution rate) and looking for the one thing that separates candidates at the same volume: evidence you reduce future tickets rather than just closing today's.
That ticket-reduction evidence is worth dwelling on, because it is the highest-signal content an IT support resume can carry. Knowledge-base articles that deflected tickets, a driver standardization that cut printer issues by a third, a self-service guide that dropped VPN calls 40%, an automation that turned a 45-minute checklist into 5 minutes: these bullets prove you think like an engineer about a queue, which is exactly the quality that gets techs promoted out of queues.
Writing the experience section. Lead each role with the scale line: users supported, ticket volume, resolution rate, satisfaction score if surveyed, and the ticketing system in parentheses. Then alternate two bullet types: administration bullets (systems you run, with the verbs of ownership: administer, configure, deploy, migrate) and improvement bullets (time cut, tickets deflected, audits passed, migrations landed). Include environment details that level you: 24/7 hospital help desk with severity triage reads very differently from a 9-to-5 office queue, and enterprise stack names travel. Never write "provided technical support to end users" without numbers; the quantification guide shows how to pull volumes from your own ticketing history, which you can export before you change jobs.
Structuring the skills section. Group by function (administration versus support) and name products with their current official names: "Microsoft 365 / Entra ID" (add "Azure AD" in parentheses if you like, since some searches still use it), "Intune (Autopilot, compliance)", "Active Directory and Group Policy", "PowerShell scripting", your ticketing systems, OS coverage including mobile, and remote-support tooling. PowerShell deserves special placement: it is the single strongest keyword separating tier-1 from tier-2 pay bands, and even modest real scripting belongs on the page. Skip decades-old or trivial entries (Microsoft Word) that dilute the signal. The skills section guide covers ordering and count.
Handling certifications and education. Certifications get their own section with exact official names, issuers, and dates: CompTIA A+, Network+, Security+, Microsoft role-based certs (Endpoint Administrator is the natural one for this profile), ITIL Foundation for enterprise service desks. Order them by relevance to the posting, not chronology. Expired certifications stay listed with their year, never presented as current, because IT credentials verify instantly. Education is brief: an associate or bachelor's degree gets two lines; if you have no degree, lead with certifications and list your highest completed education without apology, since certifications plus demonstrated volume beat degrees at most employers in this field.
Formatting for IT screens. Single column, standard headings, one page up to about eight years, PDF with real text. IT managers read fast and hate hunting; parsers reward the same restraint. Skip skill bars and percentage self-ratings entirely: telling a sysadmin you are "90% PowerShell" invites the interview question that proves otherwise. Keep a plain-text-safe structure because MSPs and staffing firms re-parse resumes into their own databases constantly. The 2026 format guide covers safe layouts.
Recurring mistakes on IT support resumes. Vague systems ("various software and hardware"). Missing volume, which makes a five-year tech read like a one-year tech. Old product names only ("Azure AD" with no "Entra ID") that miss current-name searches. Ticket-closing bullets with zero improvement bullets, which reads as queue-treading. Listing home-lab skills as production experience without labeling (label it; a labeled lab is a plus, an unlabeled one is a credibility risk). Certifications paraphrased instead of exact. And burying the help desk soft skills that actually differentiate: plain-English explanations, triage judgment, documentation people find. Run the common mistakes checklist before sending.
Use the top third for a summary that compresses scale, stack, and one improvement number, like the example below: years, users, tickets and resolution rate, the systems you administer, and your best time-cut or deflection stat. Entry-level candidates should run a short objective instead: certifications held, lab or coursework stack, and the tier they are targeting. Both patterns are in the resume summary guide, and the no-experience guide covers building the first version from labs, retail tech jobs, and campus IT work.
Tailor per posting. An MSP posting wants multi-client context-switching and breadth; an enterprise help desk wants ITIL vocabulary, SLA awareness, and your ticketing system; a healthcare or finance environment wants their compliance-adjacent tooling (Epic access, badge-tap workstations) named; a "support engineer" posting at a startup wants scripting and ownership. Mirror each posting's stack names exactly and reorder your bullets so its priorities come first. The tailoring guide shows the ten-minute mechanical version.
The 2026 context: AI chatbots and self-service portals now absorb a real share of tier-1 volume (password resets, how-do-I questions), which is compressing pure tier-1 seats while expanding demand one level up: endpoint management at scale, identity administration, automation, and the judgment calls AI hands off. The resume response is to show you already operate above the deflectable layer: administration bullets, PowerShell, Intune, and ticket-reduction work. Techs who position as the person who builds the deflection (knowledge bases, automations, self-service) rather than the person the deflection replaces are the ones the market is bidding up.
Use this page as a working file. Copy the structure, swap in your stack, volumes, and certifications, borrow phrasing from the bullet bank below, then run the finished resume through the checker to confirm the parser reads your certifications and numbers exactly as you wrote them.
Preguntas frecuentes
- Which certification should I list first?
- The one the posting asks for, always; certification order is a per-application decision, not a fixed ranking. If the req says "CompTIA A+ required, Network+ preferred", your certifications section should present them in exactly that order so the screener's checklist resolves in two seconds. For general applications without a specific posting, the default logic runs by career stage: entry-level candidates lead with CompTIA A+ because it is the recognized floor for help desk hiring; techs past tier 1 lead with the Microsoft role-based certification that matches their stack (Endpoint Administrator Associate for the Intune/Entra world, which is where most corporate support now lives) or Network+ if the target skews networking; anyone aiming at security-adjacent seats leads with Security+. Enterprise service desks with ITIL vocabulary in the posting justify moving ITIL Foundation up. Two hygiene rules regardless of order: use exact official names ("Microsoft 365 Certified: Endpoint Administrator Associate", not "Microsoft certified") because parsers and verification systems match literal strings, and date everything honestly, listing expired certifications with their year rather than as current, since IT credentials verify online in seconds and a misrepresented date does more damage than a lapsed cert ever could. If you hold many, cap the section at the four or five most relevant; a wall of minor certificates dilutes the strong ones.
- How do I move from help desk to sysadmin on paper?
- Shift the resume's center of gravity from tickets resolved to systems administered, because a sysadmin req screener is searching for ownership evidence, not queue throughput. Concretely: inventory everything in your current role that is administration rather than support (user lifecycle in Entra ID or Active Directory, Intune policies you configured, Group Policy changes, mailbox migrations, conditional access, patching, any PowerShell you wrote) and promote those to the top bullets of your current job, written with ownership verbs: administer, configure, deploy, migrate, automate. One PowerShell automation bullet outweighs five ticket-volume bullets when a sysadmin req is screening. Keep one capacity line for context, but let administration carry the page. Second, fill gaps deliberately: volunteer internally for the migration or rollout work sysadmins shed gladly, build a labeled home lab for whatever your environment lacks (a lab running AD, Entra, and Intune trials is legitimate resume content when labeled as a lab), and take the Microsoft role-based cert that matches the target. Third, target the bridge titles where this move actually happens: "IT support specialist II/III", "endpoint administrator", "junior systems administrator", "IT administrator" at small companies where one person runs everything. Finally, tailor per posting: reorder so each req's first requirement is your first bullet. Most techs make this jump by already doing sysadmin work under a support title and then writing the resume that admits it.
- Is a degree required for IT support?
- Rarely, and less each year. IT support is one of the most credential-flexible corners of tech: certifications plus demonstrated volume beat degrees at most employers, because the job's proof points (tickets resolved, systems administered, users supported) are all measurable without a transcript. Plenty of working sysadmins and support leads started with a CompTIA A+ and a help desk contract. Where a degree does still matter: some large enterprises, government agencies, and healthcare systems keep degree requirements in postings (often "or equivalent experience", which they mean), and a degree can help at the margin for internal promotions into management. If you have a degree, list it briefly; two lines, no coursework unless you are a new graduate. If you do not, follow three rules. First, never leave the education section empty or apologetic; list your highest completed education (high school diploma, some college with honest dates, a bootcamp or certificate program) plainly. Second, lead with certifications, placing that section above education so the credentials the employer actually screens for come first. Third, compensate with visible evidence: a labeled home lab, documented volunteer IT work, campus or retail tech experience quantified like a real job. The no-experience guide covers building that first page. In interviews, no one who has watched you resolve a live problem asks about the degree again.
- How do I show a home lab without it reading as padding?
- Label it, structure it, and attach outcomes, and it becomes one of the strongest sections an early-career IT resume can carry; leave it vague and it reads as filler. The labeling rule is absolute: lab work is presented as lab work ("Home lab" as the entry title or a clearly marked project section), never blended into professional experience, because an interviewer who discovers your "Active Directory administration" was a trial tenant loses trust in every other line. Within that frame, write it exactly like experience: what you built, at what scale, and what you learned to do. "Run a home lab with Proxmox hosting Windows Server 2022, a 3-machine AD domain with Group Policy, Entra ID Connect sync to a trial tenant, and Intune enrollment for two test devices; documented builds and break-fix notes in a GitHub wiki" is concrete, verifiable in conversation, and demonstrates initiative that most tier-1 applicants lack. The GitHub or wiki link matters: documentation is itself a screened skill, and a public record proves the lab exists. Choose lab content that mirrors your target stack (an Intune/Entra lab for corporate support, a networking lab with VLANs for MSP roles) so every lab keyword doubles as a posting keyword. What to avoid: listing lab-only tools in your main skills section without the lab context, inflating uptime hobbies into "infrastructure management", and letting the lab outshine real customer-facing experience you already have; employers hiring support want both the technical floor and the human skills, in that order of visibility only when your paid experience is thin.
- MSP or internal IT: which experience is worth more on a resume?
- Both are respected, and each converts into strong resume material if you present its native strengths; the mistake is presenting either one generically. MSP (managed service provider) experience is breadth under pressure: multiple client environments, mixed stacks, aggressive SLAs, and daily context-switching. On paper, quantify exactly that: "supported 14 client environments totaling 1,800 endpoints across Microsoft 365, Google Workspace, and three RMM platforms, meeting 15-minute response SLAs". Internal IT experience is depth and ownership: one environment known completely, longer projects (migrations, rollouts), closer stakeholder relationships, and improvement work whose results you lived with. Quantify that instead: users supported, systems administered, project outcomes, ticket-reduction numbers. When crossing between them, translate deliberately. MSP-to-internal: pick your one or two deepest clients and present the work as environment ownership, emphasizing projects over ticket churn, because internal teams worry MSP techs only skim surfaces. Internal-to-MSP: surface every breadth signal you have (multiple offices, acquisitions integrated, varied stacks) because MSPs worry internal techs are single-stack and slow. Hiring managers on each side carry exactly those stereotypes, and your resume's job is to preempt the one aimed at you. Compensation-wise, MSPs are the classic accelerated learning route early on, while internal seats tend to win on sustainability and project depth; a resume showing two years of MSP volume followed by internal ownership is one of the strongest support career arcs there is.
- AI chatbots are taking tier-1 tickets. How should my resume respond in 2026?
- By showing you operate above the deflectable layer, and ideally that you build the deflection itself. The market shift is real: AI assistants and self-service portals now absorb a meaningful share of password resets, access requests, and how-do-I tickets, which compresses pure tier-1 headcount while increasing demand for endpoint and identity administration, automation, escalation judgment, and the human interactions AI hands off (frustrated users, ambiguous problems, outages). Three resume responses follow. First, reweight your bullets toward administration and improvement: Intune and Entra work, PowerShell automations, migrations, conditional access rollouts, and any ticket-reduction number you own. A tech whose page reads "closes tickets fast" is describing the automated layer; one whose page reads "cut the queue 15% by building the knowledge base" is describing the person who automates it. Second, if you have touched the AI tooling itself, say so with outcomes: "tuned the help desk chatbot's escalation rules and knowledge sources, lifting password-ticket deflection to 30% without satisfaction loss" is a genuinely differentiating 2026 bullet, because most support teams are still figuring this out. Third, keep the irreplaceable human evidence visible: satisfaction scores across thousands of surveyed tickets, executive support with zero critical failures, triage under outage pressure. What to avoid: defensive framing about AI, and pretending the shift is not happening by leading with the exact ticket categories everyone knows are being deflected. Position as the operator of the new stack, and the trend works for you instead of against you.