GitLab's DevOps platform empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the world’s largest all-remote companies with 1,400+ team members and values that guide a culture where people embrace the belief that everyone can contribute .
Gitlab is looking for a Frontend Engineer for the Release stage , which is part of GitLab's CI/CD product . In this role you will develop frontend features in the product areas of Continuous Delivery and Release Orchestration. Visit our direction page for more information.
The Release group is a combined group which means that all the engineers, Frontend and Backend, report to a single Fullstack Manager, Engineering. The intention of using this model is to increase efficiency and drive results by building a process that supports the whole group's effort towards our goals. Primarily, this means that all engineers participate in conversations in the group and contribute broadly to group process iteration.
Responsibilities
You should apply if you bring:
You'll Stand Out If You Bring
Frontend Engineer Performance Indicators
Frontend Engineers have the following job-family performance indicators.
Also, we know it’s tough, but please try to avoid the confidence gap . You don’t have to match all the listed requirements exactly to be considered for this role.
Our hiring process for this position typically follows four stages. The details of this process and our leveling structure can be found on our job family page .
Country Hiring Guidelines
Please visit our Country Hiring Guidelines page to see where we can hire.
Remote-Global
Country Hiring Guidelines
GitLab hires new team members in countries around the world. All of our roles are remote, however some roles may carry specific location-based eligibility requirements. Our Talent Acquisition team can help answer any questions about location after starting the recruiting process.
Your Privacy
For information about our privacy practices in the recruitment process, please visit our Recruitment Privacy Policy page.