I completely disagree with this entire post. You can't exibit technical ability by hiding behind resume fluff. Any decent dev manager will see this a mile away and may actually hurt your chances more than help.
It can be useful for developers trying to get a foothold in industry. Entry-level coding jobs have bad HR screening where the HR blindly checks resumes for certain keywords and bins the non-conforming ones. The result is an arms race of adding more and more keywords to resumes.
Once you have your first job, the situation is different. In such a situation, more keywords attract spammy recruiters/bots.
I agree with your point of being careful before sending such a resume. Best advice will be to read the job description carefully. If it is buzzword heavy, keep a buzzword heavy resume ready to send.
While there may be different opinions regarding the usefulness of the author's tips and they will probably be more effective in certain cultures and contexts than others, I think he was rather honest in stating that the point of a CV is to get you an interview, not the job. Of course you still need to prove your skills in the interview process.
Where I live, most of the time somebody in HR is filtering the CVs and making first contact, and the dev manager only sees the CV once a first interview is scheduled. Thus, the goal of the CV is to peek the recruiter's interest, not the dev manager's.
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.
I completely disagree with this entire post. You can't exibit technical ability by hiding behind resume fluff. Any decent dev manager will see this a mile away and may actually hurt your chances more than help.
It can be useful for developers trying to get a foothold in industry. Entry-level coding jobs have bad HR screening where the HR blindly checks resumes for certain keywords and bins the non-conforming ones. The result is an arms race of adding more and more keywords to resumes.
Once you have your first job, the situation is different. In such a situation, more keywords attract spammy recruiters/bots.
I agree with your point of being careful before sending such a resume. Best advice will be to read the job description carefully. If it is buzzword heavy, keep a buzzword heavy resume ready to send.
While there may be different opinions regarding the usefulness of the author's tips and they will probably be more effective in certain cultures and contexts than others, I think he was rather honest in stating that the point of a CV is to get you an interview, not the job. Of course you still need to prove your skills in the interview process.
Where I live, most of the time somebody in HR is filtering the CVs and making first contact, and the dev manager only sees the CV once a first interview is scheduled. Thus, the goal of the CV is to peek the recruiter's interest, not the dev manager's.