The right skills section:

  • 10-15 specific skills, organized by category.
  • Tools, technologies, and concrete capabilities — not soft-skill clichés.
  • Match the job posting — list what they ask for, in their language.

Below is how to build it.

What to include

Specific, named tools and technologies:

  • Programming languages (Python, TypeScript, Go, Rust, SQL)
  • Frameworks and libraries (React, Next.js, Django, PyTorch, Pandas)
  • Tools (Figma, Postman, Datadog, Tableau, Salesforce)
  • Methodologies (Scrum, Agile, OKRs, Six Sigma)
  • Domain expertise ("B2B SaaS pricing," "ML infrastructure at scale," "enterprise sales cycles")
  • Languages (Spanish, Mandarin, French — if relevant to role)
  • Certifications (AWS Solutions Architect, PMP, CFA, NP-BC)

Each item should be specific enough that a hiring manager can verify it.

What to cut

Soft-skill labels without proof:

  • ❌ "Strong communicator"
  • ❌ "Team player"
  • ❌ "Detail-oriented"
  • ❌ "Self-starter"
  • ❌ "Hard-working"
  • ❌ "Passionate"

These tell the recruiter nothing. Show them in your bullets:

  • ✅ "Communication: led 12 cross-functional review meetings/quarter, coordinating product, eng, and design."
  • ✅ "Detail: caught and fixed three critical bugs in the audit log before launch."

Match the job posting

ATS systems screen on keywords. If the posting says "experience with Snowflake" and your resume says "data warehouse experience" — different terms. The ATS doesn't infer the match.

Read the posting; mirror its language for skills you actually have. Don't add skills you don't have just to keyword-match.

How to organize

By category:

Skills Languages: Python, TypeScript, Go, SQL Frameworks: Next.js, React, FastAPI, Django Infra: AWS, Docker, Kubernetes, Terraform Data: Snowflake, Postgres, Spark Methodologies: Agile, OKRs

Reads in 5 seconds. Recruiters can scan for what they need.

Skill levels — usually skip them

Don't write:

  • "Python ★★★★☆"
  • "Excel — Expert"
  • "SQL — Advanced"

Self-assessed skill levels are noise. Either you can use the tool on day one (list it) or you can't (don't).

Special case: certifications

If the role calls out a certification (PMP, CFA, AWS, Azure, NP-BC, etc.), list it prominently — either in skills or in a separate Certifications section.

If it's not in the role, mentioning it still helps if it's well-recognized in the industry.

Special case: languages

Spoken languages help if the role is multilingual or international. Format:

  • "Languages: English (native), Spanish (fluent), Mandarin (conversational)"

Don't list languages you can't actually hold a meeting in.

Common mistakes

  • Listing every tool you've ever touched. Misleading and dilutes your real skills.
  • Soft-skill word salad. "Driven, passionate, dedicated" — meaningless.
  • Skill levels. Self-assessed, useless.
  • Outdated tech. Listing skills from 10 years ago that aren't relevant anymore.
  • Skills that should be in bullets. "Project management" by itself says less than "Led 6-month $400K migration project, on time, under budget."

The bigger pattern

The skills section is a bridge between the job posting and your bullets. Your bullets prove the skills are real; the skills section makes them ATS-findable.

Sorce auto-tailors your resume — including the skills section — per application, so the right skills surface for each role. For more: how long should a resume be, how to list education on resume, another word for experience.