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.
Subject:RE: Testing writers at interviews From:Bettina Davis <bdavis -at- acucorp -dot- com> To:"'TECHWR-L'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 28 Jan 2000 09:30:00 -0800
I agree with Chuck. Every interview is a "test" for both sides. FYI, the
company that I work for tests EVERY writing candidate. Generally this
happens only if the candidate qualifies for a second interview.
The purpose of our test is not only to confirm that a candidate can organize
technical information clearly and compose a decent sentence, but to see how
they deal with pressure and deadlines. We learn quite a bit about candidates
by their attitude towards testing and how much (or how little) they
accomplish in the time allowed.
Personally, I don't see how employers can afford NOT to test employees in
some way. Lots of people have great samples and interview brilliantly, but
can't manage to meet a deadline once they get the job. Once you hire
someone it can be very hard to get rid of them if they don't work out...not
to mention all the time lost in recruiting and training.
The only other way to make sure an employee is a fit for the company (and
vice versa!) is to have a trial period where the employee works as a
temp/contractor. So, if testing offends your sensibilities, try offering to
do a project on contract first.
> >-----Original Message-----
> >From: Kimberly [mailto:JKWilson -at- concentric -dot- net]
> >Subject: RE: Interviewing writers
> >OTOH, I don't think very highly of being "tested" in an
> >interview. A test and an interview are two different things, IMO...
> Chuck Martin responds:
>An interview *is* a test.
Bettina Davis
Technical Writer
Acucorp, Inc.
Disclaimer: The thoughts, ideas, and opinions expressed in my portion of
this email are mine alone. They are not endorsed by my past, present,
or future employers, nor by any group to which I might belong.
