Resume Skills Section: What to Include and How to Format It

The skills section of your resume serves two masters: the ATS (Applicant Tracking System) that scans for keyword matches, and the human recruiter who wants a quick snapshot of your capabilities. Getting this section wrong is one of the most common resume mistakes — either listing so many skills that none stand out, or listing so few that the ATS filters you out. The ideal skills section is a curated, strategically ordered list that mirrors the language of the job description while honestly representing what you can do. In 2026, with ATS algorithms becoming more sophisticated, the skills section has never been more important.

Hard skills are specific, teachable, measurable abilities: programming languages (Python, JavaScript, SQL), tools (Figma, Salesforce, SAP), certifications (PMP, CPA, AWS Solutions Architect), techniques (regression analysis, A/B testing, financial modelling), and languages (Spanish, Mandarin, French). These are the skills that ATS systems scan for most aggressively because they are objective and easy to match against job requirements. Every hard skill you list should appear somewhere in the job description or be a well-known equivalent. If the job asks for "Tableau" and you know "Power BI," list both — but list Tableau first. If the job asks for "React" and you only know "Angular," do not list React. Honesty matters because you will be tested in the interview.

Soft skills — leadership, communication, teamwork, problem-solving, time management — are trickier. Listing "excellent communicator" on your resume proves nothing; anyone can write that. The best approach in 2026 is to demonstrate soft skills through your experience bullet points rather than listing them in the skills section. Instead of writing "Leadership" in your skills list, write "Led a cross-functional team of 12 to deliver a $2M product launch 3 weeks ahead of schedule" in your experience. However, if the job description explicitly lists soft skills as requirements (many do), include 2-3 of the most relevant ones in your skills section for ATS matching purposes — but only those that appear in the job posting.

How many skills should you list? The sweet spot is 8-15 skills for most roles. Fewer than 8 and you risk missing ATS keywords. More than 15 and you dilute the impact — recruiters do not read long skills lists, and listing 30 skills signals that you are padding your resume rather than curating it. Prioritise the skills mentioned in the job description, then add your strongest differentiators. For technical roles (engineering, data science, IT), you can push to 15-20 because technical skills are more granular and recruiters expect a longer list. For non-technical roles (marketing, HR, operations), keep it closer to 8-12.

Formatting matters more than most people think. The two most effective formats are a multi-column list and a categorised list. The multi-column list (3 columns of skills) is space-efficient and scannable — it works well for 8-12 skills. The categorised list groups skills under subheadings like "Programming Languages," "Cloud Platforms," "Data & Analytics," and "Soft Skills" — this works better for 15+ skills and is especially effective for technical roles. Avoid skill bars, star ratings, or percentage indicators (e.g., "Python: 90%"). These are meaningless — 90% of what? — and they waste space. ATS systems cannot parse visual skill ratings, and recruiters find them gimmicky.

Craft Resume AI analyses the job description you are targeting and automatically identifies the highest-priority skills to include on your resume. The AI matches your existing skills against the job requirements, flags any gaps, and suggests additions based on industry standards. This means your skills section is always aligned with what the ATS is scanning for and what the recruiter expects to see. Build your optimised skills section at craftresumeai.com in seconds — no guessing, no keyword stuffing, just a clean and strategic skills list that gets you past the filter and into the interview.