5 Common Phrases That Will Ruin Your Resume

erpadmin

I plan on modifying my resume based on this. Figured this would help my fellow IT brethren as well.

5 Common Phrases that will Ruin Your Resume - Knowledge Genes®

ipconfig.all

lol interesting

N2IT

erpadmin wrote: »

I plan on modifying my resume based on this. Figured this would help my fellow IT brethren as well.

5 Common Phrases that will Ruin Your Resume - Knowledge Genes®

That is very interesting I use 3 out of the 5. Thanks!

LinuxRacr

I have some changes to make for sure.

Mojo_666

I don't use any of them, I may have been missing out over the years where they were "in"

erpadmin

Mojo_666 wrote: »

I don't use any of them, I may have been missing out over the years where they were "in"

It makes sense to heed some of that at least. In fact my resume is definitely in need of a makeover, and I plan on modifying it.

For example, I have "Experience in Cisco." If any of you Cisco guys were to interview me on my "Cisco Experience", you would be in for a very good laugh. I haven't touched a router since 1999...oh I know what it does thanks to my Network+ cert and limited experience, but can I upgrade an IOS? Ehhh....with a google search, I'll say maybe. But my point is, just because I touched something, it doesn't make me CCIE. (Heck, even a CCNA).

My resume still has stuff like Ghost images and whatnot. I can refocus my resume (and should at this point) to concentrate on my system/server administration skills and PeopleSoft administration. That's a project in and of itself though. But I gotta do it.

BradleyHU

I only use "responsible for"...but i never put too much faith into these articles anyways, cuz just like most other articles, they're all about somone's opinion. and also, it depends on how the whole sentence is worded. The way i use "responsible for" is totally different from the example that he has...

erpadmin

BradleyHU wrote: »

I only use "responsible for"...but i never put too much faith into these articles anyways, cuz just like most other articles, they're all about somone's opinion. and also, it depends on how the whole sentence is worded. The way i use "responsible for" is totally different from the example that he has...

How's that been working out for you, personally?

dynamik

The underlying advice is to quantify your accomplishments, which is what I do and encourage others to do. Numbers make your accomplishments pop.

Devilsbane

I agree and disagree with these. I agree that it is important to spell out what you have done, but most of these examples are ridiculous. Even if the call volume dropped by 50% after you started, how can you attribute this to your awesome communication skills? I just think that a lot of the numbers would be difficult to obtain, and even then still wouldn't be very credible (due to other undisclosed factors. Maybe the day that you wrote these documents a new policy went into effect that also impacted call volumes?) in my book. Not to mention, they can't be verified.

undomiel

It's pretty much as dynamik said. "Quantify it" is what should be taken from the article. It isn't so much about the specific words so the article title and focus is a bit misleading.

earweed

Don't use any of those but as was mentioned earlier I probably misses out while they were in.

dynamik

My resume is actually just a list of certs and a single sentence:

I am a detail-oriented team-player with excellent written communication skills that is responsible for, and experienced with, information technology.

It is the pinnacle of perfection

BradleyHU

erpadmin wrote: »

How's that been working out for you, personally?

i have a job currently....and when i was in between jobs, i get interviews. so, it has not been a hindrance....

erpadmin

dynamik wrote: »

My resume is actually just a list of certs and a single sentence:



It is the pinnacle of perfection

LMAO! You rock!

it_consultant

I've read articles where hiring managers complain about too much specific information - something IT guys do frequently. Following this persons' advice our resumes would be 6 pages long.

For example, I might say "Designed and Implemented Hosted Exchange 2010 Product" which might sound vague but in all honesty, to go through all the high level tasks required to pull that off successfully would take ages.

I guess in some ways the wording of your resume should be designed to weed out potential employers you don't want to deal with. Just my opinion though.

ssampier

I have trouble with specifics as well. I have a hard time quantifying things like, "Setup a DHCP/DNS server","migrated firewall." How can you quantify that?

I do use numbers for budgets I managed, but I don't think it's impressing anyone (less than $20k); I just want to show I can do more than be the office geek.

dynamik wrote: »

My resume is actually just a list of certs and a single sentence:



It is the pinnacle of perfection

I SO want a resume that will fit in a fortune cookie.

Devilsbane

ssampier wrote: »

I have trouble with specifics as well. I have a hard time quantifying things like, "Setup a DHCP/DNS server","migrated firewall." How can you quantify that?

"Setup a DHCP/DNS server ensuring that all employees would be able to access the internet and waste $100,000 in payroll each year."

There, it has been quantified.

ssampier

Devilsbane wrote: »

"Setup a DHCP/DNS server ensuring that all employees would be able to access the internet and waste $100,000 in payroll each year."

There, it has been quantified.

LOL!

I think you just won the thread.

earweed

Devilsbane wrote: »

"Setup a DHCP/DNS server ensuring that all employees would be able to access the internet and waste $100,000 in payroll each year."

There, it has been quantified.

That's definitely the truth...LMAO

blargoe

Yeah, you can't quantify and/or put a dollar value on EVERYTHING. My current resume in progress has fpr each company, major projects listed first with the value they added... $ savings, efficiencies gained, risk avoidance, supporting a strategic business initiative, or whatever... and toward the end I put the more pedestrian "job responsibilities" like "manage DNS Server". The catch 22 is, earlier in one's career, it's harder to find things that can be quantified like that.