What a Principal } should know

Shapes corporate API strategy from a documentation and developer experience perspective. Defines how API documentation supports business goals: partner ecosystem, platform strategy, API monetization.

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.

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).

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.

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.

Shapes long-term documentation platform strategy: technology selection, roadmap development, integration with developer ecosystem. Determines investments in documentation infrastructure and custom tooling.

Shapes corporate knowledge management strategy. Determines investments in knowledge management tools and infrastructure. Builds connections between tacit and explicit knowledge, ensuring organizational learning.

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.

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.

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.