Technical Documentation — P2

TECHNI.TECHNICACFA5.P2

P2P2 — Developing Professionalhigh0.90approvedglobalv1

Plans, authors, edits, and maintains product and developer documentation — user guides, API references, system manuals, knowledge bases, and regulated/compliance content. Distinct from UX content design (which owns in-product copy) and from marketing/content writing (which owns persuasive demand-gen content): this focus owns the accuracy, findability, structure, and governance of technical content, including structured authoring (DITA/XML), docs-as-code workflows, information architecture, and the make-or-buy judgment of what belongs in docs versus product UI or support.

♡ SaveMy saved →My collections →

Level

P2 · P2 — Developing Professional · 1–3 yrs

Function · Focus

Technical Documentation · Technical Documentation

Market pay (median)

$78k ($61k–$100k)

Pay basis

function-anchored · wide bars

Focus — Technical Documentation

Responsibilities by level

What this person actually does at each level on the professional track — escalating scope, not one generic blob. Your level is highlighted.

Updates existing documents and formats content for clarity and consistency under the direction of senior writers.
Owns small, well-bounded surfaces such as a single guide, a feature page, or a section of the knowledge base.
Drafts user guides, knowledge base articles, and internal process documentation from source material provided by SMEs and senior writers.
Learns the team's authoring tools (e.g., MadCap Flare, Markdown, Confluence) and applies the existing style guide and templates to assigned tasks.
Collaborates closely with senior writers and technical staff to gather source information and verify factual accuracy of edits.

P2this profile

Creates and maintains product documentation, technical manuals, and user-facing content with minimal supervision across an assigned documentation set.
Runs documentation projects end-to-end — writes, edits, coordinates SME interviews, and manages the review cycle for a defined feature area.
Makes day-to-day judgment calls about what belongs in docs versus product UI or support, escalating ambiguous cases to senior writers.
Applies single-sourcing and structured authoring conventions (DITA topics, content reuse) within an established framework.
Participates in project and release planning meetings and begins mentoring junior writers on tooling and style basics.

Plans, writes, edits, and maintains documentation independently across multiple releases for a product or product area, managing scope and milestones.
Takes on complex documentation projects such as API guides and developer tutorials, reconciling OpenAPI specs with hand-written content.
Implements documentation strategies that measurably improve user experience (improved findability, reduced support tickets) within a cross-functional team.
Coordinates with engineering, product, and support to gather and validate technical information, networking with senior professionals to resolve gaps.
Contributes to documentation standards and templates, and mentors junior writers on structured authoring and review workflows.

Leads major cross-functional documentation initiatives, producing high-impact deliverables such as API reference suites, system manuals, and compliance documentation.
Develops and owns documentation standards, templates, terminology, and review workflows that raise quality across the team.
Partners with UX and engineering earlier in the lifecycle to improve information architecture so content stays findable as the product grows.
Selects authoring methods and tooling for complex projects (docs-as-code pipelines, structured authoring, localization workflows) and drives their adoption.
Peer-reviews other writers' work, mentors junior and mid-level writers, and may lead a documentation project team.

Leads documentation strategy aligned with business objectives across a product line, acting independently on broad and ambiguous initiatives.
Owns documentation deliverables for complex or regulated systems and participates in audits and regulatory documentation efforts.
Serves as the primary documentation point of contact between product and engineering, building influential networks across functions.
Evaluates new tools and authoring technologies, shapes review workflows and quality benchmarks, and reports documentation risks to leadership.
Drives the team's approach to emerging areas (e.g., AI in documentation) and supervises writers on special, high-stakes assignments.

Oversees the documentation function for a company or product line, setting the standards, processes, content standards, and quality benchmark.
Leads planning and execution of documentation across multiple teams or products, identifying and driving cross-stage initiatives that improve deliverables and processes.
Acts as an effective thought partner with management on technical and product decisions, influencing roadmap and architecture choices through a documentation lens.
Shapes workflow governance — tooling decisions, structured authoring strategy, single-sourcing and localization architecture — across the organization.
Defines and guides the company's approach to AI in documentation, mentors and reviews the work of writers and contractors, and is the recognized authority on documentation quality.

Level guidelines

The universal leveling rubric applied to this function — how scope, complexity, collaboration, and experience step up across levels.

Level	Knowledge & Application	Complexity & Problem Solving	Collaboration & Interaction	Typical Degree & Years
P1	Applies basic technical writing principles and learns the team's authoring tools and style guide. Knowledge is foundational; relies on senior writers and SMEs for context and accuracy.	Handles routine editing and formatting tasks with standard answers and clear precedent. Problems encountered are well-defined with established solutions.	Works within stable internal relationships, primarily with senior writers and immediate technical staff to gather source material and verify edits.	0–1 years; new graduate or intern, often with a writing, communications, or technical background.
P2	Applies conventional documentation practices, single-sourcing, and structured authoring within established frameworks to a defined documentation set. Comfortable with core tooling.	Exercises judgment in familiar contexts — deciding content placement, sequencing, and review coordination — escalating genuinely ambiguous cases.	Builds productive project relationships with SMEs across releases; participates in planning meetings and begins mentoring junior writers.	2+ years with a BA, or an advanced degree with limited experience.
P3	Applies in-depth documentation craft across diverse problems — API documentation, structured authoring, IA — planning own work and selecting approaches within team standards.	Evaluates identifiable factors to solve diverse documentation problems independently, such as reconciling specs with docs and designing content for findability.	Networks with senior professionals across engineering, product, and support; coordinates project activities and mentors junior writers.	5+ years with a BA, 3+ with an MA, or PhD without experience.
P4	Brings deep expertise across authoring frameworks, docs-as-code, localization, and information architecture; sets standards and methods that have functional impact.	Performs in-depth analysis of complex variables across product surfaces — high-impact API and compliance content, IA at scale — and selects the methods used.	Coordinates across groups (UX, engineering, product), influences decisions on content scope and architecture, and may supervise or lead project teams.	8+ years, often with graduate education.
P5	Recognized expert applying strategic documentation thinking to significant, often unique problems including regulated systems and emerging tooling such as AI.	Tackles intangibles and ambiguous strategic issues with high independence — governance, risk, tooling evaluation, and quality benchmarks across a product line.	Builds influential networks; serves as the primary documentation spokesperson between product and engineering and reports risk to leadership.	12+ years with extensive technical documentation expertise.
P6	Field-shaping authority on documentation strategy, governance, and quality; defines standards and the organizational approach to structured content, single-sourcing, and AI.	Provides visionary, field-defining problem-solving across multiple teams and products with full latitude, anticipating how content scales as products evolve.	Influences company and industry direction; acts as thought partner to management and provides high-level mentorship to writers and peer professionals.	15+ years; principal-level expert often combining deep documentation leadership with broad technical fluency.

Skills

Focus-specific skills the role applies — the relevance layer beyond the occupational base.

Writing: Communicates effectively in writing as appropriate for the needs of the technical audience, producing accurate and usable documentation.
Reading comprehension: Understands written sentences and paragraphs in work-related documents such as specifications, SME notes, and source material.
Active listening: Gives full attention to SMEs and stakeholders, asks clarifying questions, and does not interrupt at inappropriate times during information-gathering.
Structured authoring: Performs topic-based authoring and content reuse using frameworks like DITA and XML, dominant in enterprise documentation environments.
Single-sourcing: Creates content once and reuses it across multiple outputs and deliverables to ensure consistency and reduce maintenance.
Docs-as-code: Authors documentation in lightweight markup using engineering workflows such as Git, pull requests, and automated quality gates.
API documentation: Writes developer-facing content including API references, guides, and tutorials, and reconciles OpenAPI specs with documentation.
Documentation architecture: Applies strategic thinking about information architecture so content stays findable and navigable as the product grows.
Content management: Applies expertise in content management systems to organize and maintain large documentation sets.
Localization and global content strategy: Adapts and manages documentation for translation and global audiences.
Version control: Uses systems like Git to track and manage changes to documentation.
Mentoring and leadership: Guides junior writers and drives adoption of standards, tools, and processes across the team.
Workflow governance: Defines and shapes review workflows, tooling decisions, and quality benchmarks across teams.
MadCap Flare: Uses this tool/technology effectively during the delivery of day-to-day tasks.
Oxygen XML Author/Editor: Uses this tool/technology effectively during the delivery of day-to-day tasks.
DITA Open Toolkit: Uses this tool/technology effectively during the delivery of day-to-day tasks.
Markdown / MDX: Uses this tool/technology effectively during the delivery of day-to-day tasks.
Confluence: Uses this tool/technology effectively during the delivery of day-to-day tasks.
Git / GitHub / GitLab: Uses this tool/technology effectively during the delivery of day-to-day tasks.
OpenAPI / Spectral: Uses this tool/technology effectively during the delivery of day-to-day tasks.
Vale / Markdown linters: Uses this tool/technology effectively during the delivery of day-to-day tasks.

Provenance

The evidence base behind this profile — every layer is sourced; quality is scored by an adversarial review panel (1–5; passes at ≥4 on the minimum dimension).

Level differentiation5.0Focus specificity5.0Concreteness5.0Factual accuracy5.0Real-world coverage4.5

8 sources

Level — P2 — Developing Professional

Early-career professional; developing skills, handles routine tasks with some independence

Scope: Defined deliverables / small features
Autonomy: General supervision; reviewed at milestones
Complexity: Some non-routine problems; applies established patterns
Impact: Own and immediate-team deliverables
Decision rights: Routine technical choices within guidance
Leadership: May guide interns
Typical experience: 1–3 yrs

Adjacent roles

Nearest roles by structural coordinates (level + taxonomy). Distance 0 → 1; each carries its 3-state match band. How coordinates work → · Compare side-by-side →

TECHNI.TECHNICACFA5.P1

Technical Documentation — P1

confident0.06

TECHNI.TECHNICACFA5.P3

Technical Documentation — P3

confident0.06

TECHNI.TECHNICACFA5.P4

Technical Documentation — P4

confident0.11

TECHNI.TECHNICACFA5.P5

Technical Documentation — P5

review0.17