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.
--- Diana Barnum <dbarnum -at- columbus -dot- rr -dot- com> wrote:
> Hi,
> A local company familiar with my writing background, asked if I'd be
> interested in this job:
>
> Automating the Software Configuration Management process for a major
> insurance provider. We need process and detail oriented people who
> understand the Software Development Cycle.
>
> Anyone familiar with this? Is it writing the process in a lay-person's
> manual?
If I had to base my sole decision on those two sentences, I would not say it
was a writing job. I would say they are writing code to automate what is a
manual, or partly manual, configuration management process, and they plan to
follow some sort of a process that they choose to call a Software Development
Cycle.
Now it would make sense that if they are creating software that they would need
an array of documentation to go with it. I would ask this company that is
familiar with your writing background if writing the documentation is why they
showed this to you or if they're wondering if you want to get into the coding
side (or even project management or requirements or whoknowswhat).
I think you need to ask for clarification on this one. I wouldn't reject it or
accept it without more information.
