Writing tests seem to be a necessary evil when applying to writing jobs. Sad, but true. We are in a profession where we’re often asked to prove our skills on the spot. Somehow, this one-off, time-constrained document will tell a potential employer whether you are set to succeed or fail in a particular position. So how can we prepare ourselves to perform our best under such unusual circumstances?
InfoDevDC kicked-off their event season Tuesday night with Content Strategy to the Rescue! Opower hosted the event that featured a presentation by Theresa Rogers and an Oktoberfest-themed spread (a keg, brats, the whole shebang). It promised to outline how Opower built their knowledge management team and teach how to grow an effective, sustainable content strategy from the bottom up.
When searching for a technical writing position, your samples can make all the difference. Prospective employers want to see that you can, in fact, write. They want to see how you approach subjects, structure documents, and adhere to style. So when it comes time to find a job, and you don’t have any samples on hand, what do you do?
For technical communication, accessibility refers to how available information is to those with disabilities. Those who are blind, colorblind, or hard of sight rely on accessible documents to easily absorb information. To make accessible documentation, technical writers have to first be familiar with regulations. Then, they can learn how to adhere to those regulations.
Office glossaries are goldmines for technical writers. Too often, when writing or editing documents, technical writers come across terms they just aren’t 100% sure about. So what can you do? Ask a subject matter expert to explain? Take an educated guess? If you’re lucky enough, the office has a glossary which identifies and defines office terms.
That’s all well and good, if the office has a glossary. And if it doesn’t? Write your own of course! But what goes into a glossary? Here’s a run down.