My suggestion would be to push the fact that you do have technical and writing skills. I'm at a point where my ability to get a different tech writing job is limited by my inability to code/read/decipher/whatever C, C++ and/or Java.
Point out published work, whether articles or stories, regardless of how technical they may or may not be because that gives them the "writing" part. That you know development and engineering gives them the "technical" part.
Learning the tools, on the other hand, or pointing to experience with the tools, will be the part you'll have to talk around. If you know Microsoft Word, you'll be able to use Robohelp up through their most recent version (which I haven't seen, but have been told is different) -- Robohelp was just a wrapper around a Microsoft Word sort of thing. FrameMaker is more complicated, but relatively easy to pick up once you're using it. But it can be frustrating convincing them that while you know a bunch of other things, and things that are close enough, that you can pick up other tools given a bit of time.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
momijizukamori
no subject
Date: 2002-03-21 18:40 (UTC)Point out published work, whether articles or stories, regardless of how technical they may or may not be because that gives them the "writing" part. That you know development and engineering gives them the "technical" part.
Learning the tools, on the other hand, or pointing to experience with the tools, will be the part you'll have to talk around. If you know Microsoft Word, you'll be able to use Robohelp up through their most recent version (which I haven't seen, but have been told is different) -- Robohelp was just a wrapper around a Microsoft Word sort of thing. FrameMaker is more complicated, but relatively easy to pick up once you're using it. But it can be frustrating convincing them that while you know a bunch of other things, and things that are close enough, that you can pick up other tools given a bit of time.