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: Interviews and Portfolios From:"Brierley, Sean" <Brierley -at- QUODATA -dot- COM> Date:Tue, 10 Aug 1999 13:08:53 -0400
Hallo:
>>>-----Original Message-----
>>>From: Cam Whetstone [mailto:camw -at- ROCKETMAIL -dot- COM]
>>>My objective is to work for someone who knows what I do,
>>>not someone who needs a writing sample to evaluate a
>>>technical writer.
Then, how would I differentiate between you and the next guy. Yes, there's
the resume and yes, we can talk. Should I hire only based on the ability of
a candidate to verbally sell themselves?
I agree that you should expect to accompany your portfolio, and not mail it
unaccompanied. Certainly, too, you can describe the scope of your experience
and kinds of projects you have done. I would prefer, however, while I am
interviewing you, to thumb through at least one or two samples. It's a great
conversation piece that takes the interview to better places.
