As a Technical Writer at GitLab, you’ll collaborate with Engineers, who typically write the first draft of docs for the new features they create. You’ll dive in on special projects, planning and authoring new content and helping craft new doc site features and processes. You’ll collaborate with others across the organization to help them contribute to the documentation. You’ll be at the leading edge of DevSecOps while contributing to one of the world’s largest open-source projects and engaging with our wider community.

Have a read through this (or, some of - there's a lot!) to learn all you like about Technical Writing at GitLab.

What you’ll do

Continuously improve GitLab documentation content in collaboration with engineers, product managers, and others.
Work on Quarterly OKRs that focus on making our docs site a world-class experience, such as rewriting our existing documentation to align with concept, task, reference, and troubleshooting (CTRT) topic types.
Peer review other writers' work.
Continuously improve team processes and style guides, as well as cross-functional efforts, such as the GitLab Handbook.
Take part in company-wide events such as reviewing merge requests for Hackathons.

What you’ll bring

Must have demonstrated experience writing software documentation in a docs-as-code approach (this is a hard requirement)
Hands on experience with Git
Experience using AI tools in technical writing workflows
Experience working with CI/CD
Exemplary writing and editing skills
Remote development experience
Experience working in a highly collaborative environment

About the team

Thanks to our Transparency value, you can see what we are working on in our Documentation Roadmap epic. You can also listen to Technical Writing team members talking about what it’s like to be a Technical Writer at GitLab in this video.

Technical Writer role discussion