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

Engineering Management - Quality

Quality Management Roles at GitLab

At GitLab Quality is every Engineer's responsibility and the output of the Quality department is instrumental to GitLab’s success.

Engineering Managers in the Quality department are motivated and experienced leaders who grow our test automation efforts across the entire GitLab ecosystem. They demonstrate a passion for high quality software, strong Engineering principles and methodical problem solving skills.

They own the delivery of test automation tools and strategy and are always looking to improve Engineering productivity. They also coordinate across departments and teams to accomplish collaborative goals.

Quality Engineering at GitLab spans both Software Engineers in Test and Engineering Productivity. Engineering Productivity is a new branch in career evolution of Quality Engineering.

  • https://testing.googleblog.com/2016/03/from-qa-to-engineering-productivity.html
  • https://saucelabs.com/blog/qa-is-not-enough-you-need-to-engineer-productivity

Manager, Quality Engineering

Job Grade 

The Manager, Quality Engineering is a grade 8.

Responsibilities

  • Help define the team's road map and author project plans to deliver against that roadmap.
  • Draft team's quarterly OKR and manage the team's priorities.
  • Drive improvements to test framework architecture and test coverage.
  • Work across engineering to inject testing earlier into the software development process.
  • Drive adoption of best practices in code health, testing, testability and maintainability (clean code, test pyramid).
  • Track test gaps, quality, and productivity metrics. Work with other engineering teams to improve gaps from this data.
  • Recommend improvements into overall best practices, design, testability and quality and productivity.
  • Recruit Engineers, grow the team and stay in step with the hiring plan.
  • Help engineers grow their skills and experience.
  • Hold regular 1:1's with all members of their team.
  • Create a sense of psychological safety on their team.
  • Excellent written and verbal communication skills.
  • Give clear, timely, and actionable feedback.
  • Strong sense of ownership, urgency, and drive.

Requirements

  • 8+ years of experience in the Quality Engineering/Engineering Productivity field.
  • 2+ years of experience managing a team of Software Engineers in Test or Engineering Productivity Engineers.
  • Strong experience developing in Ruby
  • Strong experience using Git
  • Strong experience with UI & API test automation tools, particularly in Ruby stack (Capybara, Watir, Selenium and etc.).
  • Experience working with Docker containers
  • Experience with AWS or Kubernetes
  • Experience with Continuous Integration systems (e.g., Jenkins, Travis, GitLab)
  • Experience defining high-level test automation strategy based on DevOps industry's best practices.
  • Experience driving organizational change with cross-functional stakeholders.
  • Enterprise software company experience.
  • Computer science education or equivalent experience.
  • Passionate about open source, developer tools, and shipping high-quality software.
  • Collaborative team spirit with great communication skills
  • You share our values, and work in accordance with those values.
  • Leadership at GitLab
  • Ability to use GitLab

Interview 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. As a result an interview can be canceled at any time even if the interviews are very close (e.g. a few hours apart).

  • A short questionnaire from our Recruiting team
  • 30 minute Screening call with a recruiter
  • 1 hour interview with the Director of Quality (manager)
  • 1 hour technical Interview with a Senior or Staff Engineer from the Quality Engineering department.
  • 1 hour interview with a Senior or Staff Engineer (report)
  • 1 hour interview with Manager, Quality Engineering (peer)
  • 45 minute interview with VP of Engineering

Director, Quality Engineering

The Director, Quality Engineering role extends the Manager, Quality Engineering role.

Job Grade 

The Director, Quality Engineering is a grade 10.

Responsibilities

  • Define and own all of GitLab's Quality Engineering efforts.
  • Define the Quality Engineering sub-department's fiscal year Direction (in handbook).
  • Define plans and quarterly OKRs to execute against key objectives and roadmap. Align efforts strategically across R&D.
  • Drive improvements to KPIs and PIs that is in Quality Engineering's line-of-work and job-family.
  • Hire world class Engineering Managers and Software Engineers in Test (SETs) for the Quality Engineering sub-department.
  • Publish and socialize the progress of the Quality Engineering sub-department.
  • Drive retrospective and improvements that impacts Quality Engineering.
  • Manage the sub-department’s priorities and define prioritization guidelines for teams in Quality Engineering.
  • Excellent written and verbal communication skills. Able to convey bottom-line messages to executives at C & VP level.
  • Hold regular skip-level 1:1's with all Software Engineer in Tests (SETs)
  • Help the teams in Quality Engineering grow their skills and experience, ensure that they are happy and productive.
  • Interface with GitLab customers to address Functional and Performance test gaps.
  • Research and advice team on new technology and tools in the Quality Engineering space.
  • Occasionally contributes to the company blog.
  • Occasionally pepresent the company publicly at conferences.

Requirements

  • This position does not require extensive Ruby development experience but the candidate should be very familiar with industry standard libraries (test tooling, orchestration, performance, and etc) and able to provide feedback on these topics.
  • Experience leading Quality focused SLA driven metrics across the Engineering organization (time to resolve bugs, time to merge code, and etc).
  • Experience presenting at conferences and meet-ups in the Quality Engineering space.
  • Proven track record of shipping multiple iterations of an Enterprise Product.
  • You share our values, and work in accordance with those values.

VP of Quality

The VP of Quality role extends the Director, Quality Engineering role.

Job Grade 

The VP of Quality is a grade 12.

Responsibilities

  • Define and own all of GitLab's Quality Engineering, Engineering Productivity, Engineering Analytics, and Engineering Open Source efforts.
  • Drive the Quality Department's roadmap and quarterly OKRs.
  • Set an ambitious vision for the department, product, and company.
  • Manage the department's budget.
  • Hire world class leaders for the Quality department.
  • Ensure that the department recruiting efforts stay in step with the product roadmap and company hiring plan
  • Track, publish and socialize the progress of the department.
  • Drive improvements and process that impacts Quality.
  • Manage the department’s priorities, set guidelines for Quality sub-departments and teams and align them strategically across all of Engineering.
  • Work across the company to define and implement mechanisms to bake in Quality and testing earlier in the software development process.
  • Work across the company to improve the efficiency and productivity of community contributions.
  • Work across Engineering to improve the Division's Data Analytics capabilities.
  • Excellent written and verbal communication skills. Able to convey bottom-line messages to executives at C & VP level.
  • Hold regular skip-level 1:1's with all members of their team.
  • Help the teams in the Quality Department grow their skills and experience, ensure that they are happy and productive.
  • Interface with GitLab customers to address Quality and Performance gaps.
  • Research and advice team on new technology and tools in the Quality space.
  • Represent Engineering open-source software efforts and community out-reach.
  • Represent the company publicly at conferences.

Requirements

  • This position does not require extensive Ruby development experience but the candidate should be very familiar with industry standard libraries (test tooling, orchestration, performance, and etc) and able to provide feedback on these topics.
  • Experience driving the adoption of the DevOps across the Engineering organization (test pyramid, shifting left, and etc).
  • Experience leading Quality focused SLA driven metrics across the Engineering organization (time to resolve bugs, time to merge code, and etc).
  • Experience presenting at conferences and meet-ups in the Quality Engineering space.
  • Proven track record of shipping multiple iterations of an Enterprise Product.
  • You share our values, and work in accordance with those values.

Performance Indicators

Quality Engineering Management has the following job-family performance indicators.

Career Ladder

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

Compensation Calculator

To find out more about the compensation for this role, please apply to a role first. Once selected for a screening call, 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. [Mission](/company/mission/): Everyone can contribute 1. [Results](/handbook/values/#results): [Fast growth](/is-it-any-good/), [ambitious vision](/direction/#vision) 1. [Flexible Work Hours](/company/culture/all-remote/people/#those-who-value-flexibility-and-autonomy) so you are there for other people and free to plan 1. [Transparency](/handbook/values/#transparency): [over 2,000 webpages in GitLab handbook](/handbook/about/#count-handbook-pages), [GitLab Unfiltered](https://www.youtube.com/gitlab-unfiltered) 1. [Iteration](/handbook/values/#iteration): [empower people to be effective](/handbook/values/#collaboration), [Merge Request rate](/k/engineering/metrics/#merge-request-rate), [everyone using the product](/handbook/using-gitlab-at-gitlab/#introverts-of-gitlab), [DRI](/handbook/people-group/directly-responsible-individuals/), have an impact 1. [Diversity, Inclusion & Belonging](/handbook/values/#diversity-inclusion): [high percentage of women](/handbook/people-group/people-success-performance-indicators/#diversity---women-at-gitlab), [Team Member Resource Groups](/company/culture/inclusion/erg-guide/#definition-of-the-tmg---team-member-groups), [other initiatives](/company/culture/inclusion/#what-we-are-doing-with-diversity-inclusion--belonging) 1. [Collaboration](/handbook/values/#collaboration): [kindness](/handbook/values/#kindness), [saying thanks](/handbook/values/#say-thanks), [intentionally organize informal communication](/company/culture/all-remote/informal-communication/), [no ego](/handbook/values/#no-ego) 1. [Compensation](/handbook/total-rewards/compensation/#gitlabs-compensation-principles): [pay at or above the 50th percentile](/handbook/total-rewards/compensation/#competitive-rate), [stock options](/handbook/stock-options/), [office equipment](/handbook/finance/expenses/#-office-equipment-and-supplies) 1. [Work/Life Harmony](/company/culture/all-remote/people/#worklife-harmony): [don't compete on hours worked](/handbook/values/#measure-results-not-hours), [flexible workday](/company/culture/all-remote/guide/#non-linear-workday), [Friends and Family days](/company/family-and-friends-day/) 1. [Remote Done Right](/handbook/marketing/corporate-marketing/all-remote/): [all remote](/handbook/marketing/corporate-marketing/all-remote/#all-remote-flywheel), [prolific inventor of best practices](/handbook/marketing/corporate-marketing/all-remote/#vision)

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