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.
On Tue, 30 Nov 1999 11:52:55 Lydia Wong wrote:
>Trish Castin writes, in part:
>The resumes that come across my desk are not representing candidates
> . . . they all seem to look like they were created using a cookie cutter.
><end of snip>
That's such a pity, because creating a resume is, in many ways, an example of your work. THIS IS WHAT WE DO. If we cannot present ourselves effectively, there's a very slim chance of us doing better with a product we know a lot less than ourselves. I try to use all the skills at my disposal in preparing my resume. Even made them in Winhelp and HTML formats for the heck of it. I am sure that it would have made a very strong point if somebody wanted a tech writer with those specific skills.
The problem with resumes and interviews is that very often the person who evaluates the candidate is not prepared for that job (candidate evaluation). Often, employers are not very sure about what they want exactly, and sometimes are even insistent on the wrong qualifications. Unfortunately, they are in the happy position of being able to make the final decision. It is up to the candidate to prove merit. The employment process also carries undercurrents of personality matching. Given the same skills set, the candidate who is a temperamental match for the employer usually makes it.
The Candidate needs to identify areas that they can control and areas that are not within their sphere of influence.
I sometimes attend interviews for jobs I don't need. This puts me very much at ease throughout the entire process, and even if I don't get the job, I make a friend, or at least learn how to spruce up my presentation. If it looks like I'm getting the job, I try to drive a good bargain. If I get what you REALLY want from that employer, I move. If I have a commitment already that I cannot leave for some good reason, I drop out of the reckoning well in advance to avoid inconvenience to the employer.
I know this has wandered way off the topic, but since it was in my head, I thought I'd share it.
The bottom line is that tech writers are in the business of presenting information. If you cannot do that with the one product you should know best, you are in the wrong business.
A day without sunlight is like... everyday at the office.