Stretch distancetime to pivot: 6-12 months
Technical Writer / Documentation
Make the complex usable, for builders
Software, hardware and APIs all need documentation that is clear, accurate and findable, written for people trying to get something done. Technical writing is a well-paid, stable discipline where your clarity instinct meets a new, learnable technical literacy.
Demand 2026-2036
Growing
Stable, well-paid, persistent software demand.
Competition
Open
Salary, Stockholm
48-68k/mo
indicative, gross per month, mid to senior
What you already bring
the cards from your core that transfer straight in
What you can do
Write
Concretize
Structure
Document
SummarizeHow you think
Communication
Digital systems
Attention to detailsWorlds you know
Technology & Hardware
Programming
Communication & PRThe gap
what you would need to build
Technical literacy and the docs craft: enough understanding of software and APIs to document them, docs-as-code tooling, information architecture, and working closely with engineers.
How to get there
- Learn the technical-writing craft (structure, docs-as-code, API docs) and enough code to follow along.
- Document one real tool or API clearly, as a portfolio piece.
- Get fluent in the toolchain (Markdown, Git, a docs platform) and the developer mindset.
Your first move
// start here
Pick a tool with weak docs and rewrite one section the way it should read.
In Stockholm
Stockholm's deep software and product scene needs technical writers constantly; it is a stable, well-paid bridge from words into tech.
Ask yourself
three prompts from the professional development deck to pressure-test this move
