HR Specialist

10 Phrases That Kill Resumes

In Human Resources on August 19, 2009 at 5:49 pm

“10 Boilerplate Phrases That Kill Resumes”

ss_sktakcl_1

The 2009 job market is very different from job markets of the past. If you haven’t job-hunted in a while, the changes in the landscape can throw you for a loop.
One of the biggest changes is the shift in what constitutes a strong resume. Years ago, we could dig into the Resume Boilerplate grab-bag and pull out a phrase to fill out a sentence or bullet point on our resume. Everybody used the same boilerplate phrases, so we knew we couldn’t go wrong choosing one of them — or many — to throw into your resume.

Things have changed. Stodgy boilerplate phrases in your resume today mark you as uncreative and “vocabulary challenged.” You can make your resume more compelling and human-sounding by rooting out and replacing the boring corporate-speak phrases that litter it, and replacing them with human language — things that people like you or I would actually say.

Here are the worst 10 boilerplate phrases — the ones to seek out and destroy in your resume as soon as possible:

Results-oriented professional
Cross-functional teams
More than [x] years of progressively responsible experience
Superior (or excellent) communication skills
Strong work ethic
Met or exceeded expectations
Proven track record of success
Works well with all levels of staff
Team player
Bottom-line orientation

You don’t have to write resumes that sound like robots wrote them. A human-voiced resume is the new black — try it!

by: Liz Ryan
The Savvy Networker

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: