# Entry-Level IT Support Resume: What to Include and How to Show Skills

> Build an entry-level IT support or help desk resume from the duties employers list: a skills section, project bullets, certifications and honest ways to show hands-on practice without work history.

Source: https://www.epifive.com/blog/entry-level-it-support-resume-guide · Published 2026-10-25 · EpiFive

## Key takeaways

- The US Bureau of Labor Statistics lists the core duties of user support specialists, and your resume bullets should map to them directly.
- Communication, customer service, listening and problem-solving are the qualities the BLS lists, so evidence them with concrete examples.
- Label lab and volunteer projects honestly as such, and describe what you did, the tools you used and the result you observed.
- Never invent numbers, employers or tickets; use only figures you can show or explain in an interview.
- Match the tools named in the job posting to your skills section only where you have actually used them.

An entry-level IT support resume works when each line shows you doing one of the real duties of the job: diagnosing a problem, documenting it, walking a person through a fix, or setting up and repairing equipment. Put a short summary and a skills section first, then projects and experience written as specific actions and results, then certifications and education. If you have no IT job history, honest lab projects and customer-facing work are enough to fill the page.

## Who this is for

This guide is for people applying to help desk, service desk and desktop support roles, including students, career changers, and people in other jobs who are already the unofficial IT person. By the end you will have a one-page structure, bullet formulas, a way to turn home projects and coursework into evidence, and a checklist to review before you submit.

## Start from the job, not the template

The US Bureau of Labor Statistics (BLS) describes the duties of computer user support specialists, and employers' postings tend to echo them. Check these against any posting you apply to:

- Diagnose customers' computer problems and determine their causes.
- Document customers' descriptions of their problems.
- Guide customers through recommended solutions.
- Set up or repair computer equipment and related devices.
- Install new hardware or software and train users on it.
- Report major problems or recurring customer concerns to team members and managers.

The BLS also lists the qualities that matter: communication (explaining solutions clearly, orally and in writing, to nontechnical users), customer service (patience with frustrated users), listening (asking clarifying questions) and problem-solving. On education, the BLS says the typical entry-level path involves some college coursework, not necessarily a degree, and that a high school diploma plus relevant IT certifications may qualify you. It adds that no related work experience is typically required, and that some employers require certifications in the products they use.

That means your resume has two jobs: prove you can do the duties, and show the qualities. A list of software names does neither on its own.

## The structure that works

Use one page, a plain single-column layout, a standard font, and a text-based file format that applicant tracking systems can read. A simple order:

1. Name, city and region, phone, email, and a link to a portfolio or GitHub if you have one.
2. Two-line summary.
3. Skills.
4. Projects (if you have little paid IT experience, put this before experience).
5. Experience.
6. Certifications and education.

### The summary

Two lines, naming the role and your strongest evidence. Avoid adjectives you cannot back up.

```text
Help desk candidate with CompTIA A+ and a home lab running Active Directory,
DHCP and DNS. Experienced in customer-facing roles, documenting issues clearly
and walking non-technical users through fixes.
```

Replace the details with your own. If you have not earned A+, do not say you have.

### The skills section

Group skills so a screener can scan them in seconds, and only list what you have used well enough to answer a question about in an interview.

| Group | Examples (use only what applies to you) |
| --- | --- |
| Operating systems | Windows 10 and 11, Windows Server, macOS, Linux |
| Identity and directories | Active Directory, Microsoft Entra ID, group policy, password resets, MFA registration |
| Microsoft 365 | User and licence administration, Exchange Online mailboxes, Teams, OneDrive |
| Networking basics | TCP/IP, DHCP, DNS, VPN, Wi-Fi troubleshooting |
| Tools | Ticketing systems you have used, remote support tools, PowerShell basics |
| Hardware | Desktop and laptop repair, printers, peripherals |

Mirror the exact names in the posting when they are true, such as the ticketing system or remote desktop tool. If the posting says Active Directory and you built a lab domain, list Active Directory and describe the lab under Projects.

## Turn practice into evidence

Hiring managers know that entry-level candidates lack job history. What they want to see is that you have done the work. The most credible evidence is something you can explain step by step in an interview.

### Home lab and sandbox projects

Pick two or three, and write each as what you built, the tools you used and what you learned or fixed. Label them as lab work.

- **Windows domain lab.** Build a domain controller, join a client, create users, groups and a group policy, and document a password reset and a locked-out account procedure. The [system administrator interview guide](https://www.epifive.com/blog/sysadmin-interview-questions-ad-dns-dhcp) lists the concepts to be ready to explain.
- **Microsoft 365 admin practice.** The Microsoft 365 Developer Program offers a sandbox tenant for eligible members, and our article on [the sandbox tenant, eligibility and setup](https://www.epifive.com/blog/microsoft-365-developer-program-sandbox) lays out who qualifies and the limits. It is for development use, so use it for practice with users, licences and mailboxes rather than real data.
- **Azure free account lab.** See [building an Azure home lab on the free account](https://www.epifive.com/blog/azure-home-lab-free-account-limits) for the limits and cost controls to apply.
- **Hardware project.** Rebuild or repair a desktop, reinstall an operating system, and write a short procedure you can link from your portfolio.

### Documentation as proof

Documenting customers' problems is a listed duty, so show it. Write two or three knowledge base articles, each with a symptom, cause, steps and verification, using contoso.com style placeholders, and link to them from your portfolio. A clear article demonstrates writing skill, which the BLS lists as part of communication.

### Customer service and non-IT work

Retail, hospitality, call centre and school roles show patience, listening and handling frustrated people, all on the BLS list. Describe them in those terms, for example how you handled an upset customer, then connect them to support work.

## Writing bullets

Use a simple formula: action verb, what you did, tool or method, and result you can verify. Where you do not have a number, describe the outcome in words rather than inventing one.

| Weak | Stronger |
| --- | --- |
| Helped users with computer problems | Diagnosed and resolved Windows sign-in and printer issues for coworkers, documenting each fix for reuse |
| Knowledge of Active Directory | Built a two-machine Active Directory lab, created users, groups and a group policy, and wrote a procedure for unlocking accounts |
| Good communicator | Explained technical fixes to non-technical users by phone and in writing, confirming the problem was resolved before closing the request |
| Worked with Microsoft 365 | Practised licence assignment, mailbox setup and Teams configuration in a developer sandbox tenant |

Placeholders such as [number] can help you draft, but delete them before you send the resume. If you do not know the number, do not write one. A figure you cannot defend in an interview does more harm than leaving it out.

### Do not claim what the lab was not

If a project was a lab, say lab, home lab or practice environment. If you volunteered, say volunteer. If you were the informal IT contact in a family business, say so plainly. Interviewers ask follow-up questions, and the strongest answer is an honest one with detail.

## Certifications and education

List certificates you have earned with the issuer and date. CompTIA describes A+ as covering two exams, Core 1 for hardware and networking and Core 2 for operating systems and security, which can be taken in any order, and names the help desk support specialist as a related role. Microsoft's Azure Fundamentals (AZ-900) is a cloud starting point, and our [comparison of AWS Cloud Practitioner and AZ-900](https://www.epifive.com/blog/aws-cloud-practitioner-vs-az-900-first) helps you choose between cloud exams. Because some employers require certifications in the products they use, read the posting before deciding which to pursue.

Education goes last for most entry-level candidates unless it is your strongest evidence. List relevant coursework such as networking, server administration or information security, which the BLS says can help.

For one in-progress certification, write the name, issuer and planned exam date and label it in progress.

## Tailor each application

Spend ten minutes per application.

1. Highlight the duties and tools in the posting.
2. Move the most matching project or experience line to the top of its section.
3. Reword your skills so that they use the posting's wording where it is accurate.
4. Remove skills the posting does not mention if they push your resume past one page.
5. Save the file with your name in the filename.

## Check before you send

| Check | Why |
| --- | --- |
| Every tool in Skills appears in a project or experience bullet or can be explained | Interviewers ask about listed skills |
| Lab and volunteer work is labelled | Honesty and credibility |
| No invented numbers or employers | Easily exposed in a screen |
| One page, plain layout | Easy to scan and parse |
| Contact details and links work | Missed calls cost interviews |
| Spelling of product names is correct | Shows attention to detail |

## Common mistakes

- **Listing tools with no context.** Name where you used each one.
- **Writing a generic objective.** Replace it with a summary that names the role.
- **Padding with unrelated jobs.** Include them only if they show customer service or reliability.
- **Overstating certifications.** Earned and in progress are different.
- **Ignoring soft skills.** The BLS lists communication, customer service, listening and problem-solving as important, so evidence them.

Once the resume gets you an interview, [help desk interview questions for beginners](https://www.epifive.com/blog/help-desk-interview-questions-beginners) covers what to prepare.

## Checklist

- Your summary names the role and your strongest evidence in two lines.
- Skills are grouped, honest and mirror the posting where accurate.
- Two or three projects are labelled and written as action, tool and result.
- Certifications show issuer and date, with in-progress items labelled.
- The resume is one page and has no invented figures.

## References

- US Bureau of Labor Statistics, Computer Support Specialists: https://www.bls.gov/ooh/computer-and-information-technology/computer-support-specialists.htm
- CompTIA A+ certification: https://www.comptia.org/en-us/certifications/a/
- Microsoft Certified: Azure Fundamentals: https://learn.microsoft.com/en-us/credentials/certifications/azure-fundamentals/
- Microsoft 365 Developer Program FAQ: https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-faq

## Frequently asked questions

### Do I need a degree for an entry-level IT support job?

Not necessarily. The US Bureau of Labor Statistics says computer user support specialists usually have some college coursework, and that a high school diploma plus relevant IT certifications may qualify you. Some employers require certifications in the products they use, so read each job posting.

### How long should an entry-level IT resume be?

One page is enough for most entry-level candidates. Lead with a short summary and a skills section, then projects and experience, and cut anything that does not help the employer picture you doing the job.

### What if I have no IT experience?

Use home lab projects, volunteer work, school coursework and customer service roles, and describe each in terms of the real duties of the job: diagnosing problems, documenting them, guiding users through fixes and setting up or repairing equipment. State plainly that a project was a lab, not paid work.

### Should I list every certification, including ones in progress?

List earned certifications with the issuer and, where relevant, the exam code. You can add one in-progress item if you label it clearly, for example with a planned exam date, but do not list it as earned.