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 have been interviewing technical writers for years, and I would never ask
them to leave their portfolios. Sometimes these are the only samples of
work that they have, and I have heard too many stories of writers never
getting their samples back.
Usually I set up a team interview with my most experienced writers. We pass
the samples around to the members who are currently not interviewing and
make sure that everyone has a chance to spot read them while the applicant
is talking to someone else. By the time the applicant is ready to go, we are
finished with the samples. Of course we don't read them completely, but we
can see enough to get a good idea of the writer's skills.
> -----Original Message-----
> From: Darren Barefoot [SMTP:dbarefoot -at- mpsbc -dot- com]
> Sent: Monday, March 13, 2000 1:34 PM
> To: TECHWR-L
> Subject: RE: portfolio questions
> Good morning,
> Mr. Czekalski makes several good points, though he seems a little paranoid
> with regards to his third rule below. Often during interviews I don't have
> enough time to seriously read or examine a portfolio sample. If the writer
> is not willing to leave me material (or a copy of the material) how can I
> adequately evaluate their skills? If the work is propreitary, why bring it
> to the interview at all?