LUCERIA
Sign in
Software and technology · Entry level · US conventions

IT support technician: resume example, explained

This fictional example shows a recent associate-degree graduate applying for a tier 1 IT support technician role: the campus help desk is written as production support with ticket volume, SLA record and first-contact resolution, each tool category appears with a verb and a scope, and a certification is shown honestly as scheduled rather than held. Four decisions are explained, three weak bullets are rewritten from the evidence behind them, and the editable download lets you replace every detail with your own. Nothing here describes a real person or employer.

Illustrative example. An illustrative, invented entry-level technician who finished a two-year associate degree in information technology in 2026, worked a part-time campus help desk for 18 months and is applying for a tier 1 IT support technician role at a fictional regional billing company. Every employer, ticket figure and date is fictional.

Editable version of this example (.docx)

The example document

Jordan Castellano-Reyes

IT Support Technician · Help desk, Windows and macOS endpoints, Active Directory · A.A.S. Information Technology

Columbus, Ohio · 555-0148 · jordan.cr@example.com

Profile

Entry-level IT support technician with 18 months on a fictional college help desk, resolving around 25 tickets a week across password resets, Wi-Fi, printing and classroom equipment, with first-contact resolution of roughly 70 percent in the last two semesters. Comfortable with Windows and macOS endpoints, supervised Active Directory account tasks and a ticketing system with SLA timers. Completed an A.A.S. in Information Technology in May 2026; a vendor-neutral foundation certification exam is scheduled for December 2026.

Experience

Student Help Desk Technician (part time, tier 1) — Fictional State Community College, IT Services

January 2025 – June 2026 · Campus help desk serving about 6,000 students and 400 staff; 20 hours a week during semesters.

  • Resolved around 25 tickets a week (password resets, multi-factor enrollment, Wi-Fi, printing, classroom projectors), closing roughly 70 percent at first contact in the last two semesters.
  • Met the 4-hour first-response SLA on every ticket assigned in the spring 2026 semester and escalated hardware and network issues to tier 2 with a written summary of the steps already tried.
  • Imaged and enrolled 120 loaner laptops over the summer of 2025 using the college's imaging process and MDM tool, with a checklist that cut setup time per device from about 45 minutes to 20.
  • Performed Active Directory account tasks under supervision (password resets, unlocks, group membership) for around 40 users a week, following the access-request approval process every time.
  • Wrote six knowledge-base articles for the student self-service portal; the multi-factor enrollment article is the most viewed, and enrollment tickets fell by about a quarter the semester after it was published.

Electronics Department Associate (part time) — a fictional consumer electronics retailer

June 2023 – December 2024 · Sales floor and customer tech-setup counter.

  • Set up and troubleshot around 15 customer devices a week at the tech counter (phones, laptops, home routers), explaining each fix in plain language.
  • Processed device returns and warranty paperwork with no errors flagged in the store's monthly audits during 2024.

Education

  • A.A.S. Information Technology, Fictional State Community College, May 2026 (GPA 3.6)
  • Coursework: networking fundamentals, operating systems, scripting basics (PowerShell, Bash), security fundamentals

Certifications (optional for this role)

  • Vendor-neutral IT foundation certification: exam scheduled for December 2026 (in progress)
  • Campus IT Services customer-service training, 2025

Skills

Ticketing system: queue triage, SLA timers, escalation notes · Windows and macOS endpoint troubleshooting · Active Directory account administration (supervised) · Device imaging and MDM enrollment · Networking basics: Wi-Fi, DHCP, DNS, VPN client setup · Knowledge-base writing and plain-language customer communication · Scripting basics: PowerShell, Bash

Bullet rewrites, and the evidence behind them

Each rewrite was produced by asking an evidence question and using only the (fictional) answer. No number appears in a rewrite that is not in its evidence.

  1. Before

    Helped students with computer problems at the help desk.

    Evidence question

    How many tickets, of what kinds, and how often did you solve them without escalating?

    Evidence (fictional)

    Around 25 tickets a week: password resets, multi-factor enrollment, Wi-Fi, printing, classroom projectors; roughly 70 percent closed at first contact in the last two semesters.

    After

    Resolved around 25 tickets a week (password resets, multi-factor enrollment, Wi-Fi, printing, classroom projectors), closing roughly 70 percent at first contact in the last two semesters.

  2. Before

    Set up laptops for the college.

    Evidence question

    How many devices, using what process, and what did your work change about the process?

    Evidence (fictional)

    120 loaner laptops over the summer of 2025; imaged and enrolled through the college's imaging process and MDM tool; wrote a checklist; setup time per device fell from about 45 minutes to 20.

    After

    Imaged and enrolled 120 loaner laptops over the summer of 2025 using the college's imaging process and MDM tool, with a checklist that cut setup time per device from about 45 minutes to 20.

  3. Before

    Wrote documentation.

    Evidence question

    What did you write, for whom, and did it change the ticket volume?

    Evidence (fictional)

    Six knowledge-base articles for the student self-service portal; the multi-factor enrollment article is the most viewed; enrollment tickets fell by about a quarter the following semester.

    After

    Wrote six knowledge-base articles for the student self-service portal; the multi-factor enrollment article is the most viewed, and enrollment tickets fell by about a quarter the semester after it was published.

Try it on your own bullets with the bullet workbench, which asks the same questions and never adds a figure you did not supply.

Transferable skills in this example

  • Working a queue against a service level

    Evidence: Around 25 tickets a week with the 4-hour first-response SLA met across a semester.

    Where it helps: Any operations or service role with measured response times: customer support, facilities, dispatch.

  • Writing down what you tried before handing over

    Evidence: Escalations to tier 2 with a summary of steps taken; six knowledge-base articles.

    Where it helps: Technical writing, QA and junior systems administration, where handover notes matter.

  • Following an access-control process without shortcuts

    Evidence: Supervised Active Directory tasks for around 40 users a week, each through the approval process.

    Where it helps: Security operations, identity administration and compliance-heavy support roles.

  • Explaining a fix in plain language

    Evidence: Around 15 customer device setups a week at a retail tech counter, plus campus walk-ups.

    Where it helps: Customer success, training and onboarding roles, and any job where non-technical colleagues depend on you.

Occupation notes

Hard requirements

  • No state license or registration is required to work as a computer user support specialist in the US. The Bureau of Labor Statistics' Occupational Outlook Handbook describes education requirements as varying (some college courses are typical, not necessarily a degree) and says employers may require certifications in the products they use, so read each posting's must-have list and show those products in your bullets.
  • Legal authorization to work in the US is confirmed through the application and onboarding paperwork, not stated on the resume; some employers may run a background check as a condition of the offer.

Vocabulary that belongs on the page

  • Ticket queue, ticket triage, tier 1 / tier 2 escalation
  • SLA (service-level agreement), first-response time, time to resolve
  • First-contact resolution (FCR)
  • Active Directory: account unlock, password reset, group membership, organizational unit
  • Imaging (deploying a standard operating-system build), golden image
  • MDM (mobile device management), device enrollment, compliance policy
  • Knowledge base (KB), self-service portal, runbook
  • Endpoint, asset tag, warranty, loaner pool

Pitfalls specific to this occupation

  • Writing 'proficient in Active Directory' without saying which tasks and at what access level; a hiring manager assumes the least and worries about the most.
  • Listing a certification you have not yet passed as if held; name it as scheduled or in progress and keep it in its own section.
  • Burying the help desk under 'student employment' and leading with the degree; for an IT support technician the ticket volume, SLA record and first-contact resolution are the strongest lines on the page.
  • Describing troubleshooting as 'resolved issues' with no categories, so the reader cannot tell a printer jam from a network outage.

UK and US differences

  • UK: In the UK the same work is usually advertised as IT support technician, service desk analyst or first-line support; qualifications are listed by their UK names, and 'first line / second line' is used where US postings say 'tier 1 / tier 2'.
  • US: US IT support resumes are usually one page at entry level; omit a photo, date of birth and references, and leave salary history off.
  • US: Postings vary in the education they ask for; the Occupational Outlook Handbook notes that computer user support specialist jobs require some computer knowledge but not necessarily a college degree, so a documented help desk record can carry more weight than the credential line.

US occupation: Computer User Support Specialists (O*NET code 15-1232.00, O*NET 31.0 Database (O*NET-SOC 2019 taxonomy)). O*NET 31.0 Database code and title are used under the Creative Commons Attribution 4.0 International License (CC BY 4.0): https://creativecommons.org/licenses/by/4.0/. Source: U.S. Department of Labor, Employment and Training Administration; Luceria paraphrases independently and is not endorsed by O*NET. Identifies the US occupation for readers and search engines; the example's content is Luceria's own and is not derived from O*NET descriptions. Licence.

Common questions

Do I need a certification for an entry-level IT support technician job?

No license or registration is required, and the Occupational Outlook Handbook describes certifications as something employers may require for the products they use. A foundation certification helps where a posting asks for it; a documented help desk record counts for more than a certificate on its own.

How do I describe a campus or part-time help desk job so it reads like real support experience?

Use the desk's own measures: tickets a week, the categories you handled, SLA record, first-contact resolution and what you escalated. Then show one process improvement, such as a knowledge-base article or an imaging checklist, with the change it made.

Sources

Keep going

Published 6 November 2026 · Every person, employer and figure in this example is fictional. Drafted with AI assistance and checked against Luceria’s editorial standards.