Re: Interviewing technical writers
Seems like a waste of time to schedule an interview before seeing
writing samples. It's common for job listings to ask for resume and
samples both.
Actual proprietary samples should be "eyes only" and classified samples should not even exist. Indeed, if a sample appears to violate proprietary or security guidelines, that alone is sufficient for rejection. "Held XXX Clearance," said one applicant's resume. "Can't hire him," said one of our managers, a former Nuclear Test person. "The name of that clearance is classified."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.
http://bit.ly/doc-to-help
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
References:
Interviewing technical writers: From: Kim Bieler
Previous by Author:
Re: Interviewing technical writers
Next by Author:
Re: i.e. vs e.g.
Previous by Thread:
Re: Interviewing technical writers
Next by Thread:
RE: Interviewing technical writers
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads