Thank you for your interest in GitLab! It’s an exciting time to join our team. We're the world’s largest all-remote company, and we've been intentionally building our culture this way from the start. With more than 1,300 team members in 65+ countries, GitLab is a place where you can contribute from almost anywhere. We are an ambitious, productive team that embraces a set of shared ​values​ in everything we do.  


Current Technical Writing Opportunities:


To be considered for our current or future opportunities, please submit your information below. By submitting your information you are not applying to a job, you are simply joining our talent community and will only be contacted should there be a match now or in the future. You can learn more about our recruiting model on our Jobs FAQ page.


All of our positions are 100% remote.


A brief overview of the GitLab User Experience (UX) department:

The GitLab UX Department is a 60+ person globally distributed team that consists of Product Design, UX Research, and Technical Writing

Our goal is to make our product easy to use, supportive of contributions from the wider GitLab community, and built for a diverse, global community. We want GitLab to be the easiest and most delightful product in its class.

Blogs about working in UX @ GitLab:


Technical Writing

Susan Tacker, Senior Manager, Technical Writing

At GitLab, Technical Writers continuously develop the GitLab product documentation to meet the evolving needs of all users and administrators, collaborating with Product Managers, Engineers, and other UX team members.

Documentation educates readers about features and best practices, and enables them to efficiently configure, use, and troubleshoot GitLab. The Technical Writing team manages the docs.gitlab.com site and related processes and tooling.

What you can expect in a Technical Writing role at GitLab:

  • Continuously improve GitLab’s documentation content in collaboration with Engineers, Product Managers, and others.
    • Review and edit doc plans and content for all new and enhanced features.
    • Through the use and testing of GitLab and its documentation, as well as SME interviews, proactively identify information needs and content opportunities. Develop new content to meet those needs and plan further work for the technical writing team.
    • Plan and complete large content initiatives such as section reviews and overhauls.
    • Help developers and other members of the community who have documentation-related questions.
    • Help review and triage incoming suggestions, corrections, and other content from the community.
    • Act as a primary content reviewer for other technical writers.
  • Continuously improve GitLab’s documentation site features and user experience in collaboration with Engineers and other Technical Writers. This can include the documentation site’s design, search, build process, feedback methods, SEO, visitor analytics, versioning, and other technical components.
    • Plan and lead documentation site feature enhancement initiatives.
    • Work with UX to identify contextual content/documentation opportunities in the product.
    • Produce reports on documentation usage and metadata.
  • Contribute to the improvement of team process and style, as well as cross-functional efforts.
    • Act as a reviewer of release blog posts and contributor to GitLab’s Handbook.
    • Make it easy for contributors from the community—internal and external—to submit quality documentation.
    • Contribute to the documentation Style Guide and documentation process guides.
    • Collaborate and improve upon collaborative processes with others including product managers, Support, Marketing, Engineering, and the wider GitLab community.
  • Practice Leadership and collaboration.
    • Mentor newly hired technical writers.
    • Lead projects when pairing with other technical writers.
    • Plan new cross-functional efforts.
    • Represent the team at hackathons or other community endeavors.
    • Plan and lead a portion of the team’s process-improvement initiatives.
    • Organize and prioritize portions of the team's work backlogs. 

You should submit your information to the talent community if:

  • You have extensive experience planning, writing, and managing software documentation.
  • You have excellent skills in writing, editing, research, and planning.
  • You understand what makes documentation clear and effective.
  • You have great teaching skills that translate into amazing written work.
  • You have experience establishing processes used by teams across an organization in support of documentation.
  • You have experience planning and leading major initiatives such as the launch of new documentation content, large-scale documentation reviews and overhauls, cross-functional initiatives, etc.
  • You have experience using data and evidence-based decision making.
  • You have experience with a docs-as-code workflow, a markup language such as Markdown, AsciiDoc, or reStructuredText, and at least one programming language (though this does not need to be from a professional context).
  • You have experience using Git on the Linux or Mac command line and developer tools and workflows.
  • Share our values, and work in accordance with those values.
  • You are highly organized; able to triage and prioritize numerous issues and projects.
  • You are able to succeed in a remote, globally distributed work environment.

Technical Writing typically follows this hiring process


To be considered for our current or future opportunities, please submit your information below. Please note that by submitting your information you are not applying to a job, you are simply joining our talent community and will only be contacted should there be a match now or in the future. You can learn more about our recruiting model on our Jobs FAQ page.


 

Apply for this Job

* Required