Re: Employment Agencies - Technical Communication Specific

["Hutchings, Christa" <cwhutchings -at- HOMEWIRELESS -dot- COM>]

I don't even clutter up my resume with an "Objective" statement. I put a
"summary of skills" at the top of my resume instead. As a prospective
hiring authority myself, I'm more interested in a person's
qualifications (like John Posada said, "what can you do for me"), not in
what the candidate wants. I can find out what they want during the
interview.

Of course, if you have no real world experience as a TW yet, that option
might be tricky. I would still leave off the "I want..." stuff, though,
and just go straight to listing your educational background, special
(Tech Comm related) projects you handled in school, internship info,
etc.

Chris Welch-Hutchings
Sr. Technical Writer
Home Wireless Networks, Inc.
Norcross GA (USA)
cwhutchings -at- homewireless -dot- com


-----Original Message-----
From: Tracy Boyington [mailto:tracy_boyington -at- OKVOTECH -dot- ORG]
Sent: Wednesday, May 27, 1998 9:43 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: Employment Agencies - Technical Communication Specific


John Posada wrote:

> Besides, as a prospective reader of your resume, I don't care what YOU
> want. I want to know what are you going to do for me, and giving a job
to a
> rookie isn't going to do much for me right now.

So... since the objective is typically an "I want" statement, what
should you use instead? Or should you eliminate the objective
altogether?

Tracy
--
======================================================
Tracy Boyington   mailto:tracy_boyington -at- okvotech -dot- org
Oklahoma Dept. of Vocational & Technical Education
Stillwater, OK, USA
http://www.okvotech.org/cimc/home.htm
======================================================

~~~
Find TECHWR-L-related books at
http://www.raycomm.com/techwhirl/books.htm