Skills for a Resume: 100+ Examples for Different Jobs

2. What skills should you put on a resume?

Put the skills you genuinely have that are relevant to the specific job you are applying for and that you could talk about if someone asked. That is the whole test, and the strongest resume skills meet three conditions at once.

Relevant skill vs. random skill

Most people have more skills than their resume has room for, so the real work is selection. A relevant skill helps a reader picture you doing this job. A random skill is simply something true about you.

For an administrative assistant role, calendar management, Microsoft Excel, document preparation and customer communication describe the actual job. An unrelated technical ability, however genuine, does less work in that context. For a software developer role, programming languages, version control, testing and databases carry far more weight than a generic phrase like "hard worker", which every applicant could write and none can prove.

Relevance also shifts between applications. The same skill can be a headline item on one resume and a distraction on the next, which is why a single fixed skills list reused for every job tends to underperform a short list adjusted each time. If you are also assembling the surrounding document, the copy-and-paste resume template shows where this section fits.

3. Hard skills for a resume

Hard skills are specific, teachable capabilities used to perform the work: tools you operate, methods you apply, systems you know. They are usually learned through training, education or practice, and they can generally be described precisely — which is what makes them useful on a resume. "Accounts reconciliation" means something. "Detail-oriented" is a claim.

Two cautions on that list. First, a skill appearing here does not mean it belongs on your resume — cybersecurity, for instance, is worth listing only if you have genuinely worked on it, not because it sounds valuable. Second, in regulated fields a skill is not the same thing as a credential. Clinical tasks, electrical work and many trades involve licensing, certification and scope-of-practice rules, and listing a skill never implies you hold the license behind it. Credentials belong in a certifications section, stated exactly as you hold them.

For a deeper breakdown of technical and job-specific abilities, see our guide to hard skills, including 100+ examples and a hard-vs.-soft-skills comparison.

4. Soft skills for a resume

Soft skills describe how you work: how you communicate, how you handle pressure, how you deal with colleagues and customers, how you organize yourself. They matter in almost every role, and they are also the part of a resume most likely to turn into filler, because anybody can type them.

Show them, don't just list them

A line reading "hard-working, motivated, passionate, team player" tells a reader nothing they can check. The same qualities land differently when an experience bullet shows the behaviour instead of asserting the trait.

Write those bullets from your own work. Do not add numbers, percentages or team sizes you have not actually verified — an invented figure is the fastest way to lose a conversation you were otherwise winning. A short soft-skills list in the skills section is fine; the persuasion happens underneath it.

5. Technical skills for a resume

Technical skills are often assumed to mean programming. In practice they cover any specialized tool, system or process a job depends on — an ERP system in operations, an accounting package in finance, a scheduling platform in healthcare administration, a CAD package in design. If the work requires learning a specific system, that system is a technical skill.

Name the tools you can actually use unsupervised. Listing a language you read about, or a platform you watched a colleague operate, creates an expectation someone will test. Avoid inventing proficiency labels too — "expert", "advanced", "90%" are self-assessed, mean different things to different readers, and are rarely worth the space. Where a genuine distinction exists, describe it plainly: the systems you used daily, the ones you have worked in occasionally.

6. Computer skills for a resume

Computer skills overlap with technical skills, but the phrase usually refers to the everyday software people use to do office and administrative work. It helps to group them from general to specialized.

Some older advice suggests listing "internet research" or "email" as computer skills. For most roles today those are assumed, and including them can make a section look thin. The exception is where the context makes them genuinely meaningful — a role explicitly aimed at applicants returning to office work, or a posting that names them as requirements.

Specificity helps more than volume here. "Microsoft Office" is a reasonable shorthand, but if your Excel work involves pivot tables, lookups or building recurring reports, naming Excel separately tells the reader something the umbrella term hides.

7. Good skills for a resume

There is no universal list of best skills, and any article claiming otherwise is ignoring the job you are applying to. A good resume skill is relevant to the role, accurate, specific enough to carry meaning, useful to the employer, and supported by evidence somewhere in your application.

That said, some skills appear across a wide range of jobs and are worth checking yourself against. Twenty broadly useful examples:

Relevance still decides. "Budgeting" is a strong entry on a finance or team-lead application and close to noise on a warehouse one. Run each candidate skill through a single question: would the person hiring for this specific role care?

Special skills for a resume

People searching for "special skills" usually mean abilities beyond the basic duties of the role — the things that distinguish two otherwise similar candidates. Common examples:

These carry weight precisely because they are checkable. Never list a certification, a language proficiency or a specialized ability you do not actually have. A second language claimed loosely tends to surface in the interview, and equipment or safety certifications are frequently verified before a start date.

8. Skills for a resume by job

These are example skills that tend to matter in each role. Treat them as prompts for recalling your own experience, not as a list to copy wholesale — and where a skill depends on a license, certification or scope of practice, only include it if you hold it.

Notice how little overlap there is between these lists. That is deliberate: a skills section made of communication, teamwork and organization reads identically for a truck driver and a data analyst, which is exactly why it fails to distinguish either. The role-specific items do the work, and the transferable ones sit around them.

Once you know which skills a role rewards, it is worth knowing what it typically pays. You can check the wage range for your occupation and state before you apply or negotiate.

9. How to choose skills from a job description

The job description is the most reliable guide to what a particular employer wants, and reading it properly takes about five minutes. Take a fictional posting excerpt:

"We're looking for an administrative coordinator who can manage calendars, prepare reports, communicate with customers and maintain accurate records. Experience with Excel is preferred."

Each requirement maps to a skill you could name, if it is true for you:

The conditional matters more than the mapping. Add each of these only if it genuinely describes work you have done. A posting is a description of what the employer wants, not a list of things to assert about yourself, and the interview is built around the same requirements — which means anything you added without basis is likely to be the first thing you are asked about.

Nor should you copy every keyword. Packing a skills section with terms lifted from the posting produces a list nobody can defend, and no wording guarantees how any particular employer or applicant tracking system treats an application. Using the employer's vocabulary where it honestly describes your work is useful because it is recognizable, not because it is a trick.

One practical habit: mark the requirements you can support, the ones you partly meet, and the ones you cannot. The first group becomes your skills section. The second is worth addressing in your cover letter. The third tells you honestly how close the role is.

10. How to list skills on a resume

Skills can appear in three places on a resume, and the strongest applications use all three rather than relying on any one.

In practice that looks like a compact list:

SKILLS
Microsoft Excel • Reporting • Customer Service • Scheduling • CRM Software

…supported by evidence further down the page: "Prepared weekly Excel reports and maintained customer account records for the service team." The bullet does something the list cannot — it puts the skill in a context a reader can evaluate. A resume that only lists skills asks to be believed; one that lists and demonstrates them does not have to.

Skills in the professional summary

A few of your strongest, most relevant skills can also appear naturally in the summary at the top: "Operations coordinator with five years of experience in logistics, vendor communication and process improvement." Choose them for this specific job, and keep it to the ones the role is built around. For wording, resume summary examples covers the summary itself in detail.

Where the section sits in the document

Formatting matters less than placement and consistency. A skills section usually sits either directly under the summary — when skills are the main qualification, as in technical and trade roles — or after the experience section, when your work history is the stronger argument. Either way it should look like part of the same document: same heading style, same spacing, no decorative rating bars. The resume template shows the full structure this section fits into.

11. Skills to avoid putting on your resume

Very few skills are universally bad. What weakens a section is usually a mismatch between the skill and the situation, and a handful of patterns account for most of it:

• • Skills you do not actually possess, at any level of exaggeration.
• • Vague buzzwords that would be equally true of any applicant.
• • Skills unrelated to the role, however genuine they are.
• • Basic abilities already assumed for anyone doing the job.
• • Outdated tools, unless the employer still uses them.
• • Unsupported proficiency claims and self-assigned expert ratings.
• • Dozens of skills crammed into one section until none of them register.

Several of these are fixable rather than removable. A vague entry often hides a specific one:

Only swap in the more specific version when it is accurate. "Client communication" is an improvement on "communication" if you communicated with clients; if you did not, the vaguer term was at least true. Precision is valuable because it is checkable, which is also why it backfires when invented.

12. Resume skills examples

Complete skills sections for different kinds of roles. Copy the closest one and replace the entries with skills that are genuinely yours — bracketed placeholders mark the parts that depend on your own tools and experience.

SKILLS
Project Coordination • Microsoft Excel • Reporting • Customer Communication • Process Improvement • Documentation

SKILLS
Calendar Management • Microsoft Office • Google Workspace • Document Preparation • Data Entry • Customer Service

SKILLS
Customer Support • CRM Software • Account Assistance • Conflict Resolution • Written Communication • Product Knowledge

SKILLS
[Programming Language] • Git • SQL • Testing • APIs • [Relevant Framework]

SKILLS
Excel • SQL • Data Cleaning • Data Visualization • Reporting • [Relevant BI Tool]

SKILLS
Inventory Management • Order Accuracy • [Warehouse System] • Shipping and Receiving • Safety Procedures • Team Coordination

SKILLS
Patient Intake • Vital Signs • [EHR System] • Appointment Scheduling • Medical Documentation • Insurance Verification

Six to eight entries is a common length for these sections, though there is nothing special about that number — a technical role may justify more, an early-career resume fewer. What matters is that every line survives the question "could I talk about this for two minutes?" If the answer is no, delete it.

Once the section is written, read it beside the job posting one last time. The skills the employer emphasized should be visible without searching, and anything that has nothing to do with the role can usually go.

13. Frequently asked questions