A technical author's job is to sit between an expert who knows something completely and a user who knows it not at all, and build the document that closes that gap. The primary pull is Explanation in its purest form: nothing is created that did not already exist as knowledge somewhere, and nothing is fixed or organised for its own sake — the entire value of the work is making the confusing understood. The daily texture is interviewing engineers or specialists who are often bad at explaining their own expertise (because it has become automatic to them), translating what they say into something a first-time user can follow, and testing that the instructions actually work by trying to follow them cold.
In regulated industries — medical devices, aerospace, pharmaceuticals — this work carries real legal weight: a badly written instruction manual for a medical device is not just a bad user experience, it is a compliance and liability issue, and technical authors in those sectors work inside formal review and sign-off processes closer to what a lawyer or an engineer would recognise than what a general "writer" would expect.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
The bottleneck is almost never the writing. It is getting time on a busy engineer's calendar, extracting knowledge from someone who has forgotten what it was like not to know it, and then getting the resulting draft actually reviewed and approved before the deadline. Pay reflects the field's low visibility more than its actual value: UK technical writer salaries have a median around £40,000, with a typical range of roughly £32,000 to £55,000 and London roles averaging closer to £47,500 [survey_aggregator, Indeed / Glassdoor 2026] — solidly comfortable, but well below the software engineers whose work they document, despite depending on similar technical fluency.
There is no required degree. English, journalism, linguistics, and technical or STEM degrees are all common starting points, and increasingly so is a computer science or engineering background paired with strong writing. A portfolio matters more than any credential — many entrants build one by contributing documentation to open-source software projects, which is one of the field's genuine no-degree-required entry routes. In the UK, the Institute of Scientific and Technical Communicators is the closest thing to a professional home, offering membership and standard-setting rather than a hard gate [official, ISTC 2026]; the field's former largest certifying body, the US-based Society for Technical Communication, ceased operations in January 2025, so entrants should not plan around a single certification existing to validate them [org_status, STC 2025].
The real bottleneck was always SME time and knowledge extraction, which AI does not touch; regulated-industry sign-off keeps this fully human regardless of draft quality.
Entry-level mechanical work compresses; senior writers owning extraction, editorial judgement, and compliance review are stable-to-growing.
People drawn to Technical Author / Documentation Specialistare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.