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.
On Friday, November 19, 1999 11:43 AM, SteveFJong -at- aol -dot- com
[SMTP:SteveFJong -at- aol -dot- com] wrote:
> Anthony Markatos <tonymar -at- hotmail -dot- com> has the intriguing idea of asking
to
> see a company's specs in a job interview. I see where you're coming from,
> Tony, and I think you would learn what you want to learn from it, but as
a
> hiring manager I think I would not grant such a request, because I'd feel
> paranoid about letting someone who might not take the job see
> company-confidential material.
>
> (If I *did* let you see specs, depending on the product you might see
> something pretty reasonable, or something pretty awful--but that's just
us.)
>
> -- Steve
>
Tom responds:
Would it be as valid to let interviewees see project specs from an older
project? Or maybe even the interviewee could initiate a discussion about
specs. I think most technical writers would be observant enough to figure
out if the company builds to the specs or builds as they go. I've been in
places where ad-hoc works and I've been in places where it won't and I
would venture to say, it isn't too hard to tell which companies really
stick to the specs by asking the right questions about their processes.
Tom Johnson
Marketing Coordinator/Technical Writer
Elk Rapids Engineering Div., Star Cutter Company
johnsont -at- starcutter -dot- com - work
thomasj -at- freeway -dot- net - persona
