Loading CVoraFlow
Skip to content
Resume Writing6 min readPublished · Updated

How to List Skills on a Resume Without Padding

A resume skills section should act as an index of the concrete tools, languages, regulations, and methods you can use on the job. When it is padded with personality traits like "teamwork" and "hard worker", the useful technical details get buried.

What belongs in the skills section (and what belongs in your bullets)

The skills section is built for nouns: software packages, programming languages, accounting standards, laboratory techniques, machinery, certifications, and spoken languages. A reviewer scanning a resume for an accountant looks for words like "NetSuite", "QuickBooks", "Accounts Payable", "VLOOKUP / XLOOKUP", and "Bank Reconciliation".

Character traits like "strong work ethic", "time management", "detail-oriented", "fast learner", and "team player" do not belong in a skills list. Anyone can type those words, so they carry zero weight as standalone tags. Instead, prove those qualities inside your work experience bullets by showing that you met a tight deadline, trained a colleague, or caught an error before a release.

Similarly, skip basic computer literacy items that are assumed for almost every office role today, such as "Internet browsing", "Email", "Windows OS", or "Typing", unless the job advertisement specifically asks for a measured typing speed.

How to group skills so a human can read them in five seconds

An unsorted block of 25 comma-separated items where "Python", "Customer Service", "Spanish", "Figma", and "GAAP" sit next to each other is tiring to read. Grouping your skills into two to four labeled lines lets a hiring manager jump straight to the category they care about.

Keep the total list between 8 and 18 concrete items. If you list 40 tools, reviewers assume you have only touched most of them once. List the tools you can comfortably answer interview questions about without looking up the basics.

Software & Data Candidate (Sample, fictional data)
Weak version

JavaScript, Hardworking, React, SQL, Problem Solving, Git, Team Player, HTML, Communication, Node.js, Fast Learner, Microsoft Word, CSS, Agile.

Stronger rewrite

Languages & Frameworks: TypeScript, JavaScript (ES2023), Python, React, Node.js, Express, HTML5, CSS3 | Databases & Tools: PostgreSQL, Prisma, Git, Docker, GitHub Actions, Playwright

Why this works: Removing the four personality fillers and grouping languages separately from databases and DevOps tools makes the candidate’s actual stack clear at a glance.
Accounts & Finance Candidate (Sample, fictional data)
Weak version

Accounting, Excel, Good with numbers, Punctual, Invoicing, Teamwork, ERP software, Bookkeeping, Detail-oriented.

Stronger rewrite

ERP & Software: NetSuite, QuickBooks Online, SAP FI/CO, Excel (Pivot Tables, XLOOKUP, Power Query) | Accounting Workflows: Month-End Close, AP/AR Reconciliation, Fixed Asset Schedules, Sales Tax Filing

Why this works: Replacing generic words like "ERP software" and "Excel" with exact systems and features shows practical readiness for an accounting desk.
Marketing & Content Candidate (Sample, fictional data)
Weak version

Social media, Creative thinking, Writing, Google, Canva, People skills, Email marketing, Time management.

Stronger rewrite

Analytics & Search: Google Analytics 4 (GA4), Google Search Console, Ahrefs, Looker Studio | Campaign & Design Tools: HubSpot CRM, Mailchimp, Meta Ads Manager, Figma, Canva

Why this works: It separates measurement tools from campaign execution tools and names the exact platforms used.

Why self-rated skill bars, stars, and percentages backfire

Many graphic design templates encourage you to put five-star ratings, progress bars, or percentages next to every skill, such as "Excel: 4 out of 5 dots" or "Project Management: 75%". In a real hiring review, these graphics create two problems.

First, the scale has no meaning: one applicant’s "90% in Python" means they completed a weekend tutorial, while another’s "70% in Python" means they have written production services for four years but know they do not know everything in the standard library. Second, a bar set to 60% visually draws attention to the 40% gap.

If you want to indicate proficiency level, use plain words where necessary, such as "Working knowledge of R" or "Spoken Languages: English (Native), French (CEFR B2 Professional Working)". Even better, connect the skill to a real project in your experience section.

Connecting your skills section to your work history

Think of your skills section and your work experience section as a pair. Whenever you add a key tool or method to your skills list to match a job posting, check whether it appears in at least one bullet point under your jobs or projects.

A skill that only appears in the bottom skills list looks like a keyword tag added at the last minute. A skill that appears in the skills list and inside a bullet point ("Built weekly cohort retention tables in PostgreSQL and Looker Studio") gives the interviewer a concrete topic to discuss with you.

When you have used a tool only in university coursework or a personal project rather than a paid job, label that context honestly inside your Projects or Education section. For instance, listing "Docker" in your skills section and showing "Containerized a FastAPI and PostgreSQL capstone service with Docker Compose" under Projects gives a truthful picture of your hands-on level.

Review your skills section every six months to retire outdated tools you no longer want to be hired to maintain. Keeping legacy tools on page one often leads recruiters to reach out for maintenance roles you have already outgrown, whereas a focused list of your current tools keeps interviews centered on the work you want next.

  • Audit rule 1: Every tool in the top half of your Skills section should appear by name in at least one Work Experience or Project bullet.
  • Audit rule 2: Spell tool names the same way the vendor and the job posting spell them (for example, "PostgreSQL" and "TypeScript" rather than informal abbreviations).
  • Audit rule 3: Separate spoken languages and formal licenses (such as ACCA, AWS Solutions Architect, or PMP) into their own labeled lines so they do not get lost inside software lists.

Practical checklist before you finish

Run through these items on your own draft before exporting or attaching your file:

  • Delete every personality adjective ("hardworking", "punctual", "team player", "problem solver") from your skills section.
  • Replace generic tool categories ("ERP software", "Spreadsheets", "Social media") with the exact software names you have used.
  • Group 8 to 18 skills into 2 to 4 clear categories (such as Software, Domain Workflows, Certifications, and Languages).
  • Remove progress bars, star ratings, and percentage scores.
  • Verify that your top 5 most important skills also appear inside your work experience or project bullet points.

Add comma-separated or categorized skills in the Resume Editor and see how they wrap on A4 paper.

Update Your Resume Skills Section
All 11 guides