The interesting thing about skill bars is the disparity between having to show proficiency in relevant technology, while also gauging said proficiency. It comes with the natural problem of quantifying things: how do you know what you don't know, and what is the reference the recruiter is using?
I found that focusing on relative skill is helpful: if you're vastly more proficient in, say, React than in Vue, or Laravel than Symfony, make that visible. Word clouds help, though they're horrible for machine reading. Even something as simple as "+" vs "+++" can illustrate that. (Though I'd recommend avoiding 3 or 5 as your max, as that again implies a 100% value. Also, naturally, don't show a reference chart or legend).
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 interesting thing about skill bars is the disparity between having to show proficiency in relevant technology, while also gauging said proficiency. It comes with the natural problem of quantifying things: how do you know what you don't know, and what is the reference the recruiter is using?
I found that focusing on relative skill is helpful: if you're vastly more proficient in, say, React than in Vue, or Laravel than Symfony, make that visible. Word clouds help, though they're horrible for machine reading. Even something as simple as "+" vs "+++" can illustrate that. (Though I'd recommend avoiding 3 or 5 as your max, as that again implies a 100% value. Also, naturally, don't show a reference chart or legend).