Resume skills section: what to include and how to format it
Your skills section is the highest-weight section for ATS keyword scoring. It's the fastest place to improve your match rate.
Why the skills section matters so much
ATS systems are designed to find candidates with specific skills. When a recruiter sets up a job posting, they often filter candidates by required skills before any human review happens. Your skills section is the primary place ATS looks for these matches.
A well-built skills section does two things at once: it helps you pass ATS scoring, and it gives a human reviewer an instant snapshot of your technical profile in under 5 seconds.
What skills to put on a resume
There are three types of skills worth including:
Hard skills are specific, teachable, and verifiable. These are the most important for ATS. Examples: Python, React, SQL, Salesforce, Google Analytics, Agile, Figma, Excel, AWS, Docker.
Soft skills are interpersonal and organizational qualities. ATS weights these lower unless they appear in the job description. Examples: stakeholder management, cross-functional collaboration, project coordination. List only the soft skills explicitly mentioned in the job description — don't pad your list with generic ones.
Tools and platforms often sit between hard and soft — they're specific enough to score well in ATS. Examples: JIRA, HubSpot, Tableau, Slack, GitHub, Notion, Asana, Power BI.
Skills to list by field
Use this as a starting point, then adjust based on the specific job description.
Software engineering: JavaScript, TypeScript, Python, React, Node.js, Next.js, AWS, Docker, Kubernetes, PostgreSQL, MongoDB, GraphQL, REST APIs, CI/CD, Git, Agile, microservices, system design, TDD
Data and analytics: SQL, Python, R, Excel, Tableau, Power BI, BigQuery, dbt, Snowflake, A/B testing, statistical modeling, data visualization, Google Analytics, Looker, ETL pipelines, machine learning
Product management: Product roadmapping, Agile, Scrum, JIRA, user research, A/B testing, stakeholder management, OKRs, go-to-market strategy, product analytics, Figma, Notion, SQL
Marketing: SEO, SEM, Google Ads, Meta Ads, HubSpot, Salesforce, Marketo, email marketing, content strategy, marketing automation, A/B testing, conversion rate optimization, Google Analytics, Tableau
UX/Design: Figma, Sketch, Adobe XD, InVision, Zeplin, user research, usability testing, wireframing, prototyping, design systems, accessibility (WCAG), HTML/CSS
Sales: Salesforce, HubSpot, outbound prospecting, pipeline management, solution selling, contract negotiation, account management, SaaS sales, business development, Gong, Outreach
Finance: Excel, financial modeling, QuickBooks, SAP, NetSuite, budgeting, variance analysis, GAAP, accounts payable/receivable, financial reporting, cash flow forecasting, Power BI
Operations: Process improvement, Lean, Six Sigma, supply chain management, ERP, vendor management, SLA management, project management, Asana, JIRA, inventory management, logistics
HR and recruiting: HRIS, Workday, BambooHR, Greenhouse, ATS systems, talent acquisition, onboarding, performance management, compensation planning, employee relations, LinkedIn Recruiter
How to format the skills section
The most ATS-readable format is a simple list of skills separated by commas, pipes (|), or bullets. Avoid tables, columns, or any visual grouping that requires layout to understand.
Option 1 — Simple comma-separated list:
JavaScript, TypeScript, React, Node.js, AWS, Docker, PostgreSQL, Git, Agile, CI/CD
Option 2 — Grouped by category (works well for senior candidates with broad skills):
Languages: Python, JavaScript, SQL Frameworks: React, Django, Express Tools & Platforms: AWS, Docker, GitHub Actions, JIRA
Option 3 — Single line with pipes:
React | TypeScript | Node.js | AWS | PostgreSQL | Docker | CI/CD | Agile
All three are ATS-readable. Choose the format that fits your density of skills. Grouped categories work best when you have 20+ skills that benefit from organization.
Avoid these formats:
- Skill rating bars or star ratings (ATS can't read them)
- Tables or multi-column layouts
- Icon-based skill lists
- Skills listed only inside text boxes
Where to put the skills section
Place your skills section above your work experience if:
- You're in a technical field and skills are what gets you past ATS screening
- You're a recent graduate with limited experience to lead with
- You're switching to a new field and want to lead with transferable skills
Place your skills section below your work experience if:
- You're a senior candidate and your experience is more impressive than your skills list
- You're in a role where context and impact matter more than tool proficiency
For most candidates, especially in tech, placing skills above work experience is the right call. Recruiters and ATS systems check skills early.
How many skills should you list?
Minimum: 8–10 skills. Fewer looks light for most roles. Sweet spot: 12–20 skills. Enough to cover the job requirements without padding. Maximum: 25–30 skills. More than this starts to look like you're listing everything you've ever heard of.
Quality over quantity. A tight list of 15 genuinely relevant skills is more effective than a padded list of 35 where half are irrelevant to the role.
Matching your skills to the job description
The most impactful thing you can do with your skills section is reorder it for every application. Put the skills that appear in the job description first — especially in the requirements section.
If the job lists "React, TypeScript, and Node.js" as required skills, those should be the first three items in your skills section — not buried at position 11.
This takes 2 minutes per application and measurably improves both ATS scoring and recruiter first impression.
Skills section mistakes that hurt your ATS score
Listing skills you don't have: You will be tested on these in interviews. Don't list a tool as a skill if you've never used it.
Using vague descriptions instead of specific tools: "Database management" scores lower than "PostgreSQL" or "MySQL." Be specific.
Including only soft skills: A skills section that's all "teamwork, communication, leadership" with no hard skills provides minimal ATS value.
Not updating for each application: The order and content of your skills section should shift to match each job description's priorities.
Listing outdated technologies: If a tool is 15 years old and not mentioned in modern job postings, it's taking up space that could go to something relevant.
Skills buried in paragraphs: Skills mentioned only in paragraph-form bullet points are harder for ATS to parse than the same skills listed clearly in a dedicated section. Both is ideal: list in the skills section, demonstrate in the experience section.
Frequently asked questions about resume skills
Should I rate my skill levels (beginner/intermediate/expert)? Generally no — for two reasons. First, ATS systems can't process skill ratings; they just see the skill name. Second, self-assessed skill levels introduce risk: calling yourself "expert" in something sets an expectation in the interview. If you feel the need to add context, do it in your bullet points ("5+ years of Python experience") rather than a rating bar.
Should I include Microsoft Office or Google Workspace? Only if the job explicitly requires it. For most professional roles, these are assumed baseline skills and listing them wastes space. Exception: roles where advanced Excel or Sheets skills are genuinely required (finance, operations, data analysis) — in those cases, be specific: "Advanced Excel (pivot tables, VLOOKUP, financial modeling)."
What if a skill I have uses a different name than what's in the job description? Use the job description's term. If the job says "Kubernetes" and you have experience with it, use "Kubernetes" — not "container orchestration" or "K8s" alone. You can include both: "Kubernetes (K8s)" covers both variations.
How do I handle skills I learned years ago and rarely use now? If they appear in the job description, include them. If they don't, leave them out unless they're foundational to your profile. An old skill listed prominently implies current proficiency — only list it if you'd be comfortable demonstrating it in an interview.
