I see a lot of programming beginners doing webdev-projects building skill bars. When I was starting and done programming for about one or two years, in my perception skill bars were common sense to show your skill level. So in a result, something similar to this (Fig.1) had found its way onto my first real resume.
Nowadays, I think skill bars are an illogical style of presentation and completely meaningless.
A few years ago, my opinion was completely different. I thought, skill bars are a cute-looking point system and a creative way to visualize your skills.
But even if it looks cute, it is completely meaningless.
When creating a skill bar you are also creating some kind of point scale system, e.g. 10 points, 5 points or 100 percent.
But how do you compare your skills to that? To rate your skills equally on your scale, you would need to create some sort of criteria and equal tests for each one which measures the skill on your 10 point - or whatever - scale.
When not showing your criteria, the employer will not know what the criteria for your rating were. Do you even know?
Also, the point system makes no sense.
Example: English 4/5
Answer one question: What is the difference between 3/5 and 4/5?
I don't know, probably there is no difference because the points mean nothing.
Seeing such skill bars gives the impression that every skill has the same difficulty.
Example: Java 4/5 Python 3/5 HTML 5/5
Basically saying it's a unique point scale comparing completely different languages or skills on that scale, no matter of difference in quality and difficulty.
It makes no sense!
Shows design skills
Some people say skill bars show web-development or design skills because
graphics like skill bars stand out of the application or resume and maybe bias the employer positively.
But even people on Reddit dislike this trend!
Waste of space
Skill bars use a lot of space which could be used much better, e.g. to provide more information about your skill set. When considering graphics can't be read by machines (ATS systems), skill bars seem to be quite a large waste of space.
Also, graphics on a resume distract from the professional appearance of your resume and make it look more like a flyer - what you probably not want.
Subjective and unreliable
But the biggest issue with skill bars is that they are subjective and unreliable because people are bad in rating themselves.
According to Emilie Thewon, a Marketing and Business Development Director,"self-evaluating their own performance, competences and skills is flawed and inaccurate" for the most people.
Studies show that intelligent people often think deeper about the problem and rather rate themselves lower for tasks they are good at, where less intelligent persons or people who have less expertise in a certain topic rather rate themselves higher than an objective rating would be.
To accomplish this, many people cheat in their resume to have a favorable effect on the employer. As you can see in Fig.2 misrepresenting yourself in the application seems to be almost normal nowadays.
In my opinion the only thing what matters in the skill section is what you have worked with before.
So a better practice is just listing your skills and show your exact skill level suitable to the type of skill, e.g. "basic", "proficiency level" or "experienced". Also, you can add facts like certifications, degree or licenses.
If your resume is online you can show projects, link them and maybe add what you used to complete that projects.
People using skill bars are "generally quite intelligent but have very poor social skills and lack self-awareness" ~ Brian Grubba, District Manager
Please feel free to write your opinion in the comment section!
- GitHub: tim0-12432
Latest comments (31)
I agree, but for a different reason. Resumé should be about pointing out your strengths. Using these rating bars is merely pointing out your weaknesses. Personally, I don’t include any skill/language/framework on my resumé unless I feel confident to undertake a big project with it.
Or just add a visually subtle explanation line of the rating scale? .... “100% equals proficient", "5/5 represents numerous projects completion using this tool“, etc
By doing this the problem of applying the same scale on different types of skill still exists. In my opinion it makes more sense just to list the skills and explain it in the same way you done it.
Just my opinion
But I think by doing it like you explained you don't get completely rid of the problems occurring by using a skill bar presentation.
I agree, however, I was just advised 2 days ago by a big wig at Adobe, who has interviewed 700+ people, who is mentoring me and took a red pen to my resume to keep the self-rating stars on my skills section. I even asked him directly if it was ridiculous. He said keep it.
Okay. This is very interesting. Do you know why he wants you to keep it? I'm very interested in his points.
His advice may be particular to my case, I'm wanting to get back into tech after a rough go at it 2 years ago. He wants me to keep this because "everybody's doing it" and best for me to fit in at this time. He said after a few successful years in tech, I could dare to be more bold with my style choices and breaking from current norms.
I think we should show skills in our Resume, so that recruiters any view and shortlist.
ATS has also tough time reading those. Most of the ATS ignores it
I see this alot when reviewing resumes and I've never thought to myself that this is a useful addition. I'd prefer to see a list of skills and an honest overview of how much involvement the candidate has had with them. The rest can be chatted about in the interview.
The main downside of skill bars is readability.
How should I know what a full skill bar means? Everybody have their own interpretations.
But to some of this articles point, especially "Equal difficulty" and "subjective and unreliable", the solution didn't help much.
From my experience with many HRs and interviews, skill bar is used to attract HR who needs to filter lots of candidates from a pile of resumes. In this case, skill bar does have its strength, it's eye catching.
TBH, engineers don't like skill bars, because it tells too few informations (so as word like "proficient"). That's when experience and side project and some github link comes in. These are the real content engineers care about.
In short: Skill bars + level of skill in words for HR / ATS, real code or project content for engineers.
Couldn't agree more. I've noticed that in a lot of resume templates, you'll find the Skills section in this format and it really doesn't make any sense.
I think you could expand more on the solutions though, like providing examples from resumes and personal developer websites as well.
I just wanted to point at other possible ways to show your skills in the last paragraph, but I agree that a example picture would have fit good in there.
While I completely agree that the figures are somewhat meaningless, I think it does help visualise which areas a candidates feels are their relative strengths and weaknesses are. For example:
Their last job title may have been as a “Full-stack web developer” but they’re clearly more front-end focused. Whether it’s visually through info graphics or through words they’ll tell you the same thing.
Skill bars are a HUGE trend in resumes. Personally I like the way it looks (pretty colors, some going up or down or left or right) BUT it is a big no-no. Did the American Bar Assoc. give those bars? Did the Alcohol Licensing Board tell you that Bars are this long? I don't get it.
Rating your own skill this precisely is an invitation to the dunning-kruger effect. You will rarely know how much you're missing until you're getting very close to really mastering something.
And what does the end of a progress bar even represent?
Proficiency? Then you shouldn't have anything on your resume that's not a full bar anyway. There's no point in advertising that you've heard of a technology but can't even reliably work with it on your own.
Or is it mastery? Then how can anybody trust your evaluation of your own skills? Once again, this metric is very susceptible to the dunning-kruger effect. The further you are from mastering a skill, the less reliably you can tell what's left for you to learn.
Would it be fair to use keywords like; 'beginner', 'intermediate', 'expert' and so on instead? At least that wouldn't make it seem like you know everything, but tells the reader something about what level you consider yourself to be in.
I personally would prefer such keywords as description.
@darkwiiplayer I completely agree with you on this one. Some of my friends barely know HTML/CSS and say that they know Frontend Dev. They even rate themselves as 4/5 often on these bars.
While many seniors I see often rate themselves as a 2/5 or at max a 3/5.
I completely agree with you.
I have been ask how do you rate your skill from 1 to 10 in the interview, guest what I said
Step 1: Start a discussion with your future employer about their interview questions
Every time I see a candidate with a "5/5" that misses a question make me think he lied on his resume.
Same as you, I splitted my skills into 3 categories: familiar, experiemented and proficient.
I think some people and also me in the past think they have to rate their skills somehow in a resume. Skill bars seem nearly perfect for this. When creating them the compulsion to make at least one bar 100 percent is strong, whether or not it makes sense or even can be true.
I don't really get the point of skill bars and rating your own skills using a score.
It's a vague measurement and often leads to misrepresentation.
That's very insightful, thanks for sharing