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'm not sure there really is a set of questions that apply globally. I
recommend you just use the resume as a pre-screening tool.
Otherwise, why not pre-screen based on your needs.
1) For example, if you are looking for a moderately experienced writer ask,
"have your been a writer for 5-8 years?" and, "what roles have you had in
your writing projects?" or, questions about the types of documentation the
candidates have authored.
2) If you want someone with particular tool use ask, "have you used
FrameWordHelp 2001?" or whatever.
In the end, methinks you have to review resumes. Perhaps you could train
your H.R. people to read the resumes with your thoughts in mind?
Best regards,
Sean
sean -at- quodata -dot- com
> -----Original Message-----
> From: Elizabeth Ross [SMTP:beth -at- vcubed -dot- com]
>
> I'm not asking how to interview a tech writer. I do that, along with
> several
> other folks in my company. What my HR department would like is a list of
> questions and answers that *they* can use to pre-screen applicants. The
> idea
> being that they "weed out" the "unqualified" ones before taking up my time
> to review resumes and interview candidates.
>
> I am having a hard time coming up with questions that won't throw out the
> baby with the bath water.
