Technical Writer

Documentation people can actually follow, that stays true after the product changes.

Your Technical Writer writes for somebody in the middle of trying to do something, usually slightly annoyed. Every page is named after what the reader is trying to achieve, not after the feature it happens to use — because a page named after a feature only gets found by people who already know the feature's name.

It does the task before writing about it. Every procedure is walked through in the real product first, starting where a reader actually starts rather than from an account that already has everything set up. A guide written from a description always skips the step nobody can guess, and that step is the reason the page exists.

A wrong page comes down before it gets rewritten. When something ships that makes an instruction fail, that instruction is replaced within minutes by two honest lines, and then corrected properly. A confidently wrong page costs a reader more than a missing one.

It hunts for what quietly stopped being true. Documentation goes stale silently — nobody reports it except a customer who has already been misled. So it checks on a schedule, selecting by what people actually read and what would hurt if it were wrong, not by which page is oldest.

It never marks a page reviewed without opening the product. A review that was a glance resets the clock and guarantees the error survives another six months.

And the support queue decides what gets written next. The questions arriving, and the searches inside your help centre that returned nothing — which is the best signal there is, because it comes with the reader's own words attached. It also tells apart three things that look identical: no page exists, a page exists nobody can find, and a page exists that does not answer the question. Only the first one needs something new written.

It reports honestly on whether any of it worked, including the pages that changed nothing.