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

Frontend Engineer

Frontend Engineering Roles at GitLab

Frontend Engineers at GitLab work on our product. This includes both the open source version of GitLab, the enterprise editions, and the service as well. They work with peers on teams dedicated to areas of the product. They work together with product managers, designers, and backend engineers to solve common goals.

Unless otherwise specified, all Frontend Engineering roles at GitLab share the following requirements and responsibilities:


Nice to have:


Frontend Engineer Performance Indicators

Frontend Engineers have the following job-family performance indicators.


Read more about levels at GitLab here.

Junior Frontend Engineer

Junior Frontend Engineers, while sharing the same requirements and responsibilities outlined above, typically join with less or alternate experience than typical Frontend Engineers.

Intermediate Frontend Engineer

Intermediate Frontend Engineers are expected to meet the requirements and execute the responsibilities with minimal assistance.

Senior Frontend Engineer

The Senior Frontend Engineer role extends the Frontend Engineer role.


A Senior Frontend Engineer may want to pursue the engineering management track at this point. See Engineering Career Development for more detail.

Note: Staff and above positions at GitLab are more of a role than just a "level". We prefer to bring people in as Senior and let the team elevate them to Staff due to an outstanding work history within GitLab.

Staff Frontend Engineer

The Staff Frontend Engineer role extends the Senior Frontend Engineer role.


Distinguished Frontend Engineer

The Distinguished Frontend Engineer role extends the Staff Frontend Engineer role.

Frontend Engineering Fellow

The Frontend Engineering Fellow role extends the Distinguished Frontend Engineer role.

Hiring Process

Candidates for a Frontend Engineering 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. 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.

Engineering Management Roles at GitLab

View the engineering management job family page for more details on engineering management roles.

Team Specialties

As a frontend engineer, in one of the following team specialities, you should expect to …


Increase user productivity by improving the user experience across the entire GitLab UI, driving initiatives such as internationalization and analytics, as well as refreshing the design across well-trafficked parts of the UI.


Enable people in any size organization the ability to manage and analyze projects, from ideation to execution. You will work on our project management applications, including Issue Management, Kanban Boards, and Agile Portfolio Management.


Build and improve features related to creating projects using GitLab. This includes dealing with Source Code of projects including Snippets, Code Reviewing (Merge Requests), the Web IDE, projects' Wiki and Design Management.


Focus on building functionality related to the Continuous Integration stage of the DevOps lifecycle. This includes contributing to Performance and Testing tools, Cross-Project Pipelines, Visual Review Apps, and CI Recipes. Our mission is to help developers feel confident in delivering their code to production.


Create a consistent user experience for developers to interact with our integrated universal package management solution. Our focus is to simplify package sharing within organizations and teams while providing an extra layer of confidence in external dependencies.


The tools you build will be used by developers and security engineers alike, to help their teams to detect and mitigate potential vulnerabilities before they hit production. This involves displaying results of our automated security scanning, for example Dependency Scanning. The UI we build display aggregated data of scanning results in a user-friendly way.


Focus on building functionality related to the Continuous Delivery stage of the DevOps lifecycle. This includes contributing to Review Apps, Feature Flags, Merge Request Pipelines, and GitLab Pages. Our mission is to provide the best experience to developers as they deliver their changes to production with zero-touch software delivery.


Become an expert in Auto DevOps, Kubernetes and Serverless. You should also expect to create fantastic user experiences that help guide users through configuring their application and infrastructure in an intuitive way.


Build charts and dashboards to help users monitor metrics so that users know how changes in their code impacts their production environment. You should expect to become a leader in charting and data visualizations at GitLab and to become very familiar with our charting library, ECharts.


Defend is a new group which will be bootstrapped during 2019. Secure helps to improve security during the development of an application, while Defend does so during the production phase of an application. You should expect that there are a lot of interfaces to be built from scratch in Vue and VueX, potentially with real time updates and charting capabilities.


Geo is an enterprise product feature, built to help speed up the development of distributed teams by providing one or more read-only mirrors of a primary GitLab instance. This mirror (a Geo secondary node) reduces the time to clone or fetch large repositories and projects, or can be part of a Disaster Recovery solution.


Move data-driven product decisions forward by working on telemetry initiatives, understanding how users interact with GitLab. Work at the core of how GitLab earns revenue, working on our licensing and transaction applications.


The Ecosystem team is responsible for seamless integration between GitLab and 3rd party products as well as making GitLab products available on cloud service providers’ marketplaces such as AWS. The team plays a critical role in developing APIs and SDK and expanding GitLab market opportunities.


The Distribution team closely partners with our greater engineering organization to build, configure and automate GitLab deployments. GitLab's distribution team is tasked with creating a seamless installation and upgrade experience for users across a multitude of platforms.

What it’s like to work here at GitLab:

The culture here at GitLab is something we’re incredibly proud of. Because GitLab team-members are currently located in 50+ different countries, you’ll spend your time collaborating with kind, talented, and motivated colleagues from across the globe.

Some of the benefits you’ll be entitled to vary by the region or country you’re in. However, all GitLab team-members 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 to communication.

Also, every nine months or so, we’ll invite you to our Contribute event.



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


Please note that if we are actively hiring for a position, you will see it listed on our jobs page, where all of our current openings are advertised. To apply, please click on the name of the role you are interested in, which will take you to our applicant tracking system (ATS), Greenhouse.

Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply. Our hiring process is described in more detail in our hiring handbook.

About GitLab

GitLab Inc. is a company based on the GitLab open-source project. GitLab is a community project to which over 1,000 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 and inclusion, 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.