You’ve seen them everywhere. Those sleek progress bars on resume templates showing “Python: 85%” or “Leadership: 4 out of 5 stars.” They look modern. They fill space nicely. And they’re one of the worst things you can put on a resume.
Skill rating systems create more problems than they solve. They’re invisible to ATS, they’re arbitrary by definition, and they invite hiring managers to fixate on the wrong things. Here’s why they don’t work, what the one exception is, and what you should do instead.
The ATS Problem: Skill Bars Are Invisible
This is the most immediate issue. Applicant tracking systems parse text. They cannot interpret graphical elements like progress bars, star ratings, pie charts, or any other visual representation of skill levels.
When an ATS scans a resume with graphical skill bars, one of two things happens. Either the ATS picks up the skill name (because it’s rendered as text) and ignores the bar entirely, or the ATS misses both the skill name and the rating because the graphic disrupts the text flow around it.
Either way, your carefully calibrated skill percentages add zero value to your ATS score. In the worst case, they cause the surrounding text to parse incorrectly, which means skills the ATS should have captured get lost.
A 2023 Jobvista study on resume parsing accuracy found that resumes with graphical skill indicators had 23% more parsing errors in the skills section compared to resumes using plain text lists. That’s a significant disadvantage for a design choice that’s purely cosmetic.
The Arbitrary Number Problem
What does “Python: 85%” mean? 85% of what? Compared to whom?
There’s no universal scale for skill proficiency on resumes. When you write “Excel: 4/5 stars,” you’re grading yourself against a standard that exists only in your head. The hiring manager has no way to interpret that rating because they don’t know your baseline.
Consider this scenario. Two candidates apply for the same data analyst role. Candidate A rates their SQL skills at 70%. Candidate B rates theirs at 90%. But Candidate A has 8 years of SQL experience and is being modest. Candidate B took a 6-week bootcamp and is being generous. The numbers create a false comparison that rewards overconfidence.
Hiring managers know this. They’ve seen too many resumes where someone rates themselves 5/5 in a skill, then can’t answer basic questions about it in the interview. Self-assessed ratings have no reliability, and experienced recruiters treat them as noise.
The Self-Sabotage Trap
Here’s what’s counterintuitive about skill ratings. They hurt you whether you rate yourself high or low.
Rate yourself too high and you set an expectation you’ll be tested against. If you claim 95% proficiency in JavaScript and then struggle with a basic coding challenge, you’ve damaged your credibility beyond just that one skill. The interviewer now questions everything else on your resume.
Rate yourself too low and you’ve told the recruiter to pass. If you show “Excel: 60%,” the recruiter sees someone who isn’t confident in their own Excel abilities. Why would they invite you in? You’ve essentially pre-rejected yourself.
Rate yourself in the middle and it reads as mediocre. A 3/5 star rating on any skill is the equivalent of saying “I’m not great at this.” Even if you meant “solid working knowledge,” that’s not how a visual indicator reads at a glance.
There’s no winning move. The only way to avoid the trap is to not play.
What Hiring Managers Actually Think About Skill Bars
Recruiters and hiring managers have been pretty vocal about this. In a 2022 ResumeGo experiment, resumes with skill bars received no statistically significant increase in callback rates compared to resumes with plain-text skill lists. The visual element added nothing measurable.
Anecdotally, the feedback is even more negative. Hiring managers on professional forums consistently describe skill bars as “filler,” “unhelpful,” and “a sign that the candidate is more focused on design than substance.”
One technical hiring manager put it bluntly: “When I see skill bars on a developer’s resume, I assume they don’t have enough real experience to fill the space. The bars are padding.”
That perception isn’t universal, but it’s common enough that the risk outweighs any aesthetic benefit.
The One Exception: Language Proficiency
There is one area where standardized skill levels make sense on a resume: language proficiency. Unlike technical skills, language ability has widely recognized standardized frameworks.
The CEFR scale (Common European Framework of Reference for Languages) provides six levels that are internationally understood:
- A1 / A2: Basic user
- B1 / B2: Independent user
- C1 / C2: Proficient user
The ILR scale (Interagency Language Roundtable), used primarily in US government and military contexts, provides a 0-5 rating system.
Common descriptors that work without a formal framework:
- Native / Bilingual
- Professional working proficiency
- Conversational
- Basic / Elementary
These labels work because they reference external standards, not your personal assessment. When you write “Spanish: B2 (CEFR)” or “Mandarin: Professional working proficiency,” the reader knows exactly what that means. There’s an objective test behind the rating.
How to format language skills on your resume:
- Spanish: Professional working proficiency (CEFR B2)
- Mandarin: Conversational
- French: Native
No bars, no stars, no percentages. Just the language, the proficiency label, and optionally the framework reference.
What to Do Instead: Group by Proficiency Level
If you want to communicate different skill levels without using visual gimmicks, organize your skills into labeled groups. This approach gives the reader useful information while keeping everything in parsable text.
Example for a software developer:
Primary Technologies (daily use, 3+ years): Java, Python, PostgreSQL, AWS (EC2, S3, Lambda), Docker, Git
Working Knowledge (project experience, used regularly): Kubernetes, Terraform, Redis, GraphQL
Exposure (coursework or side projects): Rust, Go, Apache Kafka
This format tells the reader far more than “Java: 90%, Rust: 30%” ever could. It gives context (what “proficiency” means in terms of actual experience), it avoids arbitrary numbers, and it parses perfectly through any ATS.
Example for a marketing professional:
Core Platforms (certified or daily use): Google Analytics 4, Google Ads, Meta Ads Manager, HubSpot, Salesforce Marketing Cloud
Proficient (regular campaign use): SEMrush, Mailchimp, Canva, WordPress
Familiar (project-level experience): Tableau and Adobe Premiere Pro
The grouping approach has another advantage. It naturally highlights your strongest skills by putting them first, without requiring you to assign a number to each one.
Show Context Instead of Numbers
The most effective way to communicate your skill level is through context in your work experience section. Instead of rating a skill, show how you used it.
Weak (with rating): “Python: 4/5 stars”
Strong (with context): “Built automated data pipeline in Python (pandas, SQLAlchemy) that processed 2M+ records daily, reducing manual reporting time by 80%”
The second version communicates several things the rating never could. It tells the reader you’ve used Python for data engineering, that you know specific libraries, that you’ve worked at scale and that your work delivered measurable results. No star rating conveys any of that.
For every key skill on your resume, aim to have at least one bullet point in your experience section that demonstrates that skill in action. This is where the real proof lives, not in a self-assessed number.
If you want more ideas on how to make your skill descriptions land harder, our guide on power words to strengthen your resume covers the action verbs and phrasing that make bullet points stand out.
Technical Skills vs. Soft Skills: Different Rules
The advice above applies mainly to technical and hard skills. But what about soft skills? Should you rate those?
Absolutely not. Rating soft skills is even worse than rating hard skills, because soft skills are inherently subjective and impossible to self-assess accurately.
“Leadership: 4/5” means nothing. What’s a 5 in leadership? Who decided the scale? How would you even test it?
Soft skills should be demonstrated through your accomplishments, not listed as standalone items with ratings. “Led cross-functional team of 12 through product launch, delivering 2 weeks ahead of schedule” says more about your leadership than any star rating.
For a deeper look at how hard skills and soft skills function differently on resumes, and where each belongs, see our guide on hard skills vs. soft skills on your resume.
When Employers Ask for Skill Ratings
Some job applications and internal HR systems ask you to rate your own skills on a scale. This is different from putting ratings on your resume. When an employer’s system asks, fill it out. They’re using that data for their own filtering and the scale is defined by them.
But their system asking for self-ratings doesn’t validate putting those same ratings on your resume. The employer’s form has a defined context (their scale, their job requirements, their evaluation framework). Your resume doesn’t.
Follow the instructions on application forms. Don’t import that format into your resume.
The Portfolio Exception for Creative Roles
Designers, illustrators and other visual creatives sometimes use skill indicators as a design element in portfolio resumes. If you’re applying for a role where the resume itself is a portfolio piece (a design job where the hiring manager expects to see your layout skills), graphical skill indicators can be a deliberate creative choice.
Even then, there’s a catch. If your portfolio resume goes through an ATS first (which it will at larger companies), you need a separate ATS-friendly version. The creative version is for human review only. The ATS version should be plain text with no visual skill indicators.
This means maintaining two documents. Your portfolio version for direct submissions and networking. Your ATS version for online applications. It’s extra work, but it’s the only way to serve both audiences.
How to Restructure an Existing Skills Section
If your current resume has skill bars or ratings, here’s how to restructure it:
Step 1: List all your skills from the current resume.
Step 2: Sort them into 2-3 proficiency groups (Expert/Proficient/Familiar, or Daily Use/Regular Use/Exposure).
Step 3: For your top skills, make sure each one appears in at least one work experience bullet point with context and results.
Step 4: Remove all graphical elements. Replace bars and stars with the grouped text list.
Step 5: Test the updated resume through an ATS parser to confirm all skills are being captured.
The result will be a skills section that communicates more information, parses correctly and doesn’t give the hiring manager a reason to question your self-awareness.
Skills Sections on One-Page Resumes
Candidates with limited experience sometimes use skill bars because they need to fill a one-page resume. The bars take up visual space without requiring much actual content. This is understandable, but there are better solutions.
Instead of inflating a thin skills section with graphics, add substance:
- Include relevant coursework or academic projects
- Add volunteer experience or extracurricular leadership roles
- Expand your work experience bullets with more specific details
- Add a certifications section with any training you’ve completed
- Include a “Projects” section with personal or open-source work
These additions give you real content that an ATS can parse and a hiring manager can evaluate. Graphical filler just draws attention to the fact that you’re trying to fill space.
What Actually Matters in a Skills Section
A strong skills section does three things. First, it includes the keywords that ATS systems scan for. Second, it tells the reader what tools and technologies you work with. Third, it’s organized in a way that lets someone skim it in 5 seconds and understand your technical profile.
Here’s what a well-structured skills section looks like:
Technical Skills
Languages: Python, Java, SQL, JavaScript, TypeScript Frameworks: React, Django, Spring Boot Cloud: AWS (EC2, S3, Lambda, RDS), GCP (BigQuery, Cloud Functions) Tools: Git, Docker, Jenkins, Jira, Confluence Databases: PostgreSQL, MongoDB, Redis
Every item is a concrete keyword that an ATS can match against job descriptions. There are no vague descriptors, no graphical elements and no self-assessed numbers. The organization by category makes it instantly scannable.
If you’re building a resume and want a template that handles the skills section formatting correctly out of the box, 1Template designs its templates with text-based skill sections that ATS systems parse without issues.
Drop the skill bars. Your experience section is where you prove what you can do. Your skills section is just the keyword index that gets you there.
