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: Job searching in this time of attrition... From:Jen Jobart <jenjobart -at- gmail -dot- com> To:Gene Kim-Eng <techwr -at- genek -dot- com> Date:Wed, 5 Oct 2011 15:50:02 -0700
My group's docs are available on the web. Most of them are on http://code.google.com and http://developer.android.com/index.html, and the
locations of both sites can be easily deduced from the job posting. As a
publications manager, I always welcome feedback from candidates about my
group's docs. I may not agree with the feedback but I can still learn a lot
from it, not the least being whether or not the candidate was jazzed enough
about the job opportunity to read our widely-available docs ahead of the
interview. Such a conversation also gives me the ability to assess how a
candidate gives hard feedback, which is good information to know. I may not
agree with the feedback, in which case I like to see how a candidate
responds to my disagreement. Or I might agree with the feedback and respect
the candidate all the more for it. But regardless, whether or not I'm
likely to act on the candidate's feedback is actually rather irrelevant; I'd
still like to hear it.
On Wed, Oct 5, 2011 at 12:20 PM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> My concern about this approach is that unless you are familiar with the
> company's industrial sector, its customers' needs and their known issues,
> what you perceive as "a problem you've identified" may not be something the
> company thinks is anything that needs solving. The last thing you want to
> do is tell a publications manager who isn't trying to fill a position and
> who may have actually been the author of any document you might find that
> you can solve a "problem" that isn't perceived as one.
> Gene Kim-Eng
> > From: Steve Schwarzman <steve -at- writersbookmall -dot- com>
> > Bobby, in addition to looking for posted jobs, also try contacting
> > companies/organizations that you'd like to work for. But don't call cold.
> > your research first. Find out what they do, what their docs look like,
> > who's who. Then send an email offering specific assistance in solving a
> > particular problem you've identified to the relevant person. And then
> > up with a phone call. You might get an opening in the door in this way,
> > offering to help solve a problem instead of asking for a job.
> Create and publish documentation through multiple channels with
> Choose your authoring formats and get any output you may need. Try
> Doc-To-Help, now with MS SharePoint integration, free for 30-days.
> You are currently subscribed to TECHWR-L as jenjobart -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
> Please move off-topic discussions to the Chat list, at:
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://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-