Frontend Engineers at GitLab work on our product. This includes both the open-source version of GitLab, the enterprise editions, and the GitLab.com service. 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.
- Develop features and improvements to the GitLab product in a secure, well-tested, and performant way
- Work with Product Management and other stakeholders (Backend, UX, etc.) to iterate on new features within the GitLab product.
- Craft code that meets our internal standards for style, maintainability, and best practices for a high-scale web environment. Maintain and advocate for these standards through code review.
- Consistently ship small features and improvements with minimal guidance and support from other team members. Collaborate with the team on larger projects.
- Help improve the overall experience of our product through improving the quality of the Frontend features both in your group and features that benefit other groups.
- Help identify areas of improvements in the code base, both specific to your group and outside your group (e.g. component library) and help contribute to make it better
- 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.
- Fix prioritized issues from the issue tracker. These are typically bugs listed in a GitLab issue with an attached severity and priority label.
- Contribute to and follow our workflow process, alongside the rest of the Frontend Engineers and the GitLab community.
- Advocate for improvements to product quality, security, and performance that have particular impact across your team.
- Solve technical problems of high scope and complexity.
- Exert influence on the overall vision and long-range goals of your team. This could be technical and/or product focused.
- Experience with performance and optimization problems, particularly at large scale, and a demonstrated ability to diagnose and prevent these problems
- Help define and improve our internal standards for style, maintainability, and best practices for a high-scale web environment. Maintain and advocate for these standards through code review.
- Represent GitLab and its values in public communication around broader initiatives, specific projects, and community contributions.
- Provide mentorship for Junior and Intermediate Engineers in your section to help them grow in their technical responsibilities and remove blockers.
- Consistently ship moderately sized features and improvements with minimal guidance and support from other team members. Collaborate with the team on larger projects.
- Improves the engineering projects at GitLab via maintainer trainee program at own comfortable pace, while striving to become a project maintainer.
- Experience with writing automated tests (e.g. Jest, Karma, Jasmine, Mocha, AVA, tape)
- Experience using Git in a professional/workplace environment
- A solid understanding in core web and browser concepts (e.g. how the browser parses and constructs a web page)
- Proficiency in the English language, both written and verbal, sufficient for success in a remote and largely asynchronous work environment
- Demonstrated capacity to clearly and concisely communicate about complex technical, architectural, and/or organizational problems and propose thorough iterative solutions
- Experience with performance and optimization problems and a demonstrated ability to both diagnose and prevent these problems
- Comfort working in a highly agile, [intensely iterative][iteration] software development process
- Demonstrated ability to onboard and integrate with an organization long-term
- Positive and solution-oriented mindset
- Effective communication skills: [Regularly achieve consensus with peers][collaboration], and clear status updates
- An inclination towards communication, inclusion, and visibility
- [Self-motivated and self-managing][efficiency], with great organizational skills.
- Demonstrated ability to work closely with other parts of the organization
- Share [our values][values], and work in accordance with those values
- Ability to thrive in a fully remote organization
- Ability to use GitLab
- Working knowledge of Ruby on Rails and Haml
- Experience in a peak performance organization, preferably a tech startup
- Experience with the GitLab product as a user or contributor
- Product company experience
- Experience working with a remote team
- Enterprise software company experience
- Developer platform/tool industry experience
- Experience working with a global or otherwise multicultural team
- Experience contributing to open-source software
- Domain knowledge relevant to the product stage in which you are looking to join (e.g. someone with CI/CD experience applying for the Verify & Release team)
The Senior Frontend Engineer is a grade 7.
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 their 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 90 minute technical interview with either a Frontend Engineer or a Frontend Engineering Manager
- Next, candidates will be invited to schedule a 45 minute behavioral interview with an Engineering Manager
- Candidates will then be invited to schedule a 60 minute interview with a Director of Engineering
- Successful candidates will subsequently be made an offer.
Additional details about our process can be found on our hiring page.
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. [Mission](/company/mission/): Everyone can contribute
1. [Results](/handbook/values/#results): [Fast growth](/is-it-any-good/), [ambitious vision](/direction/#vision)
1. [Flexible Work Hours](/company/culture/all-remote/people/#those-who-value-flexibility-and-autonomy) so you are there for other people and free to plan
1. [Transparency](/handbook/values/#transparency): [over 2,000 webpages in GitLab handbook](/handbook/about/#count-handbook-pages), [GitLab Unfiltered](https://www.youtube.com/gitlab-unfiltered)
1. [Iteration](/handbook/values/#iteration): [empower people to be effective](/handbook/values/#collaboration), [Merge Request rate](/k/engineering/metrics/#merge-request-rate), [everyone using the product](/handbook/using-gitlab-at-gitlab/#introverts-of-gitlab), [DRI](/handbook/people-group/directly-responsible-individuals/), have an impact
1. [Diversity, Inclusion & Belonging](/handbook/values/#diversity-inclusion): [high percentage of women](/handbook/people-group/people-success-performance-indicators/#diversity---women-at-gitlab),
[Team Member Resource Groups](/company/culture/inclusion/erg-guide/#definition-of-the-tmg---team-member-groups), [other initiatives](/company/culture/inclusion/#what-we-are-doing-with-diversity-inclusion--belonging)
1. [Collaboration](/handbook/values/#collaboration): [kindness](/handbook/values/#kindness), [saying thanks](/handbook/values/#say-thanks), [intentionally organize informal communication](/company/culture/all-remote/informal-communication/), [no ego](/handbook/values/#no-ego)
1. [Compensation](/handbook/total-rewards/compensation/#gitlabs-compensation-principles): [pay at or above the 50th percentile](/handbook/total-rewards/compensation/#competitive-rate), [stock options](/handbook/stock-options/), [office equipment](/handbook/finance/expenses/#-office-equipment-and-supplies)
1. [Work/Life Harmony](/company/culture/all-remote/people/#worklife-harmony): [don't compete on hours worked](/handbook/values/#measure-results-not-hours), [flexible workday](/company/culture/all-remote/guide/#non-linear-workday), [Friends and Family days](/company/family-and-friends-day/)
1. [Remote Done Right](/handbook/marketing/corporate-marketing/all-remote/): [all remote](/handbook/marketing/corporate-marketing/all-remote/#all-remote-flywheel), [prolific inventor of best practices](/handbook/marketing/corporate-marketing/all-remote/#vision)
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.