Frontend Engineer

A brief overview:

GitLab is building an open source, single application for the entire DevOps lifecycle—from project planning and source code management to CI/CD, monitoring, and security.

We already have a large team of Frontend Engineers and we're planning to more than double the team's size over the next year. You can look over our organizational chart to see open vacancies.

At GitLab, we live and breathe open source principles. This means our entire handbook is online, and with a few clicks you can find the details of future releases and an overview of the product vision you’d contribute to when working here.

What you can expect in a Frontend Engineer role at GitLab:

You'll help improve the overall experience of our product through improving the quality of the Frontend features

You’ll help identify areas of improvements in the code base and help contribute to make it better

You’ll work alongside the UX team, the Backend Engineering team and Product Managers to iterate on new features within the GitLab product.

You’ll learn, collaborate and teach other Frontend Engineers. Everyone can contribute something new to the team regardless of how long they’ve been in the industry.

You’ll fix prioritized issues from the issue tracker. These are typically bugs listed in a GitLab issue with an attached severity and priority label.

Nice to have:

You have experience optimizing code and look for ways to resolve performance issues

You have experience working with modern frontend frameworks (eg. React, Vue..etc)

You have working knowledge of Ruby on Rails

You have domain knowledge relevant to the product stage in which you are looking to join (eg. someone with CI/CD experience applying for the Verify & Release team)

What it’s like to work here at GitLab:

The culture here at GitLab is something we’re incredibly proud of. Because GitLabbers are currently located in 51 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 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 to communication. Also, every nine months or so, we’ll invite you to our Contribute event.

Intermediate Frontend Engineer

Propose new ideas, needs guidance in performing feasibility analyses and scoping the work

Capable of leading medium sized features, bug fixes, and integrations with limited guidance from leads or seniors (Eg. Begin to show architectural perspective)

Should be striving to make the entire team more productive through their efforts. This might be through mentoring junior developers, or by improving the team's process, documentation, testing or tooling in a way that helps everyone in the team be more effective.

Code quality

Leave code in better shape than before (Eg. Leave tests in better shape than before: faster, more reliable, more comprehensive, etc.)

Strive to reduce complexity contained as much as possible: if a feature is complex, that's sometimes unavoidable, but Intermediate Developers show that they can reduce or mitigate complexity in their changes

Able to communicate on technical topics and present ideas to the rest of the team

Proactive in asking for guidance from others when needed

Keep issues up-to-date with progress

Performance & Scalabilty

Writes production-ready code with minimal assistance

Fixes performance issues on GitLab.com with minimal guidance using our existing tools, and identify areas of improvements where needed

Senior Frontend Engineer

Technical Skills

Write modular, well-tested, and maintainable code

Leadership

Propose new ideas, performing feasibility analyses and scoping the work

Capable of leading complicated features, bug fixes, and integrations with limited guidance from leads (Eg. Begin to show architectural perspective)

Should make the entire team more productive through their efforts. This might be through mentoring junior developers, or by improving the team's process, documentation, testing or tooling in a way that helps everyone in the team be more effective.

Code quality

Leave code in substantially better shape than before (Eg. Keep complexity contained as much as possible, Leave tests in better shape than before)

Fix bugs/regressions quickly

Monitor overall code quality/build failures

Communication

Provide thorough and timely code feedback for peers, leaving minimal work for later reviews / maintainers

Able to communicate clearly on technical topics and present ideas to the rest of the team

Keep issues up-to-date with progress

Performance & Scalability

Excellent at writing production-ready code with little assistance

Are able to fix performance issues on GitLab.com with minimal guidance using our existing tools, and improve those tools where needed

Relevant links

Hiring 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. To learn more about someone who may be conducting the interview, find her/his job title on our team page.

Selected candidates will be invited to complete a short written assessment.

Next, candidates will be invited to schedule a 30 minute screening call with our Global Recruiters

Next, candidates will be invited to schedule a 60 minute technical and behavioral interview with a Frontend Hiring Manager

Candidates will then be invited to schedule a 60 minute interview with the Director of Engineering

Apply

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, frugality, collaboration, directness, kindness, diversity, 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:

Work with helpful, kind, motivated, and talented people.

Work remote so you have no commute and are free to travel and move.

Have flexible work hours so you are there for other people and free to plan the day how you like.

Everyone works remote, but you don't feel remote. We don't have a head office, so you're not in a satellite office.

Work on open source software so you can interact with a large community and can show your work.

Work on a product you use every day: we drink our own wine.

Work on a product used by lots of people that care about what you do.

As a company we contribute more than we take, most of our work is released as the open source GitLab CE.

Focused on results, not on long hours, so that you can have a life and don't burn out.

Open internal processes: know what you're getting in to and be assured we're thoughtful and effective.