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.
Marc and Becca have given you good advice! I repeat what they
commented below, because my portfolio really helped to organize
what I had done, how I had done it, and what I felt I was capable
of doing for a prospective employer.
Oddly enought, however, only two interviewers requested to see
my whole portfolio. Another wanted just my 'best sample,'
another instead gave me a writing test (mmm, isn't it fun
being asked to write about something you know nothing about
and have 1/2 hour to investigate), and another didn't even
ask if I had samples.
I AM NOT encouraging you to abandon creating a portfolio. Just
be prepared to show only part of it or even none of it at all. Make
sure that it is organized in such a way that if the interviewer
runs off with it and you are not there to describe the samples
that they (he/she/it :-) ) can easily determine the purpose
and value of each sample.
Gretchen L. Toth
Technical Writer
The Iconovex Coporation
gretchen -dot- toth -at- iconovex -dot- com
Marc Santacroce Thu, 17 Aug 1995 01:04:51 -0700
>I find that a portfolio helps me keep control of the interview by letting
>me guide the discussion according to how my portfolio is arranged.
'Becca' 17 Aug 1995 09:05:45 -0800
>and for each a brief 1 pgph description of what the problem was
> that this doc solved, or some unusual situation and how this sample
>resolved the problem or some such
