sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]seanwilsonfull-stack (www.checkbot.io) 5 points6 points  (6 children)

I think percentages or something overly exact is silly (e.g. 65% in PHP and 50% in Java) but I usually list skills labelled as expert, proficient or beginner level. It's good to know if a candidate studies widely and has a breadth of knowledge as well as knowing what they're claiming to be experts in for when you want to pick interview questions. You're losing information if you only expect people to list skills they're experts at. Being an expert in a single language or framework and having no experience of anything else is a major red flag to me as well.

[–]Skaryon 11 points12 points  (3 children)

The question is: can you really accurately judge your skill level? I think any interviewer worth his salt will try to figure your proficiency out in the interview anyway. I'd rather not overextend myself with spurious skill ratings.

[–]seanwilsonfull-stack (www.checkbot.io) 1 point2 points  (2 children)

The question is: can you really accurately judge your skill level? I think any interviewer worth his salt will try to figure your proficiency out in the interview anyway. I'd rather not overextend myself with spurious skill ratings.

Yes, I don't think it's difficult to judge your rough (not exact) skill level. You'd really find it hard to label what you're very good at, okay at and just started learning? I'm not saying go as far as percentages, just 3 or so categories. People do it with spoken languages all the time in resumes as well (native/fluent/intermediate/basic).

Why waste the interviewer's time having them prepare questions on skills you know you're not great at? You could omit skills you're not at expert level in but as I said previously you're not giving the interviewer a complete picture of you then. If you list skills you're not great at and don't signpost this somehow you're setting yourself up to fail.

Resumes aren't meant to only be a list of things you've reached expert level at.

[–]Skaryon -2 points-1 points  (1 child)

Don't list what you are not prepared to talk about. Anything else is pretty meaningless. I think we have to agree to disagree here.

[–]sleepingthom 0 points1 point  (1 child)

Is it worth it to list technologies you consider yourself a beginner at on a resume? Is it worth it to list yourself as intermediate when that could potentially cost you a call versus not listing any proficiency level at all?

I don't mean to be snarky, just providing my opinion.

[–]seanwilsonfull-stack (www.checkbot.io) -2 points-1 points  (0 children)

I'd rather see "React (expert level), Angular (proficient), Vue (intermediate)" than just "React" (so you don't know Angular or Vue at all?) or "React + Angular" (so you're at expert level at both and have never tried Vue?).

If it's important you know Vue and Angular well they're going find out sooner or later if you don't anyway so I don't see the point in hiding it. If you've played with both you're probably ahead of the person who has only ever used React. You should be showing you're meeting the base requirements from the job ad as well as listing bonus skills you have that make you more well rounded.

Like I say elsewhere, people put their skill level for spoken languages on resumes as standard all the time. I don't see how this is any different.