Gitlab

About Gitlab

This Backend Engineer, Engineering Productivity position is 100% remote. A brief overview: ----------------- GitLab is building an open-source, single application for the entire software development lifecycle—from project planning and source code management to CI/CD, monitoring, and security. Right now, we're in a period of growth, we've more than doubled the size of the Quality department (https://about.gitlab.com/handbook/engineering/quality/) over 2019, and we've increased the number of GitLab team members from 400 to over 1100 this financial year, too. At GitLab, we live and breathe open source principles. This means our entire handbook (https://about.gitlab.com/handbook/) is online, and with a few clicks, you can find the details of future releases (https://about.gitlab.com/direction/#future-releases), check out our past releases (https://about.gitlab.com/releases/), and see an overview of the product vision (https://about.gitlab.com/direction/) you'd contribute to when working here. As a Backend Engineer, Engineering Productivity (https://about.gitlab.com/job-families/engineering/backend-engineer/) at GitLab you will be responsible for improving the productivity of internal GitLab Engineers, external contributors, and our users through shortening feedback loops and reducing cycle times for changes to GitLab. What you can expect in a Backend Engineer, Engineering Productivity role at GitLab: ----------------------------------------------------------------------------------- As part of the Engineering Productivity, you'll work on improving the product pipeline performance to provide more timely and confidence in new features for GitLab. The work you'll do will be transparent and open to the GitLab community (https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=Engineering+Productivity). You'll measure organizational productivity (https://about.gitlab.com/handbook/engineering/quality/engineering-productivity-team/#engineering-productivity-team-metrics) and experiment with changes to increase productivity. You'll aim to build scalable solutions to increase productivity of GitLab Engineers. You'll improve GitLab's usage of Review Apps (https://docs.gitlab.com/ee/development/testing_guide/review_apps.html) to validate changes to the product. You'll build automated tooling to improve the merge request workflow. You'll improve the workflow automation for issues to help product managers identify actionable issues faster. Projects you might work on as a Backend Engineer, Engineering Productivity: --------------------------------------------------------------------------- Building automated tooling to help us track key metrics such as cycle time (https://gitlab.com/gitlab-org/quality/team-tasks/issues/249) Projects that enable us to overcome bugs in our CI features (https://gitlab.com/gitlab-org/quality/team-tasks/issues/264) that impact the entire engineering department Dogfood and improve features such as Insights (https://docs.gitlab.com/ee/user/project/insights/), Review Apps (https://docs.gitlab.com/ee/ci/review_apps/) and Pipeline (https://docs.gitlab.com/ee/ci/pipelines.html) Issue and Merge Request Workflow projects such as gitlab-triage (https://gitlab.com/gitlab-org/gitlab-triage), triage-ops (https://gitlab.com/gitlab-org/quality/triage-ops), and triage-serverless (https://gitlab.com/gitlab-org/quality/triage-serverless) You should apply if: -------------------- You've got at least a few years of experience developing in Ruby or working on a Ruby on Rails application. You've got experience using Docker and container orchestration platforms such as Kubernetes. You've got development experience in object-oriented programming languages and patterns. You've worked with industry-standard CI tools like GitLab CI, Jenkins, Bamboo, or Circle CI for example. You are experienced with test automation frameworks for both front-end and back-end testing. You've got experience with Git and its command line. Our values (https://about.gitlab.com/handbook/values/) of collaboration, results, efficiency, diversity, iteration, and transparency resonate with you. You'll thrive in an environment where self-learning and self-service (https://about.gitlab.com/company/culture/all-remote/self-service/#self-service-and-self-learning-in-onboarding) is encouraged and instilled as a part of our culture. We're aware the confidence gap exists (https://www.theatlantic.com/magazine/archive/2014/05/the-confidence-gap/359815/) so we want to encourage you to apply even if you do not match all of the requirements exactly. The above list is intended to show the kinds of experience and qualities we're looking for. It is not a complete list of pre-required skills. What it's like to work here (https://about.gitlab.com/jobs/faq/#whats-it-like-to-work-at-gitlab) at GitLab: ------------------------------------------------------------------------------------------------------------------- The culture (https://about.gitlab.com/company/culture/) here at GitLab is something we're incredibly proud of. Because GitLabbers are currently located in over 67 different countries, you'll spend your time collaborating with kind, talented, and motivated colleagues from across the globe. Some of the benefits (https://about.gitlab.com/handbook/benefits/) you'll be entitled to vary by the region or country you're in. However, all GitLabbers are fully remote and receive a "no ask, must tell" paid-time-off policy, where we don't count the number of days you take off annually. You can work incredibly flexible hours, enabled by our asynchronous approach (https://about.gitlab.com/handbook/communication/) to communication. We'll also help you set up your home office environment (https://about.gitlab.com/handbook/spending-company-money/), pay for your membership to a co-working space and contribute to the travel costs (https://about.gitlab.com/handbook/incentives/#visiting-grant) associated with meeting other GitLab team members across the world. Also, every year or so, we'll invite you to our Contribute event (https://about.gitlab.com/company/culture/contribute/). Hiring Process and compensation: -------------------------------- Our hiring process for this Backend Engineer, Engineering Productivity position typically follows five stages. The details of this process and the compensation for this role can be found in our job family page. (https://about.gitlab.com/job-families/engineering/backend-engineer/)

Synonyms

Technologies (from Job Ads)

Hiring Locations (10 of 30)

Headquarters

Loading map...

Company Info

Legal Form: Inc

Company Type: Public

Company Size: 1001 - 5000

Job Ad Metrics

Job Ads found: 1717

Job Ads per Month: 35.0

Hiring Locations: 30

Data Info