2 ms·

I'm usually skeptical of somebody who puts something on their resume that they can't back up. If you've claimed to know something, you'd better have studied up

I'm usually skeptical of somebody who puts something on their resume that they can't back up. If you've claimed to know something, you'd better have studied up enough to have a conversation about it. One way I like candidates to get around this issue is to separate skills into categories like (for example) "very familiar with", "comfortable with", and "experience with". It's refreshing to see honest evaluations of skill levels, rather than people who say they know C/C++ but aren't capable of coding up a basic class in C++.

mywittyname 8y ago
So am I. It comes down to how much knowledge you expect someone to have with a skill before listing it on their resume. In this guy's case, he came right out and said that his experience was limited to an online course on the subject. I do think this is another topic that make interviewing difficult. For example, I know Javascript pretty well, I've worked with it for years. However, I haven't done modern front-end development with it in a long time, thus I don't know Vue/Angular/React or even Node. But I have created browser plugins in pure JS. Some people would argue that I shouldn't list Javascript as a skill because I don't know the popular core libraries it's used with, and other people would have no problem with listing it. The problem is interviewees have no idea what kind of person they are going to run into. I do appreciate when people rank their skills, but that also takes up pretty valuable real-estate on a resume. I personally leave them off of my "list" of skills, but call them out on projects I've worked on the past. For example, I don't list C as a skill, but I do mention working on embedded devices with C for previous jobs.