Technical Documentation
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.
6 leveled profiles. Pick a level to see the full profile.
Individual contributor
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.
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.
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.
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.
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.
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.