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:career path in the third and fourth decades? From:Monica Cellio <cellio -at- pobox -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 22 Nov 2005 09:58:10 -0500 (EST)
Hello,
It's my impression that even the best technical writers will hit a glass
ceiling long before they complete a 40- or 45-year career, unless they
adjust their careers away from technical writing. (If you know of places
where that's not true -- where, say, a 30-year veteran can continue to
advance in salary while remaining a technical writer -- please let me
know.) I've got a pretty good idea of how the first 20-odd years of a
tech-writing career can play out, but am interested in hearing from
people who are farther along. What changes in direction did you make to
stay marketable while using the skills you've acquired? I see a few
possibilities.
Many people go into management, which works at companies large enough
to have sizable doc departments. I'm not sure where doc managers go
to be promoted -- perhaps to maangers of larger groups encompassing doc,
training, support, consulting services, and so on (managers of managers)?
That's how it played out in the one case I've witnessed.
Technical writers who are domain experts might transition into working
in that domain. A writer of programming documentation, for instance,
might shift from technical writing to being a programmer. This would
mean moving from a senior-writer position to (initially) a non-senior
programmer position, but it would seem to have growth potential. This
presumably applies in other domains too, so long as you don't seek the
senior positions.
Another path would be product management. Good technical writers have
to know their users; one could presumably transition that into a
customer-facing role involving requirements analysis, feature planning,
and so on.
For the sake of completeness I mention technical marketing and sales.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-