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.
Elizabeth Ross <beth -at- vcubed -dot- com> wrote:
> My HR department has asked me to come up with a list of 7-10
> can be used for pre-screening technical writer candidates. I've
> issue for a few days and realize that this is not as simple as it
> to be.
> What sort of questions would distinguish an experienced technical
> from a beginner? I don't think questions about tools (FrameMaker et
> really get to the heart of the matter. Can this even be done? I
> such a process would helpful or harmful.
This depends on your HR-folk, somewhat. How technical are they? Will
they be able to distinguish a good correct answer from a lengthy
BS-fest, wherein the applicant uses a lot of buzzwords, but doesn't
actually say anything? :o)
> I'd like to hear your thoughts and opinions on the matter. Thanks in
Well. In the "Careful What You Wish For" department ....
Ideally, your HR-folk should be able to check the resume for "X"
number of years of experience, "Y" type of
degree/certificate/whatever, combined with "Z" months of work (paid
or voluntary). Asking specific questions about the tools your company
uses in producing its docs/help/etc. is a good idea also -- just to
judge how much training you will have to do.
If the applicant fits in those areas properly, then s/he should be
sent on to you and (some of) your staff for a "team interview," where
each of you ask the applicant questions, look at his/her portfolio,
get a "feel" for the applicant, etc.
Make sure you have the person explain selected (by you or your
teammates) bits and pieces in the portfolio (I've heard disquieting
tales of recruiters finding projects the recruiter had worked on being
passed off as the work of an applicant -- whom they know was not on
their doc team).
Probably not what you were looking for unfortunately, but hopefully
still helpful. Basically, cutting HR out of the loop beyond the
basics (check resume for education, experience, or a good combination
of the two) plus the "team interview" method should work.
> Elizabeth Ross
> Senior Technical Writer, V3 Semiconductor Corp.
> beth -at- vcubed -dot- com http://www.vcubed.com
> Cogito cogito ergo cogito sum.
".... so the teacher says, 'Can anybody tell me anything about
thermodynamics?', and I said, in my best sleazy late-night sex line
voice, 'Hot stuff!' ... and that's how I got thrown out of the
engineering program at the UW."