Product Manager

We're looking for product managers that can help us work on the future of developer tools. Specifically we're looking for independent people that are interested in building solutions for (very) large teams and organizations. We know there are a million things we can and want to improve about GitLab. It'll be your job to work out what we are going to do and how. We work in quite a unique way at GitLab, where lots of flexibility and independence is mixed with a high paced, pragmatic way of working. And everything we do is in the open. We recommend looking at our primer to get started.

Responsibilities

You are not responsible for

Requirements

Senior Product Manager

A Senior Product Manager is an experienced product manager that:

  1. Consistently displays the ability to ship changes in small iterations
  2. Regularly Proposes and leads new features
  3. Is able to distill proposals and requests from the community and customers to changes in GitLab
  4. Makes significant contributions to product marketing and makes sure this is up to date
  5. Shows deep understanding of their area and has a vision of where to go next
  6. Work independently and pro-actively
  7. Excites others with their work

Junior Product Manager

Junior Product Managers have the same requirements outlined above, but typically join with less experience.

Specialists

Product Manager, CI/CD Pipelines

A Product Manager, CI/CD Pipelines, helps us work on the future of developer tools, specifically, building out continuous integration (CI), continuous delivery (CD), and beyond.

We believe developers deserve an intuitive, integrated solution that covers the entire software development lifecycle. We believe running tests is just the beginning of automation. We believe deploying your code should be automated and repeatable, and most of all, easy. We believe in pushing the boundaries of best-practices, and bringing these to every developer, so that doing the right thing is also the easy, default way of working.

As Product Manager, CI/CD Pipelines, you will find the weak spots of GitLab CI and execute plans to improve them. You will have a strong understanding of CI/CD and an understanding of deployment infrastructure and container technologies.

Product Manager, Growth

Get more people to use and contribute to GitLab, mainly the Community Edition (CE). Marketing gets us awareness and downloads. Your goal is to ensure people downloading our product keep using it, invite others, and contribute back. You report to the VP of Product. This person is technically strong and able to contribute themselves (i.e. knows Rails).

As a Product Manager, Growth, you will plan and execute on improvements in GitLab related to growth, write specs and create wireframes to communicate your plans, ship improvements every month and make it possible to report on those improvements, do data analysis whenever useful, assist the rest of the team with topics related to growth, and build and expand tools related to growth (version.gitlab.com and others).

To be successful in this role, you should have a deep understanding of UX and UI. You've built web applications before in Ruby on Rails (be it personal or professional). You're pragmatic and willing to code yourself. You're able to independently find, report, and solve issues and opportunities related to growth in the product. And you're able to make wireframes and write clear, concrete product specifications.

Goals

  1. Conversion of download to 30 day active (install success * retention)
  2. Growth of existing CE installations (growth of comments measured with usage ping)
  3. Growth in the number of new people that contributed merged code

Possible improvements

  1. Auto install let's encrypt
  2. Check open to new users by default
  3. Check invite by email function
  4. Usage ping for CE
  5. Ensure installers are very simple
  6. First 60 seconds with a product
  7. Measure contributors like a SaaS funnel (activation, retention)
  8. Improve data for Usage ping EE
  9. Improve zero-states of project (hints on first action)
  10. New feature show-off / highlighting
  11. Great experience when not logged in (commenting)
  12. Great experience when not a project member (edit button works)
  13. Make it easier to configure email
  14. Make it easier to configure LDAP

You'll work with

Hiring Process

Applicants for this position can expect the hiring process to follow the order below. Please keep in mind that applicants can be declined from the position at any stage of the process. To learn more about someone who may be conducting the interview, find her/his job title on our team page.

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