Technical Writer Manager

The Technical Writer Manager is the people manager of a technical writing and documentation team, accountable for hiring, performance, growth, staffing, documentation roadmap and coverage, editorial standards, content operations, freshness, and partnerships with Product and Engineering. It is a Manager seat whose central outcome is users and developers can find accurate, task-appropriate, accessible documentation across the product lifecycle while writers have clear ownership, fair workload, growth, and a system that keeps content current instead of depending on last-minute heroics. The work concentrates on technical writing people leadership, documentation portfolio and roadmap, content coverage, editorial and information-quality standards, docs-as-code operations, freshness governance, API and developer documentation, accessibility, localization, and cross-functional launch planning. The signature strength is turning documentation from scattered author effort into an owned portfolio with capable writers, explicit coverage, measurable quality, and durable freshness responsibility. The Technical Writer Manager is not simply the strongest editor with direct reports. The role manages the people and production system that keeps technical content useful across product changes. It allocates writers to user journeys and product risk, sets roadmap and coverage decisions, establishes editorial and review standards, partners with engineering on source and API accuracy, and maintains ownership for freshness, accessibility, and localization. It must understand information architecture, developer tasks, release workflows, docs-as-code, and content analytics well enough to assess the work, but should not personally rewrite every important page or replace the Documentation Lead as the senior IC design authority. The manager is accountable for whether the team has the capacity, relationships, standards, and feedback system needed to produce and maintain the portfolio. Against Documentation Lead, this seat owns people, headcount, performance, team capacity, roadmap, prioritization, and the operating system for documentation outcomes; the neighbor owns senior-IC documentation strategy, information architecture, editorial standards, and complex content design without people or employment authority. Against Senior Technical Writer, this seat manages the writing team and portfolio through staffing, feedback, allocation, and cross-functional commitments; the neighbor owns complex individual authoring, domain depth, mentoring, and editorial contribution within assigned scope. These are reciprocal collaboration boundaries, not aliases. Every named title remains its own 1:1 role package.