Resume Writing

How to List Skills on a Resume (by Skill Type) in 2026

Hard skills, soft skills, languages, certifications, tools, each lands differently with recruiters and ATS. The exact grouping, order, and formatting that gets parsed cleanly and read first.

By Surya L.Updated Sep 15, 2026.13 min
On this page(12)

Why this matters

Most ATS systems rank resumes by how many JD skill keywords appear in yours. Put the right skills in the right place and you clear the filter. Put soft skills in a bulleted list at the top and you score zero on the parser and look lazy to a human. This guide separates the five skill categories and tells you exactly how to present each.

A recruiter spends roughly 7 seconds on the first pass. The Skills section is one of the three things they scan (job titles, recent company, skills). Miss a key skill keyword and you lose the callback even if the Experience section would have carried you. Skills section is ATS insurance: it is where you pay the keyword tax cleanly without stuffing your bullets.

Hard skills by role

Hard skills are measurable, learnable capabilities tied to a tool, language, or method. These are what the ATS matches against the JD. List 10 to 15 max; pick the ones most relevant to the target role.

Software Engineering

Python · Java · TypeScript · Go · React / Next.js · Node.js · PostgreSQL · Redis · AWS (EC2, S3, Lambda) · Docker · Kubernetes · GraphQL · REST API design · CI/CD · System design

Data Science / ML

Python · SQL · Pandas · NumPy · scikit-learn · TensorFlow · PyTorch · XGBoost · MLflow · Airflow · dbt · Snowflake · BigQuery · Tableau · A/B testing

Product Management

Roadmapping · User research · SQL · Amplitude · Mixpanel · Figma · JIRA · A/B testing · OKRs · Market sizing · Pricing · Go-to-market · PRD writing · Stakeholder management

Marketing / Growth

Google Ads · Meta Ads · SEO (technical + content) · HubSpot · Salesforce · Braze · Segment · GA4 · Looker · Copywriting · Email automation · Attribution modelling · CRO · Partnership marketing

Design / UX

Figma · Sketch · Adobe XD · User research · Wireframing · Prototyping · Design systems · Accessibility (WCAG) · Motion (Principle / Rive) · Framer · Information architecture · Usability testing

Finance / Accounting

Financial modelling · Excel advanced · SAP · Oracle · Tally · QuickBooks · IFRS / GAAP · Variance analysis · FP&A · Forecasting · Tax (GST / TDS) · Power BI

Sales / BD

Salesforce · HubSpot CRM · Outreach · LinkedIn Sales Navigator · Cold outbound · Consultative selling · Contract negotiation · Territory planning · Enterprise / SMB pipeline · Account mapping

Operations / Supply Chain

SAP · Oracle NetSuite · S&OP · Demand planning · Inventory management · Six Sigma · Lean · Power BI · SQL · Logistics (TMS / WMS) · Procurement

Soft skills (handle with care)

Soft skills belong in the resume, but not in a bulleted skills list. Every candidate claims "strong communication". Prove it in the Experience bullets: "Presented Q3 roadmap to 40+ stakeholders across Eng, Product, Sales" beats a Skills entry that says Communication.

Communication

Written communication, Presenting, Stakeholder updates, Cross-functional collaboration, Documentation, Active listening

Leadership

People management, Hiring and coaching, Performance reviews, Giving feedback, Conflict resolution, Mentoring

Thinking

Problem solving, Prioritisation, Decision making under ambiguity, First-principles thinking, Systems thinking, Critical thinking

Execution

Project management, Time management, Ownership, Attention to detail, Bias for action, Operating under pressure

ATS impact: Most modern ATS platforms explicitly discount soft-skill keywords because they appear in every resume. Greenhouse and Lever weight hard skills ~4x higher. Use soft skills as proof through stories, not as filler in a skills block.

Languages (use a real scale)

Include only if the role touches multilingual contexts (customer-facing, international expansion, translation, localization). Always pair each language with a proficiency level using a recognised scale.

LanguageLevel examples
EnglishNative / Fluent / Professional / Conversational
HindiNative / Fluent
SpanishB2 (CEFR) / Professional
MandarinHSK 5 / Conversational
FrenchA2 / Basic

Scale options: CEFR (A1-C2) is the global standard. "Native / Fluent / Professional / Conversational / Basic" is the US convention. Pick one scale and use it consistently.

10 certifications that carry weight in 2026

List only active, name-recognised certifications relevant to the target role. Include the issuing body and the year obtained. Expired certs should drop off.

  • AWS Certified Solutions Architect - Associate
  • Google Data Analytics Certificate
  • PMP (Project Management Professional)
  • Certified Scrum Master (CSM)
  • CFA Level II
  • Six Sigma Green Belt
  • Salesforce Administrator
  • Microsoft Certified: Azure Fundamentals
  • IBM Data Science Professional Certificate
  • Meta Blueprint Certified

Tools & software

These are often confused with hard skills. Keep them in a dedicated Tools line if the list is long; otherwise merge into hard skills.

Productivity

Notion, Linear, JIRA, Confluence, Slack, Google Workspace, Microsoft 365

Collaboration

Figma, Miro, Zoom, Loom, Slab

Development

Git, GitHub, VS Code, Postman, Datadog, Sentry

Analytics

Amplitude, Mixpanel, GA4, Looker, Tableau, Power BI, Metabase

How to format your skills section

Do

  • Group by category (Languages, Frameworks, Tools, Cloud)
  • Use comma-separated text, not bullets (parser-friendly)
  • Match the exact JD spelling ("Node.js" not "NodeJS")
  • Cap at 12 to 15 hard skills
  • List most relevant first within each group

Don't

  • Use skill-level bars / star ratings (ATS ignores, recruiters distrust)
  • List 40 skills to look broad
  • Include skills you cannot defend in an interview
  • Claim "Expert" as the default level
  • Invent abbreviations the JD did not use

A worked skills section

Here is what the rules above look like on the page: grouped, comma-separated, most relevant first, and capped. One for an experienced engineer, one for a fresher.

Software Engineer (experienced)

Languages: Python, TypeScript, Go

Frameworks: React, Next.js, Node.js

Data: PostgreSQL, Redis, GraphQL

Cloud & DevOps: AWS (EC2, S3, Lambda), Docker, Kubernetes, CI/CD

CSE fresher

Languages: Java, Python, JavaScript

Web: React, Node.js, HTML/CSS

Databases: MySQL, MongoDB

Tools: Git, GitHub, VS Code, Postman

Four tidy groups, every item defensible in an interview, and each spelled the way job postings spell it. That parses cleanly and reads fast.

Where on the resume does Skills go?

For freshers and career changers: near the top, right after the Summary, so recruiters see the match immediately. For experienced candidates (4+ years): below Experience, because your job titles and employers are stronger signals and Skills is confirmation, not the lead.

One exception: applying to highly technical roles (ML, Cloud, Security) at any level, keep Skills near the top. Hiring managers scan the stack before they scan titles.

Common Skills section mistakes

  • Listing every tool you have ever touched

    If you cannot answer a technical question about it, cut it. ATS does not reward breadth over defensibility.

  • Using star ratings or skill bars

    Looks designerly but parses as nothing. Use words (Expert, Proficient, Familiar) only if each is justified by years or output.

  • Buzzword soup ("Synergy, Paradigm")

    Strip corporate-speak. Every skill should be a tool, language, method, or certificate.

  • Duplicating soft skills across Skills + Summary + Experience

    Pick one location per skill. Soft skills belong in Experience bullets; hard skills in the Skills section.

  • Skipping the Skills section entirely for senior roles

    Keep it even as a Director. ATS still keyword-matches. A minimal 8-skill line below Experience is enough.

External references

Independent references for the claims here. External links open in a new tab.

Frequently asked questions

How many skills should I list?+
10 to 15 hard skills, grouped into 3 to 5 categories. Fewer reads thin, more reads padded.
Should I list skill proficiency levels?+
Only if you use a defensible scale (years of experience or CEFR for languages). Avoid star ratings or self-assessed percentages.
Should I repeat skills mentioned in Experience bullets?+
Yes, for the most important hard skills. ATS weights keywords by frequency (with diminishing returns). Mentioning "Python" in Skills + 2 bullets is fine; mentioning it 12 times is stuffing.
Are soft skills worth listing?+
Rarely in a dedicated list. Always prove them in Experience bullets instead. Exceptions: roles where "people management" is itself the skill (Engineering Manager, HR).
Should I list Microsoft Office / Google Docs?+
No, unless the JD asks for advanced Excel (financial modelling, pivot tables). Basic office software is assumed.
Do I need both a Skills section and a Tools section?+
Not usually. Merge unless your tool list is 15+ items, in which case split for scannability.
Does the order of skills within a category matter?+
Yes. List the most relevant to the JD first; recruiters often stop reading at the 5th skill in a row.
What skills should a fresher list with no work experience?+
The languages and tools you actually used in projects and coursework, grouped the same way as an experienced resume. Keep it to what you can defend in an interview, put your project stack first, and mirror the exact terms in the job posting. A tight, honest list beats a long one padded with things you have only heard of.
Do the skills change for Indian IT-services applications?+
Lean toward the stack those companies train and hire on (Java or Python, SQL, OOP, a little cloud) plus whatever the specific drive mentions, and show consistency across your projects. For product-company roles, weight the exact target stack more heavily and let your quantified projects back the skills up.

Build a skills section that parses cleanly

ResumeBuildz auto-groups your skills by category and uses JD-matching to flag missing keywords. Free.

Spotted something off?

Suggest an edit