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.
Sybille mentioned:
--------------------------------------------------
How about creating some samples for the sole purpose of showing them to
interviewers? In those samples you could show how you think it should be
done. The text used could be anything - use some Latin sample text if you
want - but the layout and what-have-you would be yours.... That'd show your
approach the best as it isn't influenced by something like a "corporate
design" or other guide lines within the company. The same document could be
prepared as a Winhelp, HTML help, hard copy, PDF file - whatever takes your
fancy.
--------------------------------------------------
Well, yes, that is all well and good if you want to show off your layout and
design skills. But many companies already have a corporate look-and-feel.
What they want is someone who can communicate their technology to the people
who are buying it. That means content. In that case, Latin sample text
won't tell them anything about how well you communicate.
So, like everything else we do, it boils down to audience. Does the
interviewee want to see how well you write about technology or how well you
format a document, or perhaps both?
My advice: find out what they want to see, then show it to them.
Jason, The Contrary Man (er, Non-Gender-Specific Writing Resource of Another
Opinion)
