Skills for a Resume: What to List, by Role and Level

Choose resume skills by comparing the work you have done with the work the role requires. A useful skills section makes that connection clear without becoming an inventory of every tool you have ever encountered.

This guide offers job-family lists and career-stage decisions: what to keep, where to place it and how to describe your level. Examples and numerical results are fictional illustrations; adapt the structure using your own experience. The lists are options, not a set of qualifications every applicant needs.

Use these checks to decide which skills deserve space.

Review each item and ask what you could say about it in an interview. If you cannot explain a meaningful use, narrow the claim or leave it out. Important skills often deserve supporting bullets, but you do not need a separate bullet for every tool in a concise list.

Specific tools and methods can clarify your experience. “Excel pivot tables” tells the reader more about one task than “spreadsheets,” but either term can be useful in context. Select the options relevant to the vacancy and your background. These groups include technical, interpersonal and process skills; list licenses or certifications separately when required.

A category and product name can work together, such as “CRM: Salesforce” or “EHR documentation: Epic,” when both describe your experience. They are not interchangeable: using another CRM does not establish Salesforce experience, and using one cloud platform does not establish AWS experience.

If AI-assisted work is relevant, name the task and how you checked the output. A fictional example is: “Used an approved AI tool to draft campaign variants, then reviewed factual claims and prepared two versions for an A/B test.” Do not imply that drafting variants proves experiment-design expertise.

Keep credentials accurate. OSHA Outreach 10- and 30-hour courses provide completion cards, not certifications. EPA Section 608 certification has defined equipment types; list the actual credential held. For nursing tasks, follow the license, competence and policy requirements described in the NCSBN scope framework.

Choose interpersonal skills that relate to the responsibilities. A label can help organize the section, while an example explains what you did. There is no reliable universal division between words that are “screened” and words that are only read by humans.

The guide to hard and soft skills gives more examples of combining technical capability with how you work.

Eight to twelve entries can be a useful starting point for a concise skills section, but relevance and readability matter more than the count. A technical specialist may need several grouped lines; an early-career applicant may need fewer entries.

Skills can appear in three places, each with a different purpose.

Choose placement according to your strongest relevant evidence. A career changer might place a skills section near a summary, while a student may lead with education or a strong project. An experienced applicant may put work history first. See resume section order and skills section examples for alternatives.

Grouping can make a technical list easier to read: languages, data tools and delivery platforms, for example. Use clear text and a recognizable heading, then check the exported document and any application preview.

Prefer descriptive text to an unexplained rating bar. A four-dot rating has no shared meaning unless the scale is defined. Labels such as “beginner” or “advanced” can provide context, but are clearer alongside tasks you can perform.

For example, “Python: data-cleaning scripts for a university research project” describes a different level and setting from “Maintained a Python service handling 40,000 daily requests.” Both are fictional illustrations; use the one that reflects your actual experience, not the larger number.

When a posting asks for years of experience, give an accurate duration where useful and do not add overlapping projects together as separate years. For languages, use a recognized assessment level if you have one or a clear description of your actual ability, without implying an examination result you did not earn.

Read the full posting, noting required qualifications, responsibilities and preferred experience. Identify tools, methods and credentials that you genuinely have. Use the employer’s terminology where it describes the same thing, spelling out an abbreviation when it improves clarity.

Some systems support literal searches: Greenhouse documents Boolean candidate searches. That does not establish one universal filter or rejection threshold across employers. Write naturally and keep past titles, responsibilities and qualifications accurate. See how to identify relevant resume keywords.

A resume tool can help compare wording and suggest edits, but cannot reveal the employer’s private screening settings or verify your skills. Review each suggestion against your records and the role rather than pursuing a score as a hiring prediction.

Use relevant tools and methods from coursework, projects or campus work, with the setting clear. A statistics project in R can support an R entry if you can explain what you did. A course title alone does not show your level with every tool mentioned in class. Choose placement based on the strongest relevant education or project evidence, rather than automatically placing skills first.

Part-time work and volunteering can provide concrete examples: a POS system used during retail shifts, cash reconciliation, inventory counts, event registration or fundraising outreach. Describe the actual tasks and supervision. A short, accurate list with one or two useful examples is preferable to filling space with unsupported adjectives.

Emphasize the skills relevant to the next role, including specialist methods, tools and responsibilities. There is no year when a basic tool becomes automatically unworthy of space: spreadsheet or document work may still be central to a senior position. Remove repetitive or irrelevant items and explain your more substantial contributions in experience bullets.

Show the management responsibilities you actually held: budgeting, hiring, vendor negotiation, planning or coordinating delivery. Distinguish direct reports from project contributors and budget ownership from tracking expenditure. Retain hands-on tools when they matter to the role; the right balance depends on the position rather than a fixed count.

Keep older skills when the target role still needs them, including legacy systems. Remove obsolete detail when it does not help the reader, but do not rename an old tool as a newer product you have never used. A migration example can emphasize the method while accurately naming the system.

Consolidate repeated versions where the distinction is unimportant. Retain a version number when compatibility or maintenance experience is part of the requirement. Consider whether an optional skill points toward work you want to do, while keeping required qualifications and answers truthful. The guide on how far back a resume should go covers relevance across a longer history.

Use these field lists to brainstorm, then select only relevant skills you have. Each line is an option rather than an instruction to claim every named tool. Licenses, credentials and regulated tasks need their own accurate status and scope.