Written by squawkfox

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. These words are common. They are accepted. They litter the average resume with buzzword badness. Hiring managers can identify sucky words in seconds, leaving your resume work worthless.
So how do you write a wicked resume without the suck? How do you turn the wrong words into right? To help you land the job interview, here’s how to spin the 6 sucky resume words into skills that sizzle.
My lips pucker and make sour sucking noises when I read “Responsible For” on a resume. Of course you’re responsible for something. But how many? How long? Who? What? When? Rather than waste the hiring manager’s time reading a vague list of responsibilities, be specific and use quantitative figures to back up your cited skills and accomplishments.
Employers want the numerical facts. Write percentages, dollar amounts, and numbers to best explain your accomplishments. Be specific to get the point across quickly. Prove you have the goods to get hired.
BAD
- Responsible for writing user guides on deadline.
GOOD
- Wrote six user guides for 15,000 users two weeks before deadline.
BAD
- Responsible for production costs.
GOOD
- Reduced 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.
Are you experienced? Sexy. Rather than cite Jimi Hendrix on your resume, pleeease just say what your experience entails. Saying you’re experienced at something and giving the facts on that experience are two very different approaches.
BAD
- Experience programming in PHP.
GOOD
- Programmed an online shopping cart for a fortune 500 company in PHP.
Hiring managers want to know what experience, skills, and qualifications you offer. Do tell them without saying, “I am experienced.”
Yes, I realize this isn’t a single word but rather a phrase. This phrase must die. It’s on most resumes. Is it on yours?
BAD
- I have excellent written communication skills.
GOOD
- Wrote jargon-free online help documentation and reduced customer support calls by 50 percent.
If you’ve got writing skills, do say what you write and how you communicate. Are you writing email campaigns, marketing materials, or user documentation? Are you word smithing legal contracts, business plans, or proposing proposals? However you wrap your words, be sure to give the details.
Are we playing baseball here? Unless you want to be benched with the other unemployed “team players” then get some hard facts behind your job pitch.
BAD
- Team player working well in large and small groups.
GOOD
- Worked with clients, software developers, technical writers, and interface designers to deliver financial reporting software three months before deadline.
If you want to hit a home run then do explicitly say what teams you play on and qualify the teams’ achievements.
What does detail oriented mean? Give the specifics to the details with which you are oriented. Please, orient your reader to the details.
BAD
- Detail oriented public relations professional.
GOOD
- Wrote custom press releases targeting 25 news agencies across Europe.
If you have the details, do share them with the hiring manager. Give the facts, the numbers, the time lines, the dollar figure, the quantitative data that sells your skills and disorients the competition.
Hopefully you only list the successes on your resume. So if everything is a success, then why write the s-word? Stick to showing your success by giving concrete examples of what you’ve done to be successful! Let your skills, qualifications, and achievements speak for you.
BAD
- Successfully sold the product.
GOOD
- Increased sales of organic chocolate by 32 percent.
When it comes to your successes, please don’t be shy. Boast your best, sing your praises, and sell your skills.
There you have it. Six of the suckiest words (or phrases) commonly found on resumes today. By focusing on the facts, detailing the details, and qualifying your qualifications you may just land yourself the job interview.
There are soooo many sucky words found on resumes today. Got one to add? Do share the suck. :)
Print This Article
21 Responses to 6 Words That Make Your Resume Suck
Arjewtino
January 23rd, 2009 at 14:23
I screen resumes for my employer. I have seen so many mind-boggling editing and formatting mistakes it would make you cry.
The most frequent mistake I see by far is using “lead” as the past tense of “lead”.
It’s “led”, people.
Jonathan
January 23rd, 2009 at 20:03
Hey, this is actually pretty helpful! I haven’t ever written a professional resume myself, but these are all the sort of cliche things you expect to see on a resume. Thanks for the tips on improving.
Weekly Link Post 78 « Rhonda Tipton’s WebLog
January 25th, 2009 at 20:22
[...] Ran across and interesting article listing 6 Words That Make Your Resume Suck. [...]
Slavik
January 26th, 2009 at 02:25
Thank you so much it’s quite helpful.
Resume Revisions
January 27th, 2009 at 17:25
Very Very Helpful blog. I love all the descriptions
David Portugal
January 28th, 2009 at 02:09
Hey, thanks.
These are some very helpfull tips.
Jessi
January 29th, 2009 at 12:41
Great article!
Luis
February 23rd, 2009 at 21:24
Man! my resume sucks. I have every single one of them on it.
Kaiesha
March 6th, 2009 at 04:06
Thanks this information is great i thought i had it all figured out but looking at the 6 words i guess i didn’t i had most of these.
Carol
April 20th, 2009 at 18:02
Transformation Initiatve – DRIVING CHANGE! We all change everyday, we’re one day closer to death in this mind numbing world of computers! ‘I owe, I owe, it’s off to work I go — please rear end me so I’m late’ – [my latest bumper sticker] Does the EMPLOYER’S/COMPANY NAME count?!
Dana Harris
May 6th, 2009 at 13:02
Good tips. However, my background and the types of jobs that I do (and have had) DO NOT lend themselves to any quantifiable achievements….in other words, I never increased sales by a Gazillion dollars, never increased widget output by 250%, and so forth……a lot of my experience is in public sector work centered around construction and civil engineering with some time spent in the private sector doing HVAC related engineering and as well, civil engineering…I want a better job, yet cannot really talk up my latest position as a Local Building Inspector (there is a DEPRESSION going on and I needed a JOB)……what do I say on a resume?….process 50 permits per day?….(impossible by the way)….looked at 6 wood stud walls per inspection?…c’mon……what DO I DO to write a killer resume?
Tom Clark
June 3rd, 2009 at 18:50
Great article. I found you because I Googled “Words that Suck” — in search of another writer who despises certain words people use in their writing to sound important, like “utilize” and “additionally” — two words which you can add to your list.
6 Words That Make Your Resume Suck | Resume Candidate
July 30th, 2009 at 09:07
[...] article is part of a series called How to Write a Resume. To start this series from the beginning, read [...]
David
August 1st, 2009 at 20:36
Well that was fantastic! You’ve hit on so many useful points! In essence, stay away from the generic…resume gatekeepers want clarity – not obfuscation, they want facts – not generalities, they want impactive quantitative contributions – not cliched abstracts! Great information, that’ll surely help a lot of people!
Karla Porter
August 2nd, 2009 at 01:05
Nice job and great to see this was helpful to readers. I similarly coach candidates and much prefer resumes that do not contain those meaningless words.
Kat
December 10th, 2009 at 15:34
Oh My God. I am not even a hiring manager, but I have been weeding through resumes all week, and they suck. The recession seems to just mean more bad resumes, so make yours good, and you will still stand out. Some more tips – Don’t spend 2 pages telling me the same thing over and over. For example – I know you can program, you said you had done some very difficult, programming things. You have convinced me. But I have a list of things I want, and collaborating in teams, helping less-experienced employees, testing, and coming up with ideas of your own are also on that list. One technical point after another makes me think you don’t play nice with others.
Then again, one project managed after another sounds important, but I don’t know that you know what anyone is talking about. Don’t give me your whole biography – I don’t care where you were born. And please, pretty please, don’t use any acronyms, even if you define them. Even if it’s industry standard. Jargon is painful to read!
Charlie Hubbard
December 14th, 2009 at 12:36
All good points, but much of the advice was to say something like “blah blah blah increased by 20 percent.” or “blah blah blah decreased by 20%”. The only problem is that much of that data no one has access to. Working at the company doesn’t guarantee they’ll share the hard facts of sales data with you, or that they even know it themselves. Plus, it’s not like the hiring manager can fact check any of those things you’re claiming. But, if you’re just looking to stand out…”Now with 200% efficiency!”
john doe
December 14th, 2009 at 13:32
really good thoughts, thanks for sharing
Maxim
December 15th, 2009 at 20:34
Dear friend, you forgot one very important fact! In 99% cases your resume pass first screening by a recruiter, who is not going to read all the details and come to conclusions, so the phrases which you refer as “BAD” are exactly what most of the recruiters looking to find in your resume. Points which you brought are valid, but only in the job details part of a resume.
Veera
December 17th, 2009 at 07:39
Useful tips. It is always better to show what we did, rather than talk about it.
Adding to the tips: What does it take to make a ‘good’ developer resume?
SMiGL
December 21st, 2009 at 01:37
Helpful article. Thanks!