Got questions about technical communication? Ask the community of STC-Montreal. Send us your questions for publication. (Questions may be edited.)

Today’s question to STC-Montreal is how does a person with expertise in other fields get started in technical communication?

Dear STC-Montreal,

Several years ago I graduated with a B.Eng. in Software Engineering, but never worked as a developer. In 2009, I earned a certificate in Print Communication from Concordia’s Continuing Education Department.

To spare you a long story, I want to work as a technical communicator. My problem is that I’m unsure on the best way to get started. I’ve read blog-posts on various sites about this topic, here included. What I’ve read daunts me: I fear that I may have underestimated what it will take to get a junior position as a TC. I assumed that I could start sending out resumes right away, but now it appears that if I want an HR person to even glance at my CV, I need 1) a certificate in technical communication 2) a solid portfolio and 3) a good handle of software packages like Framemaker and Robohelp, and 4) real-world experience. I don’t have any of this stuff.

So, I’m wondering whether I’m right to be nervous about my prospects. Must I have a certificate/portfolio/experience and software skills when I’m just starting out? Is my background any help at all? Are there things that I can learn later, but others I need to have and to know asap? How long does it normally take to get those essentials so I can successfully apply for positions?

I know it might sound like I’m looking for shortcuts. I’m not – I just don’t know anybody in the field so I lack the knowledge that’s truly required to become a technical communicator and to set my expectations accordingly for this vocation.

I’m grateful for any advice on how to start out. Personal stories are welcome too.

— Alex

Join the discussion. Leave your ideas and suggestions for Alex in the comments below.

Read past episodes of “Ask STC-Montreal.”