...impersonating a technical writer...

["e.ruddock" <e -dot- ruddock -at- home -dot- com>]

My job title is that of Technical Writer, but I am quickly learning that I
am not (in the true sense of the word). I "fell" into this job directly from
university two years ago, and now I can't imagine doing anything else. I
love it!! But... my current position more closely resembles that of a
documentation specialist than a tech. writer.

I work for a systems integration and factory automation company. Currently,
the engineers write the information for our systems and then hand it to me
for production. I insert the text into our standard Word template, do the
formatting, editing, and clarifying. I insert the graphics, which are
already captured and saved in a folder for me. I also create visio drawings
for architectures, and create marketing material from project profiles
completed by the engineers.

In all but a few instances, I miss out on any team aspects of a project. I
do not go on-site and learn a company's system; I don't interview users or
SMEs (other than the engineers from our company who are working on the
project); and because my position is regarded by most as a "necessary
inconvenience", I don't get to develop skills using the tools that are
becoming standard to our industry. We have FrameMaker, but don't use it. We
also have RoboHELP, but I've only used it to assist on a project. I
requested that we order Adobe PhotoShop - but my request was denied and I
was told to continue using Corel 5!

I like the company I work for, but feel I'm committing "career suicide" by
staying. I want to be able to hold my head high when I say I'm a technical
writer. I'm seeking new employment - how do I explain my lack of experience
when being interviewed, and what areas should I start to work on
immediately?

Elaine Ruddock