23-03-2026

3 mins read

The strange case of the „technical writer“

Or: why „technical writer“ is the most misleading job title in tech

There’s a small professional paradox I live with.

I’m trained in linguistics, which means I tend to take words very seriously. Which makes it slightly awkward that my own job title doesn’t quite mean what it says.

Lately, there’s been more conversation about how the role of technical writers is evolving. And yet, the name itself hasn’t really caught up.

“Technical writer” sounds straightforward enough: someone who writes about technical things. Someone who produces documentation.

Which is technically correct.

And also strangely misleading.

Taken literally, the job sounds suspiciously close to typing: taking existing knowledge and turning it into sentences.

In reality, writing is often the smallest part of the work.

A great deal of time goes into:

analyzing complex systems

structuring information

aligning terminology

understanding developer workflows

thinking about discoverability

designing documentation architecture

collaborating with UX

improving developer experience

In other words: making sure knowledge can actually be found, understood, and used.

The writing usually comes last.

As someone with a linguistics background, I can’t help noticing that the title technical writer describes only the very final step of the process.

It captures the output—not the thinking that makes the output possible.

Technical writing is one of the few professions named after its output rather than its thinking.

Before anything is written, there’s a great deal of invisible work: understanding how a system behaves, identifying what users actually need to know, structuring information so it makes sense, and deciding how knowledge should be presented.

In practice, technical writers spend less time producing text and more time shaping how knowledge is structured within a product.

The role often sits somewhere between:

information architecture

knowledge design

developer experience

product thinking

The writing is simply where all that thinking becomes visible—which makes technical writer a slightly curious job title.

It’s a bit like calling chefs “recipe typers.”

Technically not wrong. But it misses most of the interesting work.

Maybe the name made perfect sense when the profession first emerged, at a time when the visible part of the job really was producing manuals and documentation.

But the work has evolved.

Today, technical writers spend much of their time shaping how knowledge moves through systems: how information is structured, how terminology stays consistent, and how users find their way through complex products.

In other words, the job is less about writing and more about making knowledge work.

So perhaps the title is simply a historical artifact: a profession named after its most visible output rather than its actual craft.

For now, “technical writer” will have to do.

Even if writing is usually the least mysterious part of the job.