This month’s discussion focused on finding jobs for those new to technical writing, transferring skills from another field, networking, and the current job market.
A central theme was: how does one get the first job as a technical writer?
Previous experience in a related field is an asset. One attendee is a student in the Associate Technical Writing Program at BCIT (British Columbia Institute of Technology), with a background in computer programming. This helped him to land a remote job with a company in Winnipeg.
Another spoke about her experience transcribing and editing Hansard documents at the BC Provincial Legislature in Victoria. Electronic transcription is not 100% accurate but it is getting better, so her job might become redundant. She is considering courses through the SFU (Simon Fraser University) Technical Communication Certificate to use her editing skills in a new area.
Language skills can also be useful. We talked about comparative editing, comparing original text in another language to a translated version and editing the translated text.
We briefly discussed finding work as a contractor. Applicants often need to write a proposal or detailed quote to convince a client to hire them. This can be challenging for a newcomer to the field, but attending networking meetings and asking experienced contractors for advice can help.
If you’re starting out as a contractor, you can find sample technical writing proposals and contracts online and adapt them to your own situation (check for copyright permission first). One person strongly recommended asking a lawyer to review your generic contract to be sure you’re well protected.
You can also find useful information in our recent webinar, “Job Search Tips and Tricks.” (Click RSVP in the article to receive a link to the recording.)
WorkBC provides general information on technical writing and job postings. One person who used their website to research the job market found that BC has about 1100 working technical writers.
Others recommended the Write the Docs website and Slack channel, an online community for “everyone who cares about communication;” and the I’d Rather Be Writing by Tom Johnson, which discusses technical communication trends, careers, and more.
We also heard about a webinar on content operations, presented by respected international consultant and former Canada West Coast chapter president Rahel Bailie. The webinar took place on October 22, but you can use the RSVP link in the webinar announcement article to receive a link to a recording of the meeting.
The Tech Comm Café provides networking opportunities, job leads, answers to work-related dilemmas, and a burst of professional energy to keep you motivated. We discuss technical writing tools and techniques, career planning, portfolios, and anything else related to working as a technical communicator.
We welcome anyone who’s interested in technical communication — contractor, in-house, student, long-time tech writer, STC member, non-member, career-changer, or recruiter. We hope to see you at the next meeting!
Next Meeting: ONLINE on Wednesday, November 20, 2024
- Subscribe to receive email announcements of future meetings.
- If you plan to attend, RSVP by 4 p.m. Wednesday, November 20, to receive login instructions.
Date: Wednesday, November 20
Time: 7:00-8:00 p.m. Pacific Time
Location: Online via Zoom
Agenda
- Introductions. Take 60 seconds to introduce yourself, your background, current activities. A good chance to try out that new elevator speech.
- Announcements and job leads. If you know of an interesting event or a job opening, or you’re looking for work, share it with the group.
- Brainstorming Q&A. Ask about a work-related problem and discuss potential solutions.
- Speed networking. Make new contacts and discuss your professional backgrounds and goals.
Susan Nishi is a technical writer with more than 20 years experience working at hi-tech companies and organizations in the Lower Mainland. In her experience, it’s true what Aristotle said: “The more you know, the more you know you don’t know,” so go talk to the developer.