Skills to List on Resume: The Complete Category-by-Category Checklist

Hard Skills: The Non-Negotiable Foundation

Hard skills are teachable, measurable abilities that you've acquired through education, training, or hands-on experience. They're the backbone of any skills section because they're the primary keywords ATS systems scan for. Hard skills fall into several subcategories. Technical skills include programming languages (Python, JavaScript, Java, C++), frameworks (React, Django, Spring Boot), and technical methodologies (Agile, DevOps, CI/CD). Analytical skills include data analysis, statistical modeling, financial forecasting, market research, and business intelligence. Industry-specific skills vary widely: a structural engineer lists AutoCAD, REVIT, and ETABS; a nurse lists IV therapy, wound care, and telemetry monitoring; a digital marketer lists SEO, PPC campaign management, and marketing automation. The key to listing hard skills effectively is specificity. Don't write 'programming' — write 'Python, JavaScript, SQL.' Don't write 'data analysis' alone — add the tools: 'Data Analysis (Python, Tableau, SQL, Power BI).' Recruiters and ATS systems search for exact tool names, not general categories. Version numbers can matter for technical roles: 'React 18' signals current knowledge versus someone who learned React 15 five years ago and hasn't kept up. However, only include version numbers for tools where the version represents a meaningful difference in capability. List your hard skills in descending order of relevance to the target role, not in order of personal proficiency. The skill the employer needs most should appear first, regardless of whether it's your absolute strongest competency.

Soft Skills: When and How to Include Them

Soft skills are interpersonal and self-management abilities that affect how you work with others and approach your job. They include leadership, communication, problem-solving, adaptability, time management, and emotional intelligence. The debate about whether soft skills belong on a resume has a nuanced answer: include them only when they're explicitly requested in the job description and only in their most specific form. 'Leadership' is vague and unverifiable on paper. 'Cross-functional team leadership' is specific and implies a concrete experience. 'Communication' means nothing. 'Stakeholder communication,' 'executive presentations,' or 'technical writing' each tell a distinct, useful story. When the job posting asks for 'strong interpersonal skills' or 'ability to work in a fast-paced environment,' those are signals to include relevant soft skills. But instead of echoing the generic phrase back, translate it into something concrete. 'Fast-paced environment' translates to 'multi-project prioritization,' 'deadline management,' or 'rapid iteration.' The best practice for soft skills is a two-pronged approach: include two to three highly specific soft skills in your skills section (ideally using the job description's exact language), then prove them through your achievement bullet points. 'Conflict Resolution' in your skills section paired with 'Mediated a contract dispute between engineering and vendor teams, preserving a $1.8M partnership' in your experience section creates a complete, credible picture.

Tools, Software, and Technology Proficiency

In 2026, your technology stack is often the deciding factor in whether you pass the initial screen. Hiring managers need people who can be productive from day one, and knowing the company's existing tools eliminates ramp-up time. Organize your tools by function rather than listing them randomly. A project manager might structure theirs as: 'Project Management: Jira, Asana, Monday.com, Microsoft Project. Collaboration: Slack, Confluence, Miro, Notion. Analytics: Power BI, Tableau, Google Analytics. Productivity: Microsoft 365, Google Workspace.' This categorization helps recruiters quickly find what they're looking for. For technical roles, create a dedicated 'Technical Stack' or 'Technologies' subsection with clear groupings: 'Languages: Python, JavaScript, Go. Frameworks: React, FastAPI, Django. Databases: PostgreSQL, MongoDB, Redis. Cloud: AWS (EC2, S3, Lambda, RDS), Docker, Kubernetes. Tools: Git, GitHub Actions, Terraform, Datadog.' Always match the tool names used in the job description. If they say 'MS Excel,' write 'MS Excel,' not 'Microsoft Excel' or 'Spreadsheets.' ATS matching is often literal. If the posting mentions a tool you haven't used but have experience with a direct competitor (say, they want Jira but you've used Asana), list both: your actual experience and note familiarity with the requested tool. Something like 'Asana (primary), Jira (familiar)' gives you the keyword match while staying honest about your experience level.

Languages, Certifications, and Specialized Qualifications

Language skills are increasingly valuable in a globalized job market, and many candidates undervalue them. If you speak any language beyond English at a professional level, list it with a clear proficiency indicator: 'Spanish (Native),' 'Mandarin (Professional Working Proficiency),' 'French (Conversational),' 'Arabic (Basic Reading).' Use the Interagency Language Roundtable (ILR) scale or simple descriptors — not self-assessed numerical ratings. For roles with international scope, client-facing responsibilities, or in multilingual markets, language skills can be the deciding factor between two otherwise equal candidates. Don't bury them — if the company operates in a market where your language skills are relevant, consider placing languages near the top of your skills section. Professional certifications belong in your skills section because they're searchable keywords. 'PMP,' 'AWS Solutions Architect,' 'CPA,' 'Six Sigma Green Belt,' 'Google Analytics Certified,' 'SHRM-CP' — these acronyms are exactly what recruiters type into ATS search fields. List the full name with the acronym: 'Project Management Professional (PMP)' captures both search variations. For certifications with expiration dates, only list current ones. An expired certification is worse than no certification because it suggests you let your professional development lapse. If your certification expires within six months, note the renewal status. Keep certifications relevant to your target role. Listing every certification you've ever earned creates noise. A software engineer listing a food handler's certificate looks scattered, not versatile.

How Many Skills Is Too Many and What ATS Systems Look For

There's a real ceiling to how many skills help your resume and a point where additional skills actively hurt. For a one-page resume, eight to twelve skills in a dedicated section is the maximum before the section starts competing with your experience for space. For a two-page resume, you can go up to fifteen or even eighteen if they're well-organized into categories. Beyond twenty skills, you're almost certainly including padding that weakens your stronger entries. ATS systems approach skills matching in several ways you should understand. Keyword matching is the most basic: the system checks whether specific terms from the job posting appear in your resume. This is why exact terminology matters. Semantic matching is used by more sophisticated platforms like Greenhouse, Lever, and Workday: these systems understand that 'JavaScript' and 'JS' are the same thing, or that 'people management' relates to 'team leadership.' However, you shouldn't rely on semantic matching — always include the exact terms from the posting. Frequency analysis counts how many times key terms appear across your resume. This doesn't mean you should stuff a keyword ten times. It means your target skill should appear in your skills section AND organically in your experience bullet points — two to three natural appearances signal genuine expertise. Section recognition is how ATS systems identify your skills section. Use standard headers: 'Skills,' 'Technical Skills,' 'Core Competencies,' or 'Areas of Expertise.' Avoid creative alternatives like 'My Superpowers' or 'Toolkit.' The system may fail to parse non-standard headers, meaning your entire skills section goes unread. After optimizing for ATS, remember that a human will read your resume next. A wall of thirty keywords might pass the automated screen but will overwhelm the recruiter. The goal is to be comprehensive enough for ATS matching while concise enough for human readability.

Frequently asked questions

Should I list Microsoft Office on my resume in 2026?

Only if you're applying for administrative, executive assistant, or data entry roles where specific Office proficiency is a job requirement. For most professional roles, basic Office skills are assumed. Instead, list advanced capabilities that demonstrate real value: 'Excel (Power Query, VBA Macros, Pivot Tables)' or 'PowerPoint (Executive Presentations, Data Visualization).' This shows depth rather than baseline competency that every applicant has.

How should I organize skills if I have too many to list?

Create two to three clear categories with four to six skills each. Common groupings include 'Technical Skills,' 'Tools & Platforms,' and 'Domain Expertise' or 'Industry Knowledge.' This categorization improves scannability and helps recruiters find relevant skills quickly. If you genuinely have too many relevant skills, use a tiered approach: a 'Core Skills' section near the top with your eight to ten strongest, and an 'Additional Skills' line at the bottom for supplementary competencies.

Do certifications count as skills on a resume?

Yes, certifications are some of the strongest entries you can put in a skills section because they're externally validated. Unlike self-reported skills, a PMP, CPA, or AWS certification proves you passed a rigorous assessment. Include the full name and acronym for ATS matching. You can either integrate them into your skills section or create a separate 'Certifications' section — both approaches work, but including them in skills ensures they're captured during keyword scans.