Who & why
Makes product knowledge accessible: clear docs, guides, API reference, release notes. Ensures the product and system are easy to understand and use, without "figure it out from the code". Translates the complex into the clear so the reader reaches their goal in minimal time. Without one: knowledge lives in heads and chats, onboarding is "ask Vasya", users don't get it, support drowns in repetitive questions.
A day in the life
Morning: take a feature/API to document, learn how it works (code/spec, talk to an engineer), define the audience and its task. Day: write structured from the reader's task (not the code structure), add examples, test on a real scenario ("follow your own instructions"), keep one style & terminology. Evening: update release notes, translate RU/EN, prune stale content, check term consistency.
Key skills
Hard: clear writing (plain language), information structuring, docs-as-code (Markdown, Git), API docs (OpenAPI), code reading, style guides & terminology, docs IA, RU/EN. Soft: reader empathy, simplifying the complex, curiosity, working with engineers, precision.
Artifacts
Docs/guides, API reference, README, release notes, glossary. Linked to the "Guides" section of the base; built on the User Story (the reader's task) and specs.
How AI / vibe-coding boosts the role
Docs from code/spec; API reference; RU/EN translation; clarity/term check; examples & snippets — with ready prompts.
Growth: Junior → Middle → Senior → Lead
Junior: docs to a template. Middle: documents features/APIs, holds style & terms. Senior: designs the product docs structure & process. Lead/Head of DocOps: docs & process company-wide.
Common mistakes
Docs from code structure not reader task; bureaucratic complexity; stale docs; no examples; inconsistent terms.
What to learn
Plain language, task-based structuring, docs-as-code, information architecture, style guides, DX, Diátaxis (doc types). Read: Docs for Developers; Google/Microsoft Style Guide; diataxis.fr.
Salary (RU)
Junior ~80–140k₽/mo, Middle ~140–220k, Senior ~220–330k. Varies by grade/technical depth/city/year — check current data.
Laskoff agent mapping
No direct mapsTo; final docs are part of the Quest Deliver phase (report + docs/JOURNAL). "Docs updated" is part of DoD. Home skills: docx/xlsx/pdf/pptx; the "Guides" section is product documentation as markdown steps.
🤖 Persona prompt
You are an experienced technical writer. Help me make product knowledge accessible through clear documentation. Always first define the audience and its task, and structure the text around what the reader wants to do (task-based), not the code structure. Write plain language: short sentences, simple words, active voice, no bureaucratese. Add practical examples and snippets — people learn faster from them. Keep one terminology (glossary) and one style. Keep docs next to the code and current — stale docs are worse than none. On request give docs from code/spec, API reference, RU/EN translation and clarity checks.