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.
> Certainly do not tell these applicants that you cannot hire them "at this
> time." That implies you might hire them later.
This reminds me of a sketch, either on Saturday Night Live or some
similar show, about a group of friends who believed everything they
"Guess what? They didn't hire me, but they said they'd _keep my
resume in their file!_"
"Wow, that's great! You've got one foot in the door!"
> However, your post does bring a question to my mind and to the list:
> To err is human...must technical communicator's be flawless? What qualities
> do managers look at most critically?
> Many a high-stess situation has brought many a typo into my life.
The errors pointed out in the original post were NOT typos. They were
clearly written by people who didn't write well enough to be
professional writers. Now, whether typos are acceptable is another
subject... one I hope we can let lie like the sleeping dog it is. But if
you can't write, you're not qualified to be a technical writer.
Back to the original question... If I were Barb, I would send a form
letter to the non-interviewables that says "your qualifications do not
meet our needs for this position," because they obviously don't.
Tracy Boyington tracy_boyington -at- okvotech -dot- org
Oklahoma Department of Vocational & Technical Education
Stillwater, Oklahoma, USA http://www.okvotech.org/cimc/home.htm