TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>I've always--and I do mean always--thought a
>statement of objective was pretty lame.
When I was job-hunting about ten years ago, the first thing I learned was
to bury "Network Database Adminstrator" since I hated doing that and didn't
want to repeat it -- but everyone kept calling me for that sort of position
until I moved it to the second page of my resume.
The next thing I learned was to include an objective. At that time, I knew
onel language almost backwards, and wanted to develop systems using that
language. Until I put XYZ DEVELOPER as my objective, I was inundated with
calls for other types of positions. (And, yes, I found what I wanted.)
After that experience, my personal opinion is that you should list an
objective ONLY if you're looking for something very specific, and have
experience which could otherwise waste your time with calls for other types
of positions. Obviously, if you're seeking any possible interview, or are
open to different types of positions, limiting your objective would be a