Roles · Technical Writer · Junior
10 core skills, 45 in total. Expectations per skill, and what changes at the next level.
This page lists what a Junior } is expected to know and do, skill by skill. Core skills are the ones a manager and peers assess in a review cycle; the rest count only in self-assessment. Main areas: API & Integration, Version Control & Collaboration, Documentation.
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Understands REST API principles: HTTP methods, status codes, URI structure, JSON. Knows OpenAPI/Swagger specification at a basic level. Can document simple CRUD endpoints with parameters and responses.
Understands the documentation-as-code principle: documentation stored in Git, versioned alongside code, reviewed through pull requests. Can create and edit Markdown files in a repository, submit PRs with documentation changes.
Understands principles of writing developer-friendly API descriptions: clarity, completeness, usage examples. Knows the difference between reference docs and conceptual guides. Can write parameter and field descriptions in a clear style.
Understands main types of architecture documentation: system overview, component diagrams, sequence diagrams, deployment diagrams. Knows C4 model notation at a basic level. Can document simple architectural decisions using templates.
Proficient with basic diagramming tools: draw.io, Lucidchart, Miro. Can create simple diagrams: flowcharts, sequence diagrams, mind maps. Knows basic notations: UML basics, flowcharts, network diagrams.
Knows main docs-as-code tools: MkDocs, Docusaurus, Sphinx, Hugo, Jekyll. Can set up a basic documentation site from a template. Writes documentation in Markdown, knows reStructuredText basics.
Understands the purpose of a knowledge base for a technical team. Knows popular tools: Confluence, Notion, GitBook, Bookstack. Can structure information in a wiki: create pages, links, tables, templates.
Understands the purpose of runbooks and their role in incident response. Knows runbook structure: prerequisites, steps, checks, rollback. Can document simple operational procedures based on engineer descriptions.
Understands technical blogging formats: tutorials, how-to guides, case studies, announcements. Knows SEO basics for technical content. Can write simple technical posts with code examples and screenshots.
Understands user documentation principles: clarity, task-oriented approach, progressive disclosure. Knows user doc types: getting started, tutorials, how-to, reference. Can write step-by-step instructions for end users.
Not assessed by the team, but part of the self-assessment and the development plan.
45 skills get a higher expectation or become core when moving from Junior to Mid-level. The biggest jumps first.
} in the open competency matrix: 45 skills across 5 levels. The matrix is free for individuals and stays free.