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: The Technical Writing Field From:Tom Murrell <trmurrell -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 28 Jun 2001 06:04:28 -0700 (PDT)
--- george -dot- m -dot- hook -at- accenture -dot- com wrote:
> Hi, TECHWR-L Members:
>
> I'm a novice at technical writing, but it is a field that intrigues me.
> I've developed a fair background in technical editing and writing while
> working here at Accenture, but I still need some help with the basics.
> I've been reviewing job descriptions here and there, and some of the terms
> are still vague to me.
George, the first thing you need to understand, if you don't already, is that a
job description in an advertisement is generally a wish list. "Here's
everything I can think of that I might possibly want in a person who fills this
position, for this price," that is, for the salary range advertised. Generally,
but not always, you can't get everything you want for the price you want to
pay. For example, I want a brand new Lexus, and I'm willing to spend up to
$20,000 to get it. (I don't think I'm gonna get that Lexus, but that's what I
want. <g>)
> For example (and I know this is very basic):
>
> Must be able to interpret technical information and write clear
> documentation (does this mean strictly technical manuals and books and
> such, or does the term go beyond that definition?)
Probably doesn't mean technical manuals and books at all. It means anything
from well-structured architecture, requirements, and design documents to
half-thoughtout ideas on napkins from the cafeteria. (And mind that stain, it
partially covers the key component of the whole concept! <g>) It means you need
to be able to decipher writer-based engineer/programmer/designer-speak. It
means you'll be asking lots of questions to fully understand what you're to
write about. It also means you need to be able to figure some things out with
minimal clues from the documentation available to you.
If you go back and check the recent archives, we've had some excellent threads
on the need for Technical Writers to be Resourceful. In a nutshell, that's a
key component that hiring managers are looking for.
> Experience developing and managing documentation repositories (I have no
> idea ...) and web development is a plus (are technical writers also web
> designers?).
Someone else already mentioned the possibility of using repository software
programs. I'll mention one other possible aspect. They may be saying, "We've
got a ton of documentation, but we can't find anything. We need someone who can
organize what we've got and make it so we can find the specific piece of
information we need when we want it." I've worked a few places where the
"Documentation Repository" was a folder on someone's hard drive, or a series of
disorganized folders on a network drive. Again, hiring managers may be looking
for someone resourceful enough to organize things in some useful way.
Web design can be anything from doing the whole site to converting Word Perfect
files so they can be viewed online.
Keep in mind that these advertised job descriptions are a starting point and
not necessarily descriptive of what an employer actually needs. What YOU, or
any other prospects, need to do is probe such "qualification" statements to
find out what the employer means by those phrases. When I look at such a list
of required qualifications (or even things that "are a plus," I assume
automatically that I'm qualified. What I want to know is what they specifically
mean in each case. What end of the spectrum are they on? Equally important,
what end of the spectrum do they want to move toward? What are their REAL
needs, and how can I address them?
All of this highlights, I hope, the importance of doing your homework before
you go to an interview. Prepare a list of questions that will draw them out as
to what they really do and what they really need. That way you can decide
whether you (a) can do the job [you probably can], and (b) want the job.
Remember (and this is my own definition), a Technical Writer doesn't need to
know much, but a Technical Writer needs to be able to learn whatever is needed
to communicate effectively to the audience. The resume and the interview are
your chances to show the hiring folks that you have the underlying
resourcefulness and skills to do that.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
