6 Words That Make Your Resume Suck
This article is part of a series called How to Write a Resume. To start this series from the beginning, read the introduction. I’ve used a few bad words in my life. S$it, you probably have too. But when the wrong words appear on your resume, it sucks. These sucky words are not of the four-letter variety. So how do you write a wicked resume without the suck? 1. My lips pucker and make sour sucking noises when I read “Responsible For” on a resume. Employers want the numerical facts. BADResponsible for writing user guides on deadline. GOODWrote six user guides for 15,000 users two weeks before deadline. BADResponsible for production costs. GOODReduced production costs by 15 percent over three months. The resume that avoids vague “responsibilities” and sticks to facts detailing figures, growth, reduced costs, number of people managed, budget size, sales, and revenue earned gets the job interview. 2. BADExperience programming in PHP. 3. Yes, I realize this isn’t a single word but rather a phrase.