What to put in your resume skills section

The skills section is one of the most misunderstood parts of a resume. Job seekers treat it as either an afterthought — a random pile of adjectives like "team player" and "hard worker" — or a dumping ground for every tool they've ever touched. Both approaches waste the one place on your resume where a recruiter (and the software that screens you first) can scan your qualifications in about three seconds.

Done right, the skills section does a specific job: it lists the concrete, verifiable abilities that match what a particular employer is looking for, in language that mirrors the job posting. This article walks through exactly what belongs there — hard skills versus soft skills, how many to list, how to pull the right ones from a job description, what to cut, and where the section should sit on the page.

Hard skills vs. soft skills — and why the section should lean hard

Hard skills are specific, teachable, and provable: Python, SQL, Adobe Illustrator, financial modeling, Spanish fluency, forklift certification, QuickBooks, Kubernetes. Anyone can verify whether you have them. Soft skills are behavioral traits: communication, leadership, adaptability, problem-solving. They matter enormously on the job, but they're nearly worthless as bullet-point claims because everyone lists them and no one can prove them by writing the word down.

Your skills section should be dominated by hard skills. If you want to convey soft skills, do it where they're backed by evidence — in your experience bullets. "Led a 6-person team through a platform migration that shipped two weeks early" demonstrates leadership far more credibly than the word "leadership" sitting in a list. Reserve the skills section for the concrete, keyword-rich abilities that a recruiter is actually scanning for.

Rule of thumb: if a skill can't be verified or demonstrated, it doesn't belong in your skills list. Hard skills go in the section; soft skills should be proven inside your experience bullets.

How many skills to list

There's no magic number, but a useful range is roughly 8 to 15 relevant hard skills. Fewer than that and the section looks thin; many more and it turns into an unscannable wall where the important skills drown. The goal isn't to prove you've touched a lot of tools — it's to make the most relevant ones impossible to miss.

• Prioritize ruthlessly: put the skills the job actually asks for first.
• Group related skills so the section is scannable — e.g. "Languages: JavaScript, Python, Go" / "Tools: Docker, Git, Jira."
• Cut anything obsolete or assumed. Listing "Microsoft Word" or "email" for a professional role reads as filler.
• Don't list a skill you can't discuss in an interview. Padding is a fast way to get caught.

Match the job description — this is the whole game

The single highest-leverage move is to align your skills section with the exact language of the job posting. Read the description and pull out the hard skills, tools, and qualifications it names. If it says "PostgreSQL," list "PostgreSQL," not just "SQL databases." If it says "stakeholder management," and you genuinely do it, use that phrase. Recruiters skim for the terms they wrote, and applicant tracking systems (ATS) parse your resume looking for those same terms.

This matters for two audiences at once. A human recruiter matching your resume against a req wants to see their required skills echoed back. And ATS software parses your resume into fields and matches keywords — if the posting's key term appears nowhere on your resume, you're easier to overlook. The fix is not keyword-stuffing; it's honest mirroring. List the real skills you have using the words the employer used.

Only claim what's true

Matching the description never means inventing skills. If the job wants Tableau and you've never used it, don't list it — you'll expose it in the interview or on day one. Instead, list the adjacent skills you do have (Power BI, Excel, data visualization) and, if it's a genuine gap you can close, learn the basics before you apply. Tailoring is about surfacing your real, relevant skills for each role — not fabricating a match.

Cut the fluff

Certain phrases add nothing because they're unprovable and universal. Delete these from your skills section: "hard worker," "team player," "detail-oriented," "self-starter," "go-getter," "results-driven," "excellent communication skills." They cost you space and signal that you didn't know what to put there. Replace each one with either a concrete hard skill or a specific accomplishment somewhere else on the resume.

• Vague: "Strong analytical skills." Better: "SQL, Excel (pivot tables, VLOOKUP), Google Analytics."
• Vague: "Great communicator." Better: prove it — "Wrote weekly release notes read by 200+ internal users."
• Vague: "Proficient in Microsoft Office." Better: name only the apps that matter for the role, and only if they're non-obvious.

Where the skills section belongs

Placement depends on your experience and the type of role. For most experienced professionals, the skills section sits below your work experience — because your experience is the stronger selling point and should lead. For technical roles (software, data, IT) where a specific tech stack is a hard requirement, a skills section near the top makes sense so hiring managers can confirm the match instantly.

If you're early-career, changing fields, or have gaps, a skills section higher on the page can front-load your relevant abilities before the experience that's still thin. Whatever you choose, keep the format simple and ATS-friendly: a clean list or grouped categories in the main body of the document. Avoid burying skills inside columns, tables, text boxes, or graphics that ATS parsers can mangle or skip entirely.

A quick before-and-after

Weak skills section: "Hard-working, detail-oriented team player with strong communication skills, proficient in Microsoft Office and passionate about results." It's all unprovable filler and contains zero searchable, role-specific terms.

Strong skills section for a data analyst role: "SQL, Python (pandas, NumPy), Tableau, Excel (pivot tables, Power Query), Google Analytics, A/B testing, data cleaning, dashboard design." Every item is a concrete, verifiable hard skill, and each maps to something a data-analyst posting would actually ask for.

Tailoring for every job, without the busywork

The catch with all of this: the ideal skills section is different for every posting, because every posting names different tools and priorities. Rewriting it by hand for each application is tedious, which is why most people skip it — and lose the match. Tailr helps automate the tailoring: it reads a job description, surfaces the relevant skills and keywords to feature, and keeps your resume formatted so ATS software can parse it cleanly. You still decide what's true and what to include; the tool removes the repetitive part.

Bottom line: fill your skills section with 8–15 real, verifiable hard skills, phrased to match the specific job you're applying to. Prove your soft skills in your experience bullets instead of listing them. Cut every unprovable cliché. Then place the section where it does the most good for your background — and tailor it for each role.