Become a tech writer: a quickstart guide

Published: Last updated:

Every so often, someone joins the Write the Docs Slack, and asks a ton of questions around getting started in tech writing (or retraining with in-demand tech writer skills). This post captures my favourite resources, my perspective on key skills, and an outline learning path. In the spirit of a code quickstart, it doesn't aim to be comprehensive, and it's highly opinionated. It is biased towards software documentation.

The properly quick quickstart

The longer quickstart

What is a tech writer?

A technical writer (or technical author) produces material to help users achieve their goals. This can be anything from API documentation to help developers use a service, to in-app help to support new product users, to IKEA furniture manuals. As the name implies, tech writers primarily produce written material, but many also use screenshots, videos, diagrams and so on.

So you want to be a tech writer? What next?

Stop and think. Ask yourself the following:

  1. What areas do you already have expertise in? For example, if you're a developer, you may find it easier to switch to documenting code than writing vehicle maintenance manuals.
  2. What subjects do you want to write about? You may be a developer who's sick of code, and thinks writing about vehicle maintenance would be a refreshing change.

If your answers to the first two questions are very different, keep in mind that in addition to tech writing skills, you'll also need to learn a little about the domain you're documenting. Tech writers don't have to be experts, but it helps to have some familiarity with your topic.

  1. What type of job do you want, and how do you want to work? Are you happier as an employee or freelance, on-site or remote? What type of company you want to work for? Although I love freelancing, I undoubtedly benefited from time as an employee.

Defining your answers to those three questions will help focus your learning, and narrow your job search.


Technical writing has its own conventions and rules. It is a restricted, simplified use of language, and takes practice.


Trying out a static site generator may help you identify other gaps in your tech and tooling skills.

Don't stop learning

In addition to writing and tooling skills, you will need:

And, crucially, you need to keep these skills up to date. Popular tools and methodologies change. Even style conventions evolve. Don't stop learning.