Skip to content
Curriculum plan

Technical Communication & Developer Relations — Skills Plan

Planned skill map for Technical Communication & Developer Relations. The curriculum will be developed and released in stages.

21 planned skills October 2026
Dedicated track in progress. This map is a plan, not a claim that every lesson is published. Existing live learning tracks remain available while this path is developed.

Create task-based documentation, API guides, tested examples, developer tutorials, technical demos, and feedback loops for software users.

Potential roles: Technical Writer · Developer Advocate · Developer Educator · Documentation Engineer

Before you start

  • Audience analysis and clear writing
  • Basic software, API, and Git concepts
  • Research and source verification

What you’ll build

  • Document an API with working examples
  • Create a guided developer quickstart
  • Plan and deliver a technical demo with feedback

Your request helps us prioritize this track. We’ll use your email for updates about this track only. See our privacy notice.

21skills mapped
6learning stages
0published lessons

Prerequisites

PLANNED
  • Audience analysis and clear writing

    Build the Audience analysis and clear writing knowledge needed to follow the Technical Communication & Developer Relations foundations.

  • Basic software, API, and Git concepts

    Build the Basic software, API, and Git concepts knowledge needed to follow the Technical Communication & Developer Relations foundations.

  • Research and source verification

    Build the Research and source verification knowledge needed to follow the Technical Communication & Developer Relations foundations.

Foundations

PLANNED
  • Information architecture and content design

    Explain how Information architecture and content design works and where it fits in the Technical Communication & Developer Relations learning path.

  • Task-oriented documentation

    Explain how Task-oriented documentation works and where it fits in the Technical Communication & Developer Relations learning path.

  • Markdown, docs tooling, and version control

    Explain how Markdown, docs tooling, and version control works and where it fits in the Technical Communication & Developer Relations learning path.

  • Inclusive language and accessibility

    Explain how Inclusive language and accessibility works and where it fits in the Technical Communication & Developer Relations learning path.

Core Skills

PLANNED
  • API references and developer tutorials

    Use API references and developer tutorials to implement a working capability and verify its behavior in Technical Communication & Developer Relations.

  • Runnable examples and documentation testing

    Use Runnable examples and documentation testing to implement a working capability and verify its behavior in Technical Communication & Developer Relations.

  • Developer onboarding and learning content

    Use Developer onboarding and learning content to implement a working capability and verify its behavior in Technical Communication & Developer Relations.

  • Technical demos, talks, and workshops

    Use Technical demos, talks, and workshops to implement a working capability and verify its behavior in Technical Communication & Developer Relations.

Advanced / Production

PLANNED
  • Docs-as-code and review workflows

    Evaluate Docs-as-code and review workflows trade-offs against the performance, reliability, and safety needs of Technical Communication & Developer Relations systems.

  • Content measurement and searchability

    Evaluate Content measurement and searchability trade-offs against the performance, reliability, and safety needs of Technical Communication & Developer Relations systems.

  • Community programs and feedback loops

    Evaluate Community programs and feedback loops trade-offs against the performance, reliability, and safety needs of Technical Communication & Developer Relations systems.

  • Product launch communication and issue escalation

    Evaluate Product launch communication and issue escalation trade-offs against the performance, reliability, and safety needs of Technical Communication & Developer Relations systems.

Real-World Projects

PLANNED
  • Document an API with working examples

    Deliver a working outcome with Document an API with working examples, then test it against the project requirements.

  • Create a guided developer quickstart

    Deliver a working outcome with Create a guided developer quickstart, then test it against the project requirements.

  • Plan and deliver a technical demo with feedback

    Deliver a working outcome with Plan and deliver a technical demo with feedback, then test it against the project requirements.

Career / Interview Preparation

PLANNED
  • Writing and editing portfolio

    Explain your approach to Writing and editing portfolio, defend key trade-offs, and discuss what you learned.

  • Live explanation and demo practice

    Explain your approach to Live explanation and demo practice, defend key trade-offs, and discuss what you learned.

  • Community and audience strategy

    Explain your approach to Community and audience strategy, defend key trade-offs, and discuss what you learned.

← Back to all learning tracks
Share

Discussion

0

Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.

Continue with GitHub
Loading...