|
|
|
|
|
by donretag
4838 days ago
|
|
As my career grew, I found myself putting less and less on the skills section of my resume. My next version might not have the section all together. The reason is that I want to be considered as a code architect and not simply a list of buzzwords. I am at the point in my career that I can be picky about who I work for and no one will pigeonhole me into buzzwords. Of course, if you are junior, you might need to list these skills in order to pass any matching software if you are applying to big companies. In general, only list skills that you wish the explore and develop further. Do not care for PHP anymore? Do not list it. Are you rusty in some language that you used as a freshman? I would not list it as well. Do not list "common" tech skills such as HTML. If a recruiter (internal/external) does not have a buzzword match with your resume, you probably do not want to work for that company anyways. For any skill section (language, OS, etc...) list at least 2-3 to show you have some depth. Applying to a job with Ruby as your only language is not ideal. EDIT: I should add that the skills section is definitely a good spot to add something that you have been learning on your own. It is a great conversation starter and shows your interest to grow outside of work. |
|