Unusual career
Technical Writer
Technical writers turn complex products into documentation people can actually use — API references, user guides, tutorials and help centres. It is the rare career that rewards both a love of writing and a genuine interest in how things work.
What the work involves
You will interview engineers and subject-matter experts, learn products deeply, and write clear, structured documentation that fits how readers think. Increasingly the role includes managing docs as code, maintaining content in version control, and shaping information architecture so people can find answers. The hard part is rarely the prose — it is understanding the subject well enough to explain it simply.
Skills that matter
The essentials are clear, concise writing, the patience to understand technical detail, and empathy for a confused reader. Comfort with tools like Markdown, Git and documentation platforms is increasingly expected. Strong technical writers are also good interviewers — much of the job is extracting knowledge from busy experts.
Switching in
People move in from software development, support, QA, journalism and general writing roles. Developers value the change of pace; writers value the structure and subject matter.
- Build a portfolio by documenting an open-source project or a product you use
- Learn docs-as-code workflows with Markdown and Git
- Practise turning a developer's rushed explanation into a clean guide
Frequently asked questions
Do I need to be able to code to be a technical writer?
Not always, but it helps enormously, especially for developer-facing documentation. You need to understand technical concepts well enough to explain them; for some roles, reading and writing code samples is part of the job.