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

Engineering Management - Quality

Quality Engineering 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

Quality Engineering Manager

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 a Quality Engineering Manager (peer)
  • 45 minute interview with VP of Engineering

Director of Quality Engineering

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

Responsibilities

  • Define and own all of GitLab's Quality Engineering, Test Automation, and Engineering Productivity.
  • Drive the department's roadmap and quarterly OKRs.
  • Set an ambitious vision for the department, product, and company.
  • Manage the department's budget.
  • Hire world class Engineering Managers for the Quality department.
  • Ensure that the department recruiting efforts stay in step with the product roadmap and company hiring plan
  • Manage multiple teams and projects (Quality Engineering / Engineering Productivity).
  • 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 Engineering 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.
  • Exquisite 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 Quality 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 Engineering space.
  • Represent the company publicly at conferences.

Requirements

  • 12+ years of experience in the Quality Engineering/Engineering Productivity field.
  • 2+ years of experience managing multiple teams of Software Engineers in Test or Engineering Productivity Engineers.
  • 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.

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 technical Interview with a Senior or Staff Engineer from the Quality Engineering department.
  • 1 hour interview with a Quality Engineering Manager (report)
  • 1 hour interview with a Staff Engineer (report)
  • 45 minute interview with an Engineering Director (peer)
  • 45 minute interview with VP of Engineering
  • (Optional) 30 minute interview with CEO

As always, the interviews and screening call will be conducted via a video call. See more details about our hiring process on the hiring handbook.

Performance Indicators

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

Compensation

Components

Compensation at GitLab consists of:

  1. Base salary
  2. Options
  3. Bonus in some functions
  4. Discretionary bonus
  5. Retirement contributions in eligible regions
  6. Pay for equipment
  7. Remote work
  8. Unlimited time off
  9. Benefits

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