What Skills to Put on a Resume (and Which to Leave Off)

The skills section looks like the easiest part of a resume, which is exactly why most people get it wrong. They dump every tool they have ever touched into a list, pad it with "communication" and "Microsoft Word," and wonder why nothing matches. The skills you list, and where you list them, decide whether your resume matches the job in front of both the software and the human reading it.

Hard skills vs. soft skills

Hard skills are specific, teachable, and verifiable: Python, wound care, Salesforce, forklift certification, French, payroll processing, Adobe Premiere. You either can do them or you cannot, and an interviewer can test them.

Soft skills are how you work: communication, leadership, prioritization, negotiation, patience with difficult customers. They matter enormously on the job, but they are nearly worthless as bare words in a list, because anyone can type "leadership" and most people do.

The practical split:

• Hard skills go in your skills section as plain, matchable terms.
• Soft skills get demonstrated in your experience bullets, not listed. "Trained and mentored 5 new hires, all retained past their first year" proves leadership better than the word "leadership" ever will.

If a job posting explicitly names a soft skill as a requirement ("must communicate with executive stakeholders"), you can echo it once, but back it with a bullet that shows it happening.

How ATS matching actually works

An applicant tracking system does not judge your potential. Most of them do something much simpler: the recruiter searches or filters for terms from the job description, and resumes containing those terms surface. Some systems auto-score resumes against the posting the same way.

What that means in practice:

• The job description is your keyword source. Read it twice. The skills it repeats, or lists under "requirements" rather than "nice to have," are the ones your resume must contain, assuming you actually have them.
• Match the exact wording. If the posting says "search engine optimization," write "search engine optimization (SEO)," not just "SEO." Spell out acronyms once with the abbreviation beside them so both forms are searchable.
• Synonyms are not guaranteed matches. "Customer relationship management" and "Salesforce" are related, but a filter for one may not catch the other. If you have the specific tool the posting names, name it.
• Keep formatting simple. Skills buried in text boxes, columns, graphics, or skill-rating bars (four dots out of five for "Excel") can parse badly or not at all. Plain text lists parse reliably.
• Do not keyword-stuff. Pasting the job description in white text or listing 40 skills does not work. Recruiters see the parsed text, and a resume that matches on keywords but collapses under human reading is a fast rejection.

The honest way to "beat" the ATS is boring: have the skills, and state them in the same language the employer used.

Where skills go on the resume

Skills should appear in two places, doing different jobs:

1. A dedicated skills section. A short, scannable list, usually right under your summary or near the bottom. Group it if you have more than 8-10 entries:

> Technical: SQL, Python (pandas), Tableau, Excel (pivot tables, VLOOKUP) > Marketing: Google Analytics 4, Meta Ads Manager, email automation (Klaviyo) > Languages: Spanish (professional working proficiency)

Aim for 8-15 skills, all relevant to the target job. Thirty skills is not a stronger list; it is a diluted one, and it signals you did not choose.

2. Woven into your experience bullets. This is where skills become believable, because they appear attached to results:

> Built weekly sales dashboards in Tableau from SQL queries, replacing a manual report that took 4 hours per week. > Administered medications and IV therapy for a 6-patient med-surg assignment per shift.

A skill that appears only in the list looks like a claim. A skill that appears in the list and in a bullet with an outcome looks like experience. For your most important 3-5 skills, aim for both.

What to list, by field

Pick from these patterns, keeping only what you genuinely have and what the posting asks for:

• Software engineering: languages (Python, TypeScript), frameworks (React, Django), infrastructure (AWS, Docker, PostgreSQL), practices (CI/CD, code review). Skip listing every language you touched once in school.
• Nursing and healthcare: licenses and certifications first (RN, BLS, ACLS), then clinical skills (IV insertion, telemetry, wound care), then systems (Epic, Cerner).
• Sales: CRM (Salesforce, HubSpot), prospecting tools (LinkedIn Sales Navigator), methodology if the posting names one (MEDDIC, SPIN), plus deal types: outbound, enterprise, renewals.
• Trades and warehouse: certifications (OSHA 10, forklift, CDL Class A), equipment (reach truck, pallet jack, RF scanners), systems (WMS software by name if you know it).
• Teaching: certifications and endorsements, classroom platforms (Google Classroom, Canvas), specific competencies (IEP implementation, ESL instruction, curriculum design).
• Admin and operations: scheduling and ERP tools (QuickBooks, SAP, Workday), Excel at a specific level (pivot tables, macros), records management, vendor coordination.
• Marketing: analytics (GA4), ad platforms (Google Ads, Meta), SEO tools (Ahrefs, Semrush), email platforms, and content skills tied to formats (short-form video, long-form SEO writing).

Skills to cut

Some entries actively weaken a resume because they signal filler or a template last updated years ago:

• Assumed-baseline software: Microsoft Word, email, internet research, typing (unless a posting specifies a words-per-minute requirement, as some data-entry roles do).
• Bare soft-skill words: hardworking, team player, detail-oriented, multitasking. Show these in bullets or drop them.
• Dead or irrelevant tech: tools discontinued years ago, or the framework you used at one job in 2014 and never since, unless the posting specifically asks for it.
• Hobby-level claims presented as professional skills: "photography" on an accounting resume says nothing. If it is not relevant to the job, it is taking space from something that is.
• Skill self-ratings: star ratings, percentage bars, "Excel: 80%." They parse poorly and invite the reader to doubt the top of your scale.
• "References available upon request." Not a skill, and everyone already assumes it.

When in doubt, apply one test: would the hiring manager for this specific job care? If not, cut it.

The honesty rule

Never list a skill you do not actually have. Not "familiar with" something you opened once, not a tool you plan to learn before the start date. There are three reasons, and all of them are practical:

• You will be tested. Interviews probe the skills list directly. A five-minute conversation about Salesforce exposes whether you have used it.
• It poisons your real skills. Once an interviewer catches one inflated claim, they discount everything else on the page.
• Even if it works, it fails. Getting hired into a job that assumes a skill you lack is a miserable first ninety days.

The honest version has a vocabulary: "working knowledge of," "coursework in," or simply listing the skill you do have that is adjacent. If a posting requires something you lack, that is information about fit, not an invitation to improvise.

Tailoring, every single time

The right skills list is not fixed. It shifts with every posting: the same analyst might lead with SQL for one application and Excel modeling for another, because that is what each employer asked for. Reading every job description and re-weighting your skills to match is the part of applying that people skip when they are tired, and it is precisely the part Qlivik does automatically, matching your real skills against each posting and tailoring the resume before you approve the application.

List what you have, say it the way the employer says it, prove the important ones in your bullets, and cut the rest. That is the whole skill.