re: How to write a SOLID dev resume to be 2018 STAR VIEW POST


One thing I've found which helps is to have your skills, and level of skill in each, in an easily digestable format, like a small table. The people looking through your CV have a very limited time to read through possibly dozens, so anything that helps the reader get to the point quickly is ideal. Also, be careful about giving yourself 10/10 in anything, it's a pretty good sign that you're suffering from the Dunning-Kruger effect!


That's actually a controversial one.

I don't like to rate the skills I'm using, because what it means 5/10? or 2/10 or even 10/10?

I'm listing skills relevant to the position. And I divide it into strong, knowledgeable, and (eventually if relevant) learning. And keep them to 1-3 bullets at the top of my resume (summary).

And I believe it's better to write how you actually used it and for what purpose by mixing them in the accomplishments.

But this is really a matter of preference here and both ways are good.

Putting your skills in a table makes it hard to scan by ATS system (and there's more and more of them in play before your resume actually gets to the recruiter).


Yes, I agree. By level of skill, I didn't specifically mean a value score. I do the same as you, qualifying skill against basic, fair, good, & great. An ATS system won't have trouble scanning words, and that's basically all they are, glorified keyword searchers. It's why I tend to avoid going through agencies now; if they knew the technology they wouldn't be in recruitment, and a computer can never match a person for deriving context!

Yeah, that's true. I don't want to go into ATS and "best on how to apply" discussion here. It's too opinionated and probably everyone is right :p

code of conduct - report abuse