Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Technical Writer

At GitLab, our team of technical writers is responsible for ensuring that the documentation for all of our products is clear, correct, comprehensive, and easy to use. We are looking for great writers with strong technical proficiencies to help our users succeed with our rapidly evolving suite of DevOps tools.

Responsibilities

  • Collaborate with GitLab engineers, who typically write the first draft of documentation for the new features they create.
  • Dive in on special projects, planning and authoring new content, and helping to develop new docs site features and processes.
  • Collaborate with others across the organization to craft new and improved content. You’ll be at the leading edge of DevOps while contributing to one of the world’s largest open-source projects and engaging with our wider community.

Requirements

  • You have:
    • Experience planning, researching, writing, and editing software documentation.
    • Excellent skills in grammar, minimalist documentation design, and effective information architecture.
    • Great teaching skills that translate into amazing written work.
    • Experience using the Linux shell, command-line Git, HTML/CSS, and/or at least one programming language (does not have to be in a professional context).
    • Experience using static site generators and managing docs as code.
    • Experience with some of the following:
      • Using or documenting DevOps tools.
      • JavaScript and front-end development.
      • Advanced programming or other technical experience.
      • Using GitLab.
      • A rapidly scaling start-up environment.
      • Remote work, especially in collaboration with others across countries and time zones.
  • You are:
    • Highly organized and able to triage and prioritize numerous issues and projects.
    • Able to succeed in a remote, globally distributed work environment.
  • You share our values, and work in accordance with those values.
  • You have experience with workflows and tooling used by engineering, operations, and product teams.

Levels

Technical Writer (Intermediate)

The Technical Writer (Intermediate) reports to the Manager, Technical Writing.

Technical Writer (Intermediate) Job Grade

The Technical Writer (Intermediate) is a grade 6.

Technical Writer (Intermediate) Responsibilities

  • Content: Create, merge, and maintain product documentation and release posts for assigned product groups. Balance priorities.
  • Structure: Ensure newly developed content uses content topic types to make product documentation easier to scan.
  • Organization: Ensure that product documentation pages in your assigned groups are well organized by using good naming and logical groupings.
  • User interface: Create or improve user interface text, such as field labels or error messages, with a focus on your assigned groups.
  • Reviews: Provide effective reviews for content created by others mainly within your assigned groups, based on relevant style guides.
  • Product knowledge: Understand the technology and features of the development groups to which you’re assigned.
  • Process: Contribute Handbook changes that help the organization evolve the culture and best practices.
  • Communication: Communicate effectively and professionally with other team members.
  • Leadership: Act as the Technical Writing lead for assigned groups.

Senior Technical Writer

The Senior Technical Writer reports to the Manager, Technical Writing.

Senior Technical Writer Job Grade

The Senior Technical Writer is a grade 7.

Senior Technical Writer Responsibilities

Extends the Technical Writer (Intermediate) responsibilities in complexity and scope.

  • Content: Efficiently create, merge, and maintain product documentation and release posts for assigned product groups. Guide improvements to merge requests. Suggest and balance priorities.
  • Structure: Implement content topic types in both new and previously created content to make product documentation easier to scan.
  • Organization: Ensure that product documentation pages are well organized in your assigned stage by using good naming and logical groupings.
  • User interface: Actively create or improve user interface text, such as field labels or error messages, with a focus on your assigned stage.
  • Reviews: Provide effective and efficient reviews for content created by others across your assigned stage, based on relevant style guides.
  • Product knowledge: Deeply understand the technology and features of the development groups to which you’re assigned, and have a general understanding of your assigned stage.
  • Process: Contribute Handbook changes that help the organization evolve the culture and best practices.
  • Communication: Communicate effectively and professionally with other team members.
  • Leadership: Act as the Technical Writing lead for assigned groups and stages.
  • Recruiting: Be available to interview potential technical writing candidates.
  • Mentoring: Mentor other technical writers and team members regarding best practices and other process knowledge.

Staff Technical Writer

The Staff Technical Writer reports to the Senior Manager, Technical Writing.

Staff Technical Writer Job Grade

The Staff Technical Writer is a grade 8.

Staff Technical Writer Responsibilities

Extends the Senior Technical Writer responsibilities in complexity and scope.

  • Content: Efficiently create and maintain product documentation and release posts for assigned product groups or stages. Guide improvements to merge requests.
  • Structure: Actively implement content topic types in both new and previously created content to make product documentation easier to scan.
  • Organization: Ensure that product documentation pages are well organized across stages by using good naming and logical groupings.
  • User interface: Create model examples of user interface text, including field labels or error messages, with a cross-stage focus. Actively improve style guide and Pajamas content related to user interface text.
  • Reviews: Model review practices that improve the quality of contributions over time. Support and guide team members to improve reviews in their groups and stages.
  • Product knowledge: Understand the technology and features of both the development stage to which you’re assigned and the end-to-end GitLab product to help improve the information architecture of the docs site.
  • Process: Actively contribute Handbook changes that help the organization evolve the culture and best practices.
  • Communication: Communicate effectively and professionally with other team members, and be a model for collaboration.
  • Leadership: Identify and lead cross-stage projects that improve the deliverables or processes of the Technical Writing team.
  • Recruiting: Be available to interview potential technical writing candidates.
  • Mentoring: Mentor other technical writers and team members about suggesting and balancing priorities, industry best practices, and other process knowledge.

Principal Technical Writer

The Principal Technical Writer reports to the Senior Manager, Technical Writing.

Principal Technical Writer Job Grade

The Principal Technical Writer is a grade 9. The Principal Technical Writer has extensive experience in a Staff-level role.

Principal Technical Writer Responsibilities

Extends the Staff Technical Writer responsibilities in complexity and scope.

  • Content: Efficiently create and maintain product documentation and release posts for assigned product groups or stages. Guide improvements to merge requests. Help set priorities at a team level.
  • Structure: Actively implement content topic types in both new and previously created content to make product documentation easier to scan.
  • Organization: Ensure that product documentation pages are well organized across stages by using good naming and logical groupings.
  • User interface: Provide expert guidance on user interface text. Actively improve style guide and Pajamas content.
  • Reviews: Foster effective review practices for team and community contributions to GitLab documentation and user interface changes.
  • Product knowledge: Deeply understand the technology and features of the development stage to which you’re assigned, and have a general understanding of the end-to-end GitLab product to help improve the information architecture of the docs site.
  • Process: Actively contribute Handbook changes that help the organization evolve the culture and best practices, and lead efforts to encourage other team members regarding contributions.
  • Communication: Communicate effectively and professionally across all product groups and stages, and be a model for collaboration with community contributors.
  • Leadership: Identify and lead cross-GitLab department projects that improve the deliverables or processes of the Technical Writing team.
  • Recruiting: Be available to interview potential technical writing candidates.
  • Mentoring: Mentor other technical writers and team members regarding best practices and other process knowledge.
  • Impact: Provide positive influence on the adoption of stages per organization through more usable documentation, with the ultimate goal being a contribution to higher ARR.

Performance Indicators

Career Ladder

For more details about the engineering career ladders, review the engineering career development handbook page.

Hiring Process

Candidates for this position can expect the hiring process to follow the order below. Please keep in mind that candidates can be declined from the position at any stage of the process.

  1. Candidates who demonstrate interest in the role will be asked to share work samples and respond to questions related to technical writing.
  2. Qualified candidates will be invited to schedule a 30 minute screening call with one of our Global Recruiters. In this call, we will discuss your experience, understand what you are looking for in a Technical Writing role, talk about your work and approach to technical writing, discuss your compensation expectations and reasons why you want to join GitLab, and answer any questions you have.
  3. If you successfully pass the screening call, you will be invited to schedule a 45-minute first interview with our Technical Writing Manager. In this interview, we will want you to talk through the approach you took in the examples of work you shared as part of your application, your experience up to now, understand what you're looking for in a technical writing position, and answer any questions you have.
  4. The next interview is with one of our Technical Writers. We’ll discuss your experience, why you’re looking to join GitLab, your domain experience, and what it's like to be a technical writer at GitLab. We’ll assess your alignment with our values, and answer any questions you have.
  5. Next, you’ll meet one of our Product Managers for a 45-minute interview. We’ll discuss your experience, why you’re looking to join GitLab, your domain experience, and what it's like to be a technical writer at GitLab. We’ll assess your alignment with our values, and answer any questions you have.
  6. Finally, you’ll meet our Senior Manager, Technical Writing. At this stage, we’ll look to understand your views on how documentation impacts user experience, your experience up to now, you'll have a discussion around technical writing maxims, and the interviewer will answer any questions you have.

Additional details about our process can be found on our hiring page.

Compensation Calculator

To find out more about the compensation for this role, please join our talent community first. Once you've joined, you'll be able to sign up here to view our compensation calculator. Be sure to use the same email address for both.

About GitLab

GitLab Inc. is a company based on the GitLab open-source project. GitLab is a community project to which over 2,200 people worldwide have contributed. We are an active participant in this community, trying to serve its needs and lead by example. We have one vision: everyone can contribute to all digital content, and our mission is to change all creative work from read-only to read-write so that everyone can contribute.

We value results, transparency, sharing, freedom, efficiency, self-learning, frugality, collaboration, directness, kindness, diversity, inclusion and belonging, boring solutions, and quirkiness. If these values match your personality, work ethic, and personal goals, we encourage you to visit our primer to learn more. Open source is our culture, our way of life, our story, and what makes us truly unique.

Top 10 reasons to work for GitLab:

  1. Work with helpful, kind, motivated, and talented people.
  2. Work remote so you have no commute and are free to travel and move.
  3. Have flexible work hours so you are there for other people and free to plan the day how you like.
  4. Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.
  5. Work on open source software so you can interact with a large community and can show your work.
  6. Work on a product you use every day: we drink our own wine.
  7. Work on a product used by lots of people that care about what you do.
  8. As a company we contribute more than we take, most of our work is released as the open source GitLab CE.
  9. Focused on results, not on long hours, so that you can have a life and don't burn out.
  10. Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.

See our culture page for more!

Work remotely from anywhere in the world. Curious to see what that looks like? Check out our remote manifesto and guides.

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license