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: interviewing and spotting "fibs" From:howard <pencil -at- WAVENET -dot- CO -dot- UK> Date:Mon, 21 Sep 1998 20:17:29 +0100
>C Davis wrote:
>If you want to test people, find a copyediting test or "rewrite this
>paragraph" >test from an old college textbook. Run off 50 copies and
>include them with the >application form. Don't make the test over long or
>you might turn good >applicants off (about 10-20 minutes). Don't interview
>anyone that doesn't turn >it in. You can even give the test to the
>receptionist for the person to do >while they wait for the interview.
This appears to be a good test of writing and information structuring
abilities but, if you suspect people are lying about their abilities,
what's to stop them getting someone else to do the test?
Also, given the earlier posts' complaints of people not being able to use
the software, would it not be a good idea to also provide a computer to do
the test on - maybe even, if the interview structure allows it,
mid-interview; say between individual interviewing and a panel interview
(gives the panel 10-20 minutes to discuss their perceptions without leaving
candidates chewing themselves up with nerves)?
Provided it is made clear to the candidate that this is being done, you
could even use a keystroke/movement recorder - not so much to "catch them
out" but to assess their approach to the application, learning curve, and
general competence.
Perfectly acceptable user-testing techniques given last week's posts on
that subject - so, if they'll be using your computers and software, why not?
'twould allow those who can learn quickly to demonstrate their suitability
for a job even if they don't know the particular application.
If they can use the software quickly and well, then their ability to use
company- or site-specific macros and style sheets and suchlike shouldn't
(to my mind) be too much trouble.
And you also get your original required information - whether or not they
can write/structure/layout information.
I admit this approach may be unsuitable for idiosyncratic or
counter-intuitive applications, but in this situation at least you'll know
whether those that claim, upfront, they can use it actually can or not.