Andy Chase

Objectives are a tricky thing, and it's been my experience that the objective you put on a resume that gets you hired rarely matches the job you wind up doing. That's not necessarily a bad thing, but since my skills and interests are constantly evolving I've elected to link to two or three different wiki pages related to the things I'm interested in doing for a living; you won't find typical resume Objectives like "Seeking full time work implementing cross platform solutions for blah blah blah...". I like to think that the more general description pages will give prospective employers a better insight into why I'm interested in these things in the first place.

That was the contents of the "Resume Objectives" page on my incomplete, experimental Wiki resume from 2002. It's the number 7 result on MSN's search for the words "Resume Objectives", and I when I began looking at my traffic again I was surprised to learn that it's also currently the number one requested page on *.greyledge.net.

I guess perhaps it's good advice - the "Objective" section on the resume that resulted in my current job read

Seeking a position developing web sites, applications, and services using open source technologies and protocols.

Succinct without being overly specific, no buzzwords, and now that I read it again, I realize that it describes exactly what I got hired to do.