Algorithms & Data Structures 1
▼
Understands basic data structures: arrays, lists, dictionaries for accurately describing APIs and interfaces. Knows main collections and can correctly document parameter types and return values. Uses data structure knowledge for creating clear diagrams and schemas in documentation.
Documents complex data structures in API references: nested objects, trees, dependency graphs. Creates data structure visualizations for technical guides and architectural documentation. Evaluates and describes data structure choice trade-offs in advisory documents.
Defines data model documentation standards for all organizational projects. Coordinates creation of a unified data structures knowledge base for developers and architects. Implements auto-generation of documentation from schema definitions and data models.
Shapes corporate standards for describing and visualizing data structures in technical documentation. Defines best practices for documenting complex data architectures in large distributed systems. Influences the development of automatic documentation generation from data schemas.
API Management 1
▼
Understands API documentation structure: endpoint descriptions, request parameters, response formats, error codes. Knows main tools: Swagger UI, Redoc, Postman. Can read and supplement existing API documentation.
Independently creates comprehensive API documentation based on OpenAPI/Swagger specifications. Documents authentication, rate limiting, pagination, versioning. Writes getting started guides and tutorials for API consumers.
Defines API documentation standards for the organization: templates, review processes, quality gates. Coordinates work of multiple technical writers on a large API portfolio. Implements documentation quality metrics (completeness, accuracy, freshness).
Shapes developer experience strategy through API documentation at the company level. Determines investments in developer portal, interactive docs, sandbox environments. Builds processes where API documentation is part of the Definition of Done.
Clean Code & Refactoring 1
▼
Understands basic code quality metrics and their impact on creating clear documentation. Knows clean code principles and uses them for writing quality examples in documentation. Evaluates code readability when selecting snippets for technical guides.
Analyzes code quality of documented projects to determine documentation priorities. Uses linters and static analysis to automatically check code examples in documentation. Creates coding standards guides with emphasis on self-documenting code.
Defines the relationship between code quality metrics and documentation quality at the project level. Standardizes code quality analysis tools for documentation team needs. Implements automated code-documentation consistency checks in the CI process.
Shapes corporate strategy for the relationship between code quality and documentation quality at the company level. Defines industry metrics for evaluating technical documentation quality through code analysis. Researches AI-driven approaches to automatic documentation freshness maintenance.
Collaboration Tools 1
▼
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.
Fully works in docs-as-code workflow: branch, write, PR, review, merge, deploy. Configures CI/CD for automated documentation building and publishing. Uses linting (markdownlint, vale) for text quality control.
Defines organizational docs-as-code standard: workflows, branching strategy for docs, review processes, quality metrics. Coordinates team migration to docs-as-code approach. Creates contribution guidelines for developers.
Shapes documentation-as-code strategy at the corporate level. Defines how docs-as-code integrates with SDLC, developer experience, and knowledge management. Ensures scalability of the approach as the organization grows.
Concurrency & Parallelism 1
▼
Understands async/await and callback concepts for correctly describing asynchronous APIs in documentation. Knows main asynchronous programming patterns and can document Promise-based APIs. Creates simple async code examples for getting started guides.
Documents complex asynchronous APIs: streaming, WebSocket, event-driven interfaces with practical examples. Creates error handling guides for asynchronous code for developers. Describes concurrency and parallel execution patterns in architectural documentation.
Defines standards for describing asynchronous patterns and concurrency across all organizational documentation. Coordinates a unified approach to documenting event-driven and stream-based APIs across teams. Implements automatic async code example generation from OpenAPI specifications.
Shapes industry standards for documenting asynchronous APIs and event-driven systems. Publishes research on the effectiveness of different concurrency description approaches in documentation. Defines best practices for visualizing asynchronous data flows in technical documentation.
Docs-as-Code 3
▼
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.
Creates complex technical diagrams: C4 model (all 4 levels), data flow diagrams, state machines, ER diagrams. Uses diagrams-as-code tools (Mermaid, PlantUML). Maintains visual consistency and diagram readability.
Defines organizational standards for technical information visualization: notations, tools, color schemes, templates. Coordinates creation of unified system landscape diagrams combining knowledge from different teams. Trains on visualization techniques.
Shapes technical knowledge visualization strategy at the company level. Defines tools and approaches for diagramming automation. Ensures visual documentation serves as living documentation reflecting the actual state of systems.
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.
Confidently works with 2-3 docs-as-code frameworks. Configures navigation, search, versioning, custom components. Uses MDX/RST extensions, plugins for diagrams, code highlighting. Integrates docs build into CI/CD.
Defines docs-as-code strategy and standards for the organization. Selects the toolchain, defines docs platform architecture. Coordinates migration from legacy wiki (Confluence) to docs-as-code approach. Trains teams on tools.
Shapes long-term documentation platform strategy: technology selection, roadmap development, integration with developer ecosystem. Determines investments in documentation infrastructure and custom tooling.
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.
Regularly writes technical posts: deep-dive articles, comparison articles, best practices guides. Optimizes content for SEO and developer audience. Works with CMS (WordPress, Ghost, dev.to). Creates content plans for engineering blogs.
Defines content strategy for the organization's technical content. Coordinates authors from different teams. Implements editorial process: ideation, writing, review, publication, distribution. Measures content impact.
Shapes technical content strategy at the company level. Defines how engineering blog supports business goals: developer adoption, hiring, thought leadership, partner ecosystem. Manages content budget and team.
Kubernetes & Orchestration 1
▼
Understands basic Kubernetes concepts and can document simple deployment configurations. Knows core K8s objects: Pod, Service, Deployment for describing infrastructure in guides. Creates getting started documentation for working with clusters for developers.
Documents project Kubernetes architecture: deployments, services, ingress, ConfigMaps with diagrams. Creates deployment and application management guides in K8s for the DevOps team. Describes troubleshooting procedures and common issues in operational runbooks.
Defines corporate standards for documenting Kubernetes infrastructure across all projects. Coordinates creation of a unified K8s knowledge base with runbooks and troubleshooting guides. Implements documentation-as-code approach to infrastructure documentation management.
Shapes industry standards for documenting Kubernetes infrastructure and cloud-native architectures. Publishes research on infrastructure documentation effectiveness for operational reliability. Influences the development of automatic K8s documentation generation tools.
OOP & Design Patterns 1
▼
Knows basic design patterns and can correctly use their names in technical documentation. Understands the purpose of main patterns for accurately describing architectural decisions in API references. Creates simple pattern diagrams for architecture visualization in guides.
Documents design pattern usage in product architecture with examples and rationale. Creates architectural guides describing pattern choices and their trade-offs for developers. Develops a project pattern catalog with code examples and usage recommendations.
Defines standards for documenting architectural decisions and patterns for all company projects. Coordinates creation of a corporate pattern library with descriptions, examples, and decision criteria. Implements Architecture Decision Records as a standard documentation practice.
Shapes industry standards for documenting architectural patterns and decisions. Publishes research on the effectiveness of different architecture documentation formats. Influences the development of automatic architecture documentation generation tools.
Relational Databases 1
▼
Understands basic PostgreSQL concepts for documentation: documenting database schemas and data models, writing query examples for API documentation, understanding table relationships for data flow diagrams. Follows team conventions for database documentation standards.
Documents project database schemas: tables, relationships, indexes, migrations with ER diagrams. Creates PostgreSQL guides for developers: best practices, conventions, common queries. Describes backup, restore, and maintenance processes in operational documentation.
Defines corporate database documentation standards for all organizational projects. Coordinates creation of a unified database knowledge base with automatic updates from schema changes. Implements documentation-driven database management with versioned schema docs.
Shapes industry standards for documenting databases and data architecture. Publishes research on the effectiveness of different database documentation approaches. Influences the development of automatic database documentation generation from PostgreSQL metadata.
REST API 1
▼
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.
Creates comprehensive REST API documentation in OpenAPI/Swagger: paths, schemas, security, examples. Documents API design conventions: naming, pagination, filtering, error format. Configures Swagger UI / Redoc for interactive documentation.
Defines organizational REST API design and documentation standards. Coordinates API governance: design reviews, breaking change detection, deprecation policy. Ensures API design consistency through documented standards.
Shapes corporate API strategy from a documentation and developer experience perspective. Defines how API documentation supports business goals: partner ecosystem, platform strategy, API monetization.
Technical Documentation 3
▼
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.
Writes comprehensive API guides: quickstart, authentication flow, error handling, use cases. Creates code samples in multiple languages (curl, Python, JavaScript, Go). Maintains terminology and style consistency across all API docs sections.
Builds a content strategy system for API documentation at the product level: content types, audience mapping, content lifecycle. Coordinates work between writers and developers. Implements user feedback loops for continuous documentation improvement.
Defines technical writing standards for API documentation at the company scale. Shapes approaches to multi-audience documentation (internal devs, partners, public). Researches and implements best practices from leading developer portals (Stripe, Twilio, GitHub).
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.
Creates comprehensive architecture documentation with architects: system context, container diagrams, component diagrams (C4). Documents data flows, external system integrations, deployment topology. Keeps documentation up to date.
Defines architecture documentation standards for the organization: required artifacts, detail levels, review process. Coordinates architecture documentation across teams, ensuring a unified system landscape view.
Shapes the company's architectural knowledge strategy: unified architecture knowledge base, enterprise architecture integration, governance processes. Defines how architecture documentation supports strategic technical decision-making.
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.
Independently creates runbooks for production systems: deployment procedures, incident response, disaster recovery. Ensures step-by-step clarity and unambiguity of instructions. Conducts dry-run testing of runbooks with the operations team.
Defines runbook standards for the entire organization. Builds a culture of operational documentation. Coordinates runbook coverage: every production service has a complete set of runbooks. Conducts runbook reviews.
Shapes operational documentation strategy at the corporate level. Defines how runbooks integrate with SRE practices, incident management, and organizational resilience. Ensures knowledge transfer during incidents.
User Documentation 2
▼
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.
Designs knowledge base information architecture: taxonomy, navigation, search optimization. Creates content governance: templates, naming conventions, review processes. Ensures content freshness through scheduled reviews.
Defines knowledge management strategy for the organization. Selects tools, standardizes processes, trains authors. Ensures knowledge is not lost during employee turnover through structured knowledge capture.
Shapes corporate knowledge management strategy. Determines investments in knowledge management tools and infrastructure. Builds connections between tacit and explicit knowledge, ensuring organizational learning.
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.
Creates comprehensive user documentation: information architecture, content hierarchy, cross-references. Writes for different audiences (beginners, advanced users, admins). Uses user feedback to improve documentation.
Defines user documentation standards for the organization. Coordinates localization into multiple languages. Establishes quality and effectiveness metrics. Builds feedback loops with product and support teams.
Shapes customer-facing documentation strategy at the company level. Determines investments in documentation tools and team. Ensures documentation supports product adoption, customer success, and self-service support.