Resume Skills Section: Hard Skills, Soft Skills and What ATS Looks For

A strong resume skills section lists the specific hard skills the target job requires, in the same terms the job description uses, organized so a recruiter can scan it in seconds. Soft skills belong mostly in your experience bullets, where you can prove them. Applicant tracking systems search for job-relevant terms, so matching your skills to the posting truthfully matters more than listing as many skills as possible.

Hard skills vs soft skills

Understanding the difference shapes what goes in this section.

Hard skills

Hard skills are specific, teachable, and usually verifiable. Examples:

Programming languages and frameworks such as Python, Java, or React.
Platforms and tools such as Salesforce, AWS, Jira, or Tableau.
Methods such as financial modeling, regression analysis, or Agile delivery.
Certifications and licenses.
Languages spoken, at a stated level.

These are the skills recruiters search for and the terms an ATS is most likely to match against a job description.

Soft skills

Soft skills describe how you work: communication, leadership, problem solving, collaboration, adaptability. They matter a great deal to employers, but listing them as single words is weak evidence. Anyone can type "excellent communicator."

The better approach is to demonstrate them in experience bullets. Instead of listing "stakeholder management," write a bullet like "Coordinated requirements across finance, operations, and IT for a billing system migration."

What ATS looks for in skills

An ATS resume is one that applicant tracking systems can parse and search accurately. For the skills section, that means:

Relevant terms. Recruiters often search their ATS for specific skills. If the job asks for "Kubernetes" and your resume does not mention it anywhere, a search may not surface you.
Exact wording where it applies. Use the posting's terminology. If the job says "Microsoft Power BI," write that rather than a vague "BI tools."
Both full names and abbreviations for terms that are commonly written either way, such as "Continuous Integration/Continuous Deployment (CI/CD)."
Plain text. Skill bars, star ratings, icons, and graphics can confuse parsers and say little to humans.
A standard heading. "Skills" or "Technical Skills" is easier to recognize than creative alternatives.

For more on formatting, see ATS resume format and common ATS resume mistakes.

How to build your skills list

Start with the job description. List every hard skill, tool, and method it mentions. See resume keywords from the job description.
Mark which ones you genuinely have. Be honest about depth. Hands-on project experience is different from having completed a tutorial.
Prioritize must-haves. Put the skills the posting emphasizes first.
Add your other strengths that are relevant to the role, even if not listed.
Cut what does not apply. Outdated tools and unrelated skills dilute the list.
Check consistency. Every major skill in the list should appear in at least one experience bullet showing where you used it.

That last step matters. A skills section that is not backed by experience reads as keyword padding, and interviewers will ask about it.

Formatting the section

For most roles

A single list of 8 to 15 skills, separated by commas or in two or three short lines, is usually enough.

For technical and IT consulting roles

Grouping helps readers scan a longer list. For example:

Languages: Python, SQL, Scala
Data platforms: Spark, Databricks, Snowflake, Airflow
Cloud: AWS (S3, Glue, Redshift, Lambda), Azure Data Factory
Practices: data modeling, CI/CD, data quality testing

Avoid adding years of experience next to every skill unless the role or client specifically asks for it, and if you do, make sure the numbers are accurate.

Where to put it

For most resumes, place the skills section just below the summary. Technical roles, IT consulting profiles, and career change resumes especially benefit from having skills high on the page. For senior roles where experience carries the story, a shorter skills section can sit lower.

Tailor it for every role

The skills section is one of the easiest parts of a resume to tailor. Reordering skills so the job's must-haves appear first, and adding relevant skills you have but did not list, can make a meaningful difference in how quickly a recruiter sees the match. See how to tailor a resume to a job description.

Common mistakes

Listing every tool you have ever touched.
Including skills you cannot discuss in an interview.
Using graphics or ratings instead of text.
Listing soft skills as single words with no supporting evidence.
Leaving the same generic list on every application.

Recruiters at staffing firms use Knuckler AI to generate a tailored, ATS-checked resume for each job description, with the skills section reordered around the posting's requirements and grounded in the candidate's actual experience, then review it before submission.

Key takeaways

Put specific, verifiable hard skills in the skills section, and show soft skills through accomplishments.
Match the job description's wording where it truthfully applies, and include common abbreviations.
Keep the list focused, plain text, and under a standard heading.
Back every listed skill with at least one experience bullet.
Reorder and adjust the skills section for each application.

Frequently asked questions

How many skills should I list on a resume?

There is no fixed number, but a focused list of roughly 8 to 15 relevant hard skills is easier to scan than a long dump. Technical roles may group more skills into categories.

Should I include soft skills in the skills section?

Usually it is better to show soft skills through accomplishments in your experience section. A list of soft skill words on its own carries little weight with recruiters.

Where should the skills section go on a resume?

For most resumes, place it near the top, after the summary, especially in technical fields. Career changers and IT consultants often benefit from having it high on the page.