Выберите текущую позицию
Укажите роль и уровень — система покажет путь развития, навыки и gap-анализ.
Путь развития
Junior
0-2 years
Ответственность: Completing tasks under the guidance of senior colleagues. Learning the codebase, standards, and team processes. Writing code to spec, fixing simple bugs, writing tests.
Ключевые навыки:
Middle
2-5 years
Ответственность: Independently developing features from decomposition to deployment. Participating in code review. Optimizing performance. Mentoring junior developers. Taking part in architecture discussions.
Ключевые навыки:
Senior
5-8 years
Ответственность: Designing the architecture of components and services. Solving complex technical problems. Managing technical debt. Code review as a quality gatekeeper. Mentoring middle developers. Choosing technologies for new tasks.
Ключевые навыки:
Lead / Staff
7-12 years
Ответственность: Technical leadership of a team or area. Designing system architecture. Coordinating with other teams. Establishing standards and best practices. Participating in hiring. Planning the technical roadmap.
Ключевые навыки:
Principal
10+ years
Ответственность: Technical strategy at the company or domain level. Cross-organizational influence. Solving systemic business problems through technology. Mentoring lead engineers. Publicly representing the company.
Ключевые навыки:
Gap-анализ: навыки для развития
Для перехода на следующий уровень необходимо развить:
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.
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.
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.
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.
Designs knowledge base information architecture: taxonomy, navigation, search optimization. Creates content governance: templates, naming conventions, review processes. Ensures content freshness through scheduled reviews.
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.
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.
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.
Creates comprehensive user documentation: information architecture, content hierarchy, cross-references. Writes for different audiences (beginners, advanced users, admins). Uses user feedback to improve documentation.
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.