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: Tech Writing 101 - How to tie a shoe From:"Clark, Robert" <Robert -dot- Clark -at- SCHWAB -dot- COM> Date:Tue, 12 Jan 1999 13:14:49 -0800
Garret wrote:
"If anyone has every taken a shot at this (for a writing test, etc.) I'm
> collecting examples for a tech writing class. Please, no shortcuts (i.e.,
> "Wear loafers.")"
>
> Garret Romaine
> garret -dot- h -dot- romaine -at- tek -dot- com
>
>
Garret,
Your comment about no shortcuts brings this question to mind. You're not
trying to cheat on your homework are you? Why don't you share with us what
YOU have written?
Actually, I have seen this question and similar ones from prospective
employers. While it is valuable to have the employer learn about your
skills in descriptive narrative, if I can't convince them with samples and
the stuff on my website, I bail out of the interview, that is unless, the
company actually makes shoelaces and needs a user manual. :)
This may be an interesting topic thread to discuss:
What things do you enjoy/object to during the interview process?
For me, I NEVER, EVER fill in the past employment or salary history
information on applications. I always put "see resume" and leave the salary
area blank. I went to great lengths to create a winning resume and I
strongly feel it is a waste of time to have to rehash the dates and
descriptions on their form.
As for salary history, AARGH! It's none of their business. What I made on
previous assignments has absolute no bearing on what I am willing to work
for on their new position. When the question is raised in the interview, I
come back with a question about what their budget for the position is, i.e.
what range they were thinking of. That way, they can quote a figure and I
can come back with "that's a little less than I was thinking of, but
considering my experience and skills and what a great opportunity this is, I
would be willing to consider an offer at XXX."
It's these little things that save a lot of time job shopping and separate
out the sweatshops from the great places to work.