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.
If you're legitimately a publications manager and not just the first
tech writer in through the door during some company's startup, the
hiring process is an eternal quest for people who can do the writing
part of your job better than you can. At least it is for me. I don't
think I'd hire a candidate who couldn't run rings around me in
FrameMaker or whatever authoring tool we're using, or who didn't have
some critical skill that I either lack or am not strong in, and one of
the arguments that I use the most in trying to get approval to hire such
people is that staff members with stronger hands-on skills than mine
will improve day-to-day productivity and free me up to concentrate on
improving process and project management.
No, I probably wouldn't hire someone for a staff position whose resume
was a long chain of publications manager positions, but I'm not sure if
it would be because I wanted to avoid having to sleep with one eye open
or just because I had doubts about the candidate's reading
comprehension.
Gene Kim-Eng
----- Original Message -----
From: "bryan johnson" <bryan -dot- johnson -at- motoman -dot- com>
>I've had circumstances where I've "dumbed down" a writers resume
>because I knew the (non writing) hiring manager felt very threatened
>that this new, professional writer, would come in and take their job.
>They had moved up through the company from admin work to putting
>together basic documentation and been given the title of Tech Pubs
>Manager. The documentation was good considering the source, but nothing
>a professional technical writer would consider acceptable.
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-