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:jobs: PDX-OR-US, TW and Senior TW levels From:"Erik W. Harris" <ewh -at- PLAZA -dot- DS -dot- ADP -dot- COM> Date:Mon, 28 Apr 1997 10:05:18 -0700
For Portland-area writers, editors, and writing supervisors:
ADP Dealer Services Group has several open positions for good technical
writers, at both junior and senior levels. The positions are located at our
R&D facility, just south of sunny downtown Portland, Oregon.
Here's an example:
>Technical Writer/Course Developer--Software Tools Development, FULL TIME
>ADP, Systems and Data Communications Software Development Group
>
>SCOPE/DUTIES: The initial assignment will be on a team developing
>internal tools related to configuration management and defect tracking
software.
>Responsibilities will include writing end-user documentation and training
>materials for a variety of tools used in software development. The
>users of the tools are ADP internals and ADP technical support personnel.
>
>QUALIFICATIONS/REQUIREMENTS:
>* At least 2 years experience in software documentation or training development
>in a software engineering environment.
>* Experience in on-line documentation, WEB site administration and
development,
>and CBT development desirable.
>* Experience with engineering tools and tools development desirable.
>* FrameMaker 4.0 or 5.0 desirable.
>* At least a user-level knowledge of UNIX required.
>* Experience with Windows NT and Windows '95 desirable.
And another example:
>The basics for the OLI tech writer position: ['OLI' is our acronym for an
online document library]
>
>Primary responsibilities include maintaining a project documentation set,
>and assisting in the electronic conversion of documentation files for
>release/distribution.
>
>In addition to strong writing skills, the candidate must be an effective
>verbal communicator. Must be proficient in Information Mapping methodology,
>and have a strong working knowledge of online authoring principles and design.
>
>The candidate must be well-organized, detail-oriented, thorough, and able to
>successfully oversee numerous concurrent tasks and deadlines. Must be able
>to adapt quickly to change, and work effectively as a member of a
>multi-disciplined team. Background in or familiarity with Microsoft® Word,
>UNIX, and/or HTML a plus.
There is also at least one supervisory-level position, managing a group of
writers, open at this time.
I f y o u a r e i n t e r e s t e d in any of these positions, or know
someone in the Portland area who is looking for full-time work, please
contact me by e-mail ONLY at ewh -at- plaza -dot- ds -dot- adp -dot- com and I will follow up with
a fax number, arrangements to meet, or whatever is suitable.
An introduction to the 'inside story':
Generally speaking, for writers at this R&D facility, it's the best of times
and the worst of times. There are many opportunities to do solid,
cutting-edge work (intranet, online documentation, online help) for readers
who are starved for information in a situation of changing technology, but
the flip side of the coin is that there's a huge backlog of work to do, and
a whole lot of our 'standard practices' are in flux, evolving from
largely-obsolete, paper-intensive processes. To stay on top of it all as a
writer here, you have to be well-organized, able to anticipate requirements,
and willing to fight for good documentation standards on behalf of your
readership. You'll have to have a lot of confidence in your writing skills
*before* you start working.
About me:
I am a Senior Technical Writer at ADP; I've been here over 3 years, after
stints in Montana as a proposal writer and in Massachusetts as a technical
writer/marketing writer. I am not a manager, nor am I making hiring
decisions. Read on....
Why am I doing this?
Reason 1: We at ADP have a lot of good writers, but our 'writing culture'
within the development organization is not strong enough, in my view. We
need an infusion of energized, skilled, well-presented, articulate writers
to strengthen the group! Wannabes and desktop-publishing types should
probably look elsewhere.
Reason 2 (Truth in advertising): I can win bonuses by recommending
successful candidates. (And so could you if you worked here.) That's why I
really only want to talk to people in Portland, whose portfolios I can see
-- before I can recommend you, I want to know about the work you've done! :^D
Final note to want-ad-sensitive techwr-l-ers: No buzzwords, corporatespeak,
namby-pambyism, or marketing hype is implied or intended in this posting.
Direct flames to alt.fire.retardant.quick-action `:^| (that's my attempt
at a cocked eyebrow)
** ewh -at- plaza -dot- ds -dot- adp -dot- com aka 503/402-3295
** erik harris in portland oregon
** a senior technical writer at a large corporation
** "ille albus canne vinco homines"
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html