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 didn't catch the beginning of this thread. The gist (as I understand it)
Chuck Martin said:
If I were interviewing a tech writer and decided to give a small written
test, and got a response that, verbally or non-verbally, communicated the
message that "I didn't expect this," that person sure wouldn't be at the top
of my hiring candidate's list.
There have been many discussions about testing applicants on this list, so
it might be useful for you, Chuck (or whoever posted the first note about
this), to search the archives on this topic. I searched them not long ago,
and found, as we see in this latest discussion, a lot of disagreement about
I have my own opinions, but since they are mixed, I probably wouldn't
further the discussion by expressing them. ; ) However, when I searched the
archives I found a post by Eddy Skau that comments on the scenario Chuck
describes quite nicely. Eddy wrote (in part):
To me, a person who takes umbrage over writing a test would display:
1) Doubt about their abilities
2) Inability to work with a team (subtle)
3) Insubordination (where applicable)
4) Not serious about securing the job in question.
I think Eddy's overall point is correct: testing applicants reveals more
about them than just their writing skills.
Just my (and Eddy's!) two cents,
FarPoint Technologies, Inc.