The point of the scale is to see how they rate their own fluency against their actual experience. There is no baseline or litmus to base it against. It doesn't matter what scale the other guy is using at all.
It's a way to frame the conversation. And not a means for doing flat comparisons between candidates.
I understand that is the intent of the person who is putting it on the resume. That makes complete sense, and if people decide they want it for the aesthetic or the novelty, regardless, who am I to say no?
Instead, I am asking how a hiring manager, a talent scout, et cetera, will be able to tell all of the relevant scores apart, relative to one another, if you have 3 people with score bars, and 0 of those people provide reference points for their scoring systems, and 0 of those people provide justification for the scores they have chosen, and you don't have enough time in the day to review all GitHub profiles to choose who to move forward with, and rather, review GitHub in a secondary screening process.
A few, simple words would remove ambiguity in the eyes of the scout, and help that process along.
That's why I wrote this blog post. Of course I see why someone put this on their resume. I did it too. It looks nice and of course I would never say: Never do this! There are use cases and employers who prefer graphics and visual representations of the skills on resumes. I'm just very interested in points why you should and why you shouldn't. In my opinion it would be the best solution just to provide a GitHub link to show what you are able to do and work with, of course 😂
That's not always possible I know.
I'm not an employer and it would be very interesting what the opinions of real team managers are.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The point of the scale is to see how they rate their own fluency against their actual experience. There is no baseline or litmus to base it against. It doesn't matter what scale the other guy is using at all.
It's a way to frame the conversation. And not a means for doing flat comparisons between candidates.
I understand that is the intent of the person who is putting it on the resume. That makes complete sense, and if people decide they want it for the aesthetic or the novelty, regardless, who am I to say no?
Instead, I am asking how a hiring manager, a talent scout, et cetera, will be able to tell all of the relevant scores apart, relative to one another, if you have 3 people with score bars, and 0 of those people provide reference points for their scoring systems, and 0 of those people provide justification for the scores they have chosen, and you don't have enough time in the day to review all GitHub profiles to choose who to move forward with, and rather, review GitHub in a secondary screening process.
A few, simple words would remove ambiguity in the eyes of the scout, and help that process along.
That's why I wrote this blog post. Of course I see why someone put this on their resume. I did it too. It looks nice and of course I would never say: Never do this! There are use cases and employers who prefer graphics and visual representations of the skills on resumes. I'm just very interested in points why you should and why you shouldn't. In my opinion it would be the best solution just to provide a GitHub link to show what you are able to do and work with, of course 😂
That's not always possible I know.
I'm not an employer and it would be very interesting what the opinions of real team managers are.