Most people spend 30 minutes rewriting their experience bullets and 2 minutes on their skills section. That's backwards.
ATS systems match the skills section directly against required and preferred qualifications. It's often the most heavily weighted part of the parse. Ignoring it is leaving points on the table.
Hard skills vs. soft skills: what actually belongs here
Hard skills belong in your skills section. Soft skills don't.
Hard skills: specific, teachable, verifiable. "Python," "SQL," "Figma," "Google Analytics," "Agile," "Workday." These are what the ATS is scanning for.
Soft skills: "communication," "leadership," "problem-solving," "team player." Every resume claims them. ATS systems don't weight them. Hiring managers don't trust them without evidence. Keep them out of the skills section — put evidence of them in your experience bullets instead. "Led a team of 8 engineers" proves leadership without claiming it.
How many skills to list
10–20 is the right range. Under 10 looks thin. Over 25 becomes noise — and if you're listing 30 skills, most of them are probably weak signal that dilutes the relevant ones.
Prioritize:
- Skills that appear explicitly in the job description you're applying to
- Skills you can speak to confidently in an interview
- Tools and technologies specific to your role, not generic
The exact-match problem that kills ATS scores
This is the single most common skills section mistake.
ATS parsers match strings, not concepts. If the job description says "React.js" and your skills section says "React" — that's a miss to the parser. Zero keyword overlap for that term.
Same issue applies to:
- "Node.js" vs "NodeJS" vs "Node" — different strings
- "Google Analytics" vs "GA4" vs "Analytics" — not interchangeable to a parser
- "Microsoft Excel" vs "Excel" vs "MS Excel" — varies by system
- "Agile" vs "Agile Methodology" vs "Scrum/Agile" — treat as separate
Before submitting any application, copy the skill terms from the job description and check that your resume uses the same capitalization and spelling. Use Applyr's keyword checker to see exactly which terms the JD uses and which ones your resume is missing.
How to format the skills section
Format matters as much as content. Parsers skip content they can't read.
Use a simple flat list or comma-separated lines. Label the section "Skills" or "Technical Skills" — not "Core Competencies," "My Expertise," or "What I Bring." Non-standard labels confuse parsers.
Avoid:
- Tables for the skills section — most ATS parsers skip table content entirely
- Two-column skill layouts formatted as a table
- Icons or rating bars next to skills ("Python ★★★★☆" — ATS ignores it, recruiter is skeptical)
- Skills buried inside a text box or floating element
The cleanest format — organize by category, one line each:
Programming Languages: Python, Go, TypeScript, SQL Frameworks: React.js, FastAPI, Next.js Tools: Docker, Kubernetes, GitHub Actions, Datadog Cloud: AWS (EC2, S3, Lambda), GCP
Skills by role — what to include
Software Engineers
Programming languages, frameworks, tools, cloud platforms, methodologies. Include specific versions where the JD uses them (React 18, Python 3.11). Don't list every language you've touched — list the ones you'd be comfortable being tested on.
Product Managers
Analytics tools (Mixpanel, Amplitude, Looker, Tableau), project management tools (Jira, Linear, Notion, Asana), methodologies (Agile, OKRs, JTBD), any technical background (SQL, Python basics). If you've worked in a specific domain (fintech, healthtech, B2B SaaS), that counts as a skill category too.
Data Scientists / Analysts
Languages (Python, R, SQL), ML frameworks (PyTorch, TensorFlow, scikit-learn), data engineering tools (dbt, Spark, Airflow, BigQuery), visualization (Tableau, Looker, Matplotlib). Separate "Languages" from "ML Frameworks" from "Tools" — keeps it organized and scannable.
Designers
Design tools (Figma, Sketch, Adobe XD, Photoshop, Illustrator), research methods (user interviews, usability testing, A/B testing), prototyping (Framer, InVision), platform-specific skills (iOS/Android design guidelines, web accessibility standards).
Sales / BD
CRM tools (Salesforce, HubSpot, Outreach, Salesloft), methodologies (MEDDIC, SPIN, Challenger), deal size and motion (enterprise, mid-market, PLG), verticals you've sold into.
Marketing
Channels (SEO, paid social, email, content, events), tools (HubSpot, Klaviyo, Google Analytics, Semrush, Marketo), platforms (Meta Ads, Google Ads, LinkedIn Ads), attribution and analytics frameworks.
The fastest way to improve your ATS score
Update your skills section to match the JD's exact terminology, then check your match score before applying.
Most resumes are missing 8–15 relevant keywords per job description. Half of those gaps are in the skills section — wrong spelling, missing tools, or outdated terminology. Closing them moves the match score by 15–25 percentage points with changes that take under 10 minutes.
Find the exact keywords your resume is missing →
After updating your skills, run a full ATS check to verify the score moved before you apply. Applyr's ATS checker takes 8 seconds and shows your match percentage against any job description.