Resumes and Objective Statements

Last week I saw a post on lifehacker on a new site called  First of all, if you’re questioning your resume in any way, definitely plug in your resume and you can get an automated grade.  You can also opt-in to get assistance on your rewrite if you’d like.

I submitted mine last week, and I scored a B.  Not bad, not great.  There are 3 key areas where they grade you: Brevity, Impact, and Depth.  The number one area they suggested I work is brevity.  I have been told by recruiters my resume is too long, but at the same time, they always comment on the clarity (or depth) of my resume.  That was mirrored in my score, almost a perfect depth, but a very poor brevity.  I’m going to work on that a bit, and try again.  I’d like to see if I can cover the same material using fewer words.

But that’s not the advice that caught my attention most.  Their algorithms suggested I remove my Objective section.  I was shocked!  I’d always used this to cinch the deal.  To get that interview.  So I followed up with Jen Kramer, she was listed in the “report card” the system sent me on my submission.  I explained how I used it, and asked for some clarification.

A rose by anyother name would still smell like plastic.
A rose by any other name would still smell like plastic.

She said, “the way you describe what you do with an objective statement is not how most people use it – and that may be why it works for you.”  She referred me to a post on their site that explained why they suggest people not include an objective statement.  To summarize: resumes with objective statements scored lower when they were reviewed by hiring managers, resume writers, and recruiters.

So, with that in mind Jen suggested “Keep the content, change the title. Just don’t call it an Objective Statement.”

So,  based on the way I use my objective statement, I’m now changing that to Executive Summary.  While I still use this section to explain in 3-5 sentences who I am, and how all I want to do is exactly what the job post needs me to do, the name will now be different.  I’m going to come back to this several more times in the coming weeks.

I’m trying to pull in all the information I can to make my presentation the best it can be for all of you.   I’ve submitted this presentation to  SQL Saturday Boston, and SQL Saturday Columbia, SC.

If you have any comments or questions, please send them in…I’m here to help!

By Shannon Lowder

Shannon Lowder is the Database Engineer you've been looking for! Look no further for expertise in: Business Analysis to gather the business requirements for the database; Database Architecting to design the logical design of the database; Database Development to actually build the objects needed by the business logic; finally, Database Administration to keep the database running in top form, and making sure there is a disaster recovery plan.

1 comment

Leave a comment

Your email address will not be published. Required fields are marked *