Technical Writer

Impact:

• The documentation you maintain and improve has a daily, visible effect on how people work — this is not documentation that sits on a shelf never to be read.
• An internal AI assistant uses the Handbook as its knowledge base, so the quality and structure of what you write directly determines how well the whole company can find answers.
• Document new products from day one, setting the standard before complexity accumulates.

Ownership:

• Run documentation migration projects end-to-end: scope what needs to move (and improve), get buy-in from the team that owns it, and deliver it — from operations documentation to people documentation and beyond.
• Choose your work based on impact. You decide when to raise the bar and when documentation is finished.

Influence:

• Shape how new departments adopt the Handbook. Work with teams that have never used Git, explain why their knowledge belongs in the Handbook, and either run the migration for them or support them doing it themselves.
• Mentor another technical writer — raise their standard by reviewing their work, sharing approaches, and role modelling how to run projects independently.