The skills section of your resume does two jobs at once: it helps ATS systems match your resume to the job description, and it gives a recruiter a quick summary of your technical and functional capabilities. Done well, it signals an immediate fit. Done poorly — too generic, too long, or misaligned with the posting — it either gets ignored or triggers a keyword mismatch that buries your application.

Hard skills vs. soft skills: what belongs in the list

Hard skills

Hard skills are specific, teachable, and verifiable. They are the primary content of a resume skills section. Examples include:

  • Tools and software: "Salesforce," "Figma," "Python," "Tableau," "Adobe Premiere"
  • Technical competencies: "SQL," "REST API design," "financial modeling," "supply chain planning"
  • Methodologies: "Agile," "Scrum," "Six Sigma," "GAAP accounting"
  • Certifications: "AWS Certified Solutions Architect," "PMP," "Google Analytics certified"
  • Languages: "Spanish (professional proficiency)," "Mandarin (conversational)"

Soft skills

Soft skills — communication, leadership, teamwork, problem-solving — are claimed by virtually every applicant and are nearly impossible to verify from a list. Listing them in a skills section adds almost no value and wastes space that could be used for something differentiating.

The right approach: demonstrate soft skills through your work experience bullets. "Led weekly cross-functional syncs with product, engineering, and design to ship three features ahead of schedule" shows communication and collaboration far more convincingly than a label does.

Exception: if a soft skill appears as a literal required qualification in the job description (e.g., "exceptional written communication required"), include it in the skills section to match the ATS keyword, but back it up with evidence in your bullet points.

How to choose which skills to include

Start with the job description

The most important source for your skills section is the specific job posting you are applying to. Extract every hard skill listed as required or preferred and check each one against your actual experience. Include those you genuinely have; do not pad with skills you cannot support in an interview.

Use the exact terminology from the posting where possible. If the job says "Microsoft Excel" rather than just "Excel," use the full name — ATS keyword matching can be literal.

Prioritize by relevance, not alphabet or recency

List your most relevant skills first, not in the order you learned them or alphabetically. The skills a recruiter sees before they stop scanning should be the ones most directly tied to the role's requirements.

Remove obvious or universal skills

Skills that every adult professional is assumed to have add no signal:

  • "Microsoft Word" or "PowerPoint" (for non-specialized roles)
  • "Internet research"
  • "Email communication"
  • "Fast learner," "self-motivated," "detail-oriented"

If a skill does not differentiate you from other applicants to this role, it does not belong in the list.

Automatically match your skills to every job description

Taloru identifies which skills from the job posting you are missing and updates your resume to close the gap — for $3.99 per application.

Match My Skills →

How to format the skills section

Option 1: Simple comma-separated list

The most ATS-friendly approach. List skills in one or two lines, separated by commas or pipe characters.

Example:
Python • SQL • Tableau • dbt • Airflow • Google BigQuery • Spark • A/B Testing • Looker

Option 2: Grouped by category

Useful for candidates with skills spanning multiple functional areas. Group related skills under brief subheadings.

Example:
Data & Analytics: Python, SQL, Tableau, dbt
Cloud & Infrastructure: AWS, GCP, Kubernetes, Terraform
Project Management: Agile, Jira, Confluence

Option 3: Inline with job bullets (no separate section)

For candidates with a very focused skill set, weaving skills naturally into the work experience bullets can be more effective than a separate section. This approach works especially well when every skill listed can be directly evidenced by a specific project or result.

Where to place the skills section

Placement depends on format and career stage:

  • After work experience — standard placement for reverse-chronological resumes; appropriate for most candidates
  • Before work experience — appropriate for technical roles where skills are the primary screen, or for career changers using a combination format
  • Above the fold — some candidates include a brief "Core Competencies" row directly under the summary before diving into experience; this satisfies both ATS keyword placement and recruiter scanning

Tailoring the skills section for each application

Your skills section should not be identical across every application. For each role, review the job description and make these adjustments:

  • Add any required skills from the posting that you have but did not include
  • Reorder so the skills most emphasized in the posting appear first
  • Use the exact phrasing the job uses — "project management" vs. "program management" can matter to an ATS
  • Remove skills the role has no use for, freeing space for more relevant ones

Frequently asked questions

How many skills should I list on my resume?

Eight to fifteen skills is the right range for most candidates. Fewer than eight can make the section feel thin; more than fifteen dilutes the signal and risks looking like a keyword dump. Prioritize skills explicitly listed in the job description and remove any that are too basic to add information.

Should I include soft skills in the skills section?

Avoid listing bare soft skills like "communication" or "leadership" — every candidate claims these. Instead, demonstrate soft skills through your bullet points with specific examples. If a soft skill is listed as a literal requirement in the job description, you can include it — but pair it with evidence in your work history bullets.

Where should the skills section go on a resume?

For most candidates using a reverse-chronological format, the skills section belongs after the work experience section. If you are a career changer or a technical candidate whose skills are the primary qualification, moving the skills section above work experience can be effective.

Should I list skill proficiency levels on my resume?

Proficiency labels like "beginner" or "expert" are generally not recommended. Self-assessed proficiency is subjective and rarely means the same thing to two readers. Signal proficiency through context instead — the complexity of projects you describe in your bullets will show skill level far more credibly than a label.