# Technical writer / documentation engineer

> Turns what a system does into something a stranger can follow — and, in the process, is usually the first person to discover the system does not make sense.

Page: https://flyvolo.ai/en/careers/technical-writer
Impact index: 63/100 · confidence Low confidence · assessed 2026-09-14
This is not a probability of losing a job.

## Scope

Covers product and developer documentation — guides, references, API docs, release notes. Regulated technical writing (medical devices, aviation, pharmaceutical submissions) is a different job with a different exposure, because there the document is a compliance artefact and its form is prescribed. Marketing content and general copywriting are separate occupations here.

## Tasks

### Drafting the reference

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: This is the most exposed writing task on this site, because the source of truth is machine-readable and the output format is fixed. Generating a parameter table from a signature was already partly automated by doc generators long before models; what models added is prose that reads as if a person wrote it, which removed the last reason to have a person write it.
- What this does NOT establish: A reference that is generated is a reference nobody read before publishing, and the failure mode is not wrongness but plausibility: documentation that describes what the code declares rather than what it does. That gap is only found by someone using the thing, which is the task below — so automating this raises the value of that one rather than removing the job.
- Records:
  - 2026-07-21 · Policy mandate · Korea's AI framework act requires operators of high-impact AI to write and retain documents evidencing their safety measures, and to run a plan for explaining the system's criteria and training data — https://flyvolo.ai/en/changes/ev-20260721-technical-writer-2 (source: https://www.law.go.kr/법령/인공지능발전과신뢰기반조성등에관한기본법/제34조)
  - 2026-04-01 · Worker adoption · Census BTOS supplement: writing is the leading generative-AI task reported inside US firms, and 65% of firms limit AI use to three tasks or fewer — https://flyvolo.ai/en/changes/ev-20260401-technical-writer-1 (source: https://www2.census.gov/library/working-papers/2026/adrm/ces/CES-WP-26-25.pdf#worker-tasks)

### Actually using the thing you are documenting

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: The input for this task does not exist in any repository: it is the experience of being confused in a specific place. A model trained on the codebase inherits the engineer's knowledge, which is precisely the knowledge that has to be absent for the test to work — the value here comes from not knowing. Experienced writers describe having people who did not write the documentation follow it end to end, and for medical-device instructions the US regulator judges them only by representative users performing with the device.
- What this does NOT establish: This task is the strongest argument for the occupation and the weakest in a budget meeting, because its output is an absence — support tickets that did not happen. Where documentation teams have been cut, this is the task that went first, and nothing about the technology was required for that.
- Records:
  - 2026-08-26 · Worker adoption · Interviews with 31 technical writers found documentation relies on engineers' technical review and outsiders testing it end to end, and 25 found LLM review feedback unreliable — https://flyvolo.ai/en/changes/ev-20260826-technical-writer-3 (source: https://arxiv.org/abs/2608.26232v1)
  - 2026-08-03 · Constraint · FDA guidance says instructions for use are judged by how representative users perform with the device, and that fixing a use problem by rewriting the instructions needs new test data — https://flyvolo.ai/en/changes/ev-20260803-technical-writer-4 (source: https://www.fda.gov/media/80481/download)

### Deciding what does not get written

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: Cheap generation makes this the most valuable task rather than the least, because the constraint moved: when writing everything became possible, choosing became the whole job. Deciding what to leave out depends on knowing which users exist and what they are trying to do, which is not in the code.
- What this does NOT establish: Being more valuable is not the same as being recognised: documentation is usually measured by coverage, and coverage is exactly the metric that cheap generation makes meaningless. A team judged on pages published will be rewarded for abandoning this task at the moment it becomes the important one.
- Records:
  - 2026-07-21 · Policy mandate · Korea's AI framework act requires operators of high-impact AI to write and retain documents evidencing their safety measures, and to run a plan for explaining the system's criteria and training data — https://flyvolo.ai/en/changes/ev-20260721-technical-writer-2 (source: https://www.law.go.kr/법령/인공지능발전과신뢰기반조성등에관한기본법/제34조)
  - 2026-04-01 · Worker adoption · Census BTOS supplement: writing is the leading generative-AI task reported inside US firms, and 65% of firms limit AI use to three tasks or fewer — https://flyvolo.ai/en/changes/ev-20260401-technical-writer-1 (source: https://www2.census.gov/library/working-papers/2026/adrm/ces/CES-WP-26-25.pdf#worker-tasks)

### Getting the answer out of an engineer

- Direction: Still human-led
- Basis: inferred (VOLO's reasoning, no attached source)
- Why: The information required is undocumented by definition — if it were written down, this task would not exist. Extracting it is a social act performed against somebody's calendar, and the skill is knowing which question produces the real answer rather than the official one.
- What this does NOT establish: This task is what makes the job hard to do remotely, part-time or from a contractor's chair — which is exactly the direction cost pressure pushes it. The threat here is not automation, it is the job being restructured into something that cannot include this task, after which the documentation degrades for reasons nobody attributes correctly.
- Records:
  - 2026-08-26 · Worker adoption · Interviews with 31 technical writers found documentation relies on engineers' technical review and outsiders testing it end to end, and 25 found LLM review feedback unreliable — https://flyvolo.ai/en/changes/ev-20260826-technical-writer-3 (source: https://arxiv.org/abs/2608.26232v1)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt