10 of the Worst Executive Job Search Email Mistakes

by Meg Guiseppi on May 23, 2016

An email message may carry the first impression you make on someone.


In job search, that email message will probably be sent to someone who can help (or hinder) you in reaching your career goals.

That first impression can advance or derail your opportunity to position the value you offer the employers you’re targeting.

Poor grammar, typos, and a host of other email issues can disqualify you right out of the gate.

Emailing is an integral part of job search communications. Don’t blow your chances.

Always think of, and write, email messages in the same way you would a formal, snail-mailed job search (or business) letter or note.

Within the following 3 posts, I’ve actually highlighted 11 job search email mistakes many job seekers make:

Executive Job Search Email Mistakes: Careless Email Address and Subject Line

The first things the recipient will notice in their email inbox are your email address and the subject line of your email message.

Either or both of these can land your email message in spam, or cause the recipient to immediately delete it.

6 Executive Job Search Email Content Blunders

Always put yourself in the shoes of the email recipient. Write in a formal, professional manner, reinforcing your personal brand and good-fit qualities.

3 Executive Job Search Email Misconceptions

Even if you feel you’ve gotten all your ducks in a row, and you’re ready to hit “send” . . . wait.

Take one last look at your email message . . . tweak it before sending it . . . and consider what happens to it, once you’ve sent it out there into the email stratosphere.

More About Emailing and Executive Job Search

Personal Branding and the Email Signature Dilemma

When Job Search Email Goes Missing

10 Steps to Executive Job Search Success

Personal SEO in Executive Job Search: What’s in a Name?

The Online Safety and Privacy Dilemma in Executive Job Search


{ 0 comments… add one now }

Leave a Comment


{ 1 trackback }

Previous post:

Next post: