Sign upSign InSign upSign InAmber NunneryFollowCode Like A Girl--ListenShareIt’s common to assume that Technical Writing is limited to software development, that it’s strictly manual writing, or that it’s exclusive to tech professionals. While this is true in some cases, technical writing covers a surprisingly broad spectrum of work, and is very unique to the company it’s done for. Essentially, technical writing is the act of gathering, arranging, and writing a polished version of complex technical information that is most logical, efficient, and effective for a specific audience.Technical writers are often the internal development communicators between multiple company departments and, potentially, clients and end users. The writing itself falls into several categories, some of which include software user stories and release notes, product manuals and specifications, knowledge bases and FAQs, proposals, scripts, audience analysis, product and market requirement docs, competitive analysis docs, information architecture (IA), flowcharts and roadmaps, and case studies. Prototyping and API (Application Programming Interface) documentation are worth looking into, and science and medical writing are also their own.These tips are for you if you’re called to this type of work.Given that technical writing handles niche company content, your most valuable asset is that of the operations in your current job role and your knowledge of them.Assess what systems, procedures, and specific information you operate under or handle within your current role. Can you imagine creating quality instructions for them? Do you have opinions on how resources, systems, and communication can be improved? Are you driven to establish resource banks or design information?If any of these questions are a yes, you’re already a great fit for technical writing.Even if your level of education isn’t geared towards technical writing, anything you’ve studied or worked on can be valuable.For example, production workers are walking knowledge bases for the work they do and the equipment they use. English majors are another example of transferable skills with their awareness of voice, style, and overall tone needed to communicate to specific audiences successfully.Specialized science degrees or backgrounds can be an advantage since you hold strong foundational knowledge of a field which most likely needs technical writers. For example, someone with a biology degree easily has the necessary expertise to document lab procedures or equipment manuals.Another example would be a tech-savvy person with an education degree who knows to document EdTech product requirements. Or, a background in programming lends itself to software development technical writing.An ideal combination would be a science or technical-based background with proven English writing and communication skills, but it’s not the only route.Technical writing requires a solid understanding of plain language, active voice, grammar, punctuation, and sentence structure. If you haven’t written in years, revisit the fundamentals: parts of speech, clauses, commas, and syntax. Plain language and active voice will be easier once you’ve got grammar and punctuation down.Some online resources for grammar and punctuation include English Grammar 101, The Punctuation Guide, and Udemy. Grammarly is a nice tool, but it’s best to have the skills and knowledge aside from a helper like Grammarly.If you find that your background doesn’t support you enough, resources are available. One of the most popular online technical writing certification courses is Technical Writer HQ. It’s affordable, self-paced, informative, and provides hands-on practice, real-world examples, and a capstone project that acts as a portfolio (with free, professional feedback).Udemy is also loaded with niche technical writing courses since software development technical writing is in high demand. These include branches of business writing, information architecture, prototyping, coding languages, Markdown, and API writing.A range of software, platforms, and tools are used for technical writing. If they’re free, download, learn, and create with them. If they cost money, use a free trial to do the same.Platforms for technical writing can be grouped into three categories: foundational, supplemental, and AI-based.Foundational platforms include Microsoft Office 365, and in some cases, Google Workspace. Microsoft Word is the age-old word processor used for most formal writing. Google Docs are close behind, but Word is superior in its available tools. Along with Word and Docs, Microsoft PowerPoint and Google Slides are also considered foundational for certain areas of technical writing.Supplemental tools assist with building charts, graphs, and visuals. These include Snagit, LucidChart, Draw.io, Figma, Madcap Flare, and Microsoft or Google-related shortcuts for generating visuals (like turning an Excel table into a pie chart). Adobe Technical Communication Suite, although pricey, is also highly resourceful.You may worry that a move into technical writing is risky as we enter the era of AI, but take comfort in the fact that out of the various fields of writing, technical writing is one of the safest. Given its focus on highly unique company information and the need to achieve context-heavy accuracy, technical writers are and will continue to be in demand.Context-heavy accuracy through AI can only be produced with highly-trained prompt writers, which relies on the skills of a technical writer. Only a human can contextualize relevant company information and ask the right questions to subject matter experts (SMEs) to gather the specific information for documentation and prompt writing.For specific AI software tools, check out this Unite.AI article.A portfolio is essential for breaking into technical writing. This can be done by voluntarily creating technical documentation for your current role or by creating it for a hypothetical company scenario, whether it’s through a certification or independent.Identify a system or process that needs an instruction manual or FAQ. Create a knowledge base for older software that’s used within your company. Or, imagine a hypothetical app, and create each stage of software development documentation for that app. Note: Technical Writer HQ provides in-depth documentation types and stages for software development settings.If you can create high-quality technical documentation for a hypothetical company or product, imagine your potential when you’re onboarded into a company and surrounded by real context, processes, and SMEs.Portfolios speak.Given the massive role that technical writing plays in company and product operations, writers must be able to receive feedback open-mindedly. After all, writing is meant to serve a large-scale functional purpose for everyone involved. Think of your readers’ feedback as a customer survey.If you know anyone who works as a technical writer, works in a similar business setting to your portfolio or is just familiar with the purpose of technical writing, ask them to read your portfolio and give feedback. The writing process, even technical writing, requires editing and revising, and it’s usually more effective when done with a separate pair of eyes. Be willing to use your readers’ input to improve your “product.”If you’ve created a portfolio, possibly gotten certified, and started pursuing a technical writing position, own it. With a dense technical writing portfolio, you have permission to own technical writing as something you do.Create a website that displays your portfolio. Some resources for this include Wix, WordPress, or Journo Portfolio. Display your portfolio URL directly on your resume. In your “about” section, provide an honest case:I’ve worked as an _____ for X years, and am transitioning into technical writing.You’re not fooling anyone; you’re taking initiative. As long as you’re honest about the fact that you’re making that transition, you’re doing it right.There are plenty of transferable skills that lend themselves well to technical writing, but ultimately, any writing experience and detail-oriented management you have is what you should leverage most. Your actual work history should complement your technical writing portfolio.For every job title and summary in your job history, consider focusing on documentation or systems you’ve planned, created, edited, revised, or curated. Make those details your primary focus for what that role entailed.As with many career pursuits, breaking into technical writing may take time. If you’re applying for roles, take note of job descriptions and skills you could potentially research and gain knowledge in. Follow up with direct messages that include a portfolio link. Patience is important, but persistence will get you somewhere. Eventually, the work you’ve put in to own the title will catch someone’s eye.----Code Like A GirlTexas-based technical writer. Find me at ambernunnery.com.Amber NunneryinAge of Awareness--Python Code NemesisinCode Like A Girl--1Python Code NemesisinCode Like A Girl--1Amber NunneryinAge of Awareness--1Jari RoomerinBetter Humans--108Unbecoming--836Nick Wignall--190Stephen AdesinainLevel Up Coding--80Microsoft DesigninMicrosoft Design--67The PyCoachinArtificial Corner--513HelpStatusWritersBlogCareersPrivacyTermsAboutText to speechTeams