<div class="content-intro">The GitLab&nbsp;<a class="c-link" href="https://about.gitlab.com/solutions/devops-platform/" target="_blank" data-stringify-link="https://about.gitlab.com/solutions/devops-platform/" data-sk="tooltip_parent" data-remove-tab-index="true">DevSecOps platform</a>&nbsp;empowers 100,000+ organizations to deliver software faster and more efficiently. We are one of the&nbsp;<a class="c-link" href="https://about.gitlab.com/company/culture/all-remote/guide/" target="_blank" data-stringify-link="https://about.gitlab.com/company/culture/all-remote/guide/" data-sk="tooltip_parent" data-remove-tab-index="true">world’s largest all-remote companies</a>&nbsp;with 2,000+ team members and&nbsp;<a class="c-link" href="https://handbook.gitlab.com/handbook/values/" target="_blank" data-stringify-link="https://about.gitlab.com/handbook/values/" data-sk="tooltip_parent" data-remove-tab-index="true">values</a>&nbsp;that foster a culture where people embrace the belief that everyone can contribute. Learn more about&nbsp;<a class="c-link" href="https://vimeo.com/778157354" target="_blank" data-stringify-link="https://vimeo.com/778157354" data-sk="tooltip_parent" data-remove-tab-index="true">Life at GitLab</a>.</div><h4>An overview of this role</h4>
As a Frontend Engineer, your work within the <a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/">Plan</a> stage will focus on building and improving high priority and scalable features for some of our largest customers which connect the work that engineering teams perform to higher level strategy, across multiple teams, and in longer time horizons (quarters or years). The core features include issues, epics, and other tools used in software development planning.&nbsp;
This includes getting to work on a platform (i.e.<a href="https://docs.gitlab.com/ee/architecture/blueprints/work_items/"> Work Items</a>) that the Plan team is building as a foundation of GitLab to serve our users for years to come, and you’ll get to do that in collaboration with some of the mort talented engineers out there, including members of the Vue Framework Core Team.
 Some interesting links about the team and role:
<ul>
<li><a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/">Plan Handbook</a></li>
<li><a href="https://handbook.gitlab.com/handbook/engineering/development/dev/plan-project-management/">Project Management</a></li>
<li><a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/">Product Planning</a></li>
</ul>
What you’ll do&nbsp;&nbsp;
<ul>
<li>You’ll be contributing to a foundational GitLab platform (i.e. Work Items) that will power core features like Issues, Epics, Design Management, and OKRs for years to come.</li>
<li>Develop features and improvements to the GitLab product in a secure, well-tested, and performant way</li>
<li>You’ll work with peers within the Plan Stage along with Engineering, Product, and UX counterparts to iterate on new features within your group and across the Plan stage.</li>
<li>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.</li>
<li>Consistently ship features iteratively and make improvements with minimal guidance and support from other team members. Collaborate with the team on larger projects.</li>
<li>You'll help improve the overall experience of the product by improving the quality of the Frontend we ship, within the <a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/">Plan stage.</a>.</li>
<li>You’ll help identify areas of improvements in the code base, both specific to your group and outside your group (eg. <a href="https://gitlab.com/gitlab-org/gitlab-ui">GitLab UI</a> component library) and make contributions to it.</li>
<li>You’ll learn, collaborate, and get opportunities to mentor other Frontend Engineers across the engineering division. Everyone can contribute something new to the team regardless of how long they’ve been in the industry.</li>
<li>You’ll work deliverables as determined in the milestone plan (see <a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/#picking-something-to-work-on">how we plan milestones</a>). These are typically features, bugs, technical debt cleanup, security fixes, and maintenance of owned feature areas.</li>
<li>You’ll contribute to and follow our workflow process, alongside the rest of the Frontend Engineers and the GitLab community as a whole.</li>
</ul>
What you’ll bring&nbsp;
<ul>
<li>Professional experience with Vue 2 or 3 and a state management library such as Vuex or VueApollo</li>
<li>Professional experience with building frontend webapps with GraphQL</li>
<li>Experience with writing automated tests with Jest (bonus for RSpec)&nbsp;</li>
<li>A solid understanding of semantic HTML, CSS and core JavaScript concepts</li>
<li>A solid understanding of core web and browser concepts (eg. how the browser parses and constructs a web page)</li>
<li>Experience with Ruby and HAML is highly desirable (but not madatory)&nbsp;</li>
<li>Demonstrated capacity to clearly and concisely communicate about complex technical, architectural, and/or organizational problems and propose thorough iterative solutions</li>
<li>Experience with performance and optimization problems and a demonstrated ability to both diagnose and prevent these problems</li>
<li>Comfort working in a highly agile, intensely iterative software development process</li>
<li>Effective communication skills: Regularly achieve consensus with peers, and clear status updates</li>
</ul>
&nbsp;
About the team
You’ll be joining either the Product<a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/"> Planning</a> or Project Management team, which are part of the <a href="https://about.gitlab.com/handbook/engineering/development/dev/plan/">Plan</a> stage, consisting of a globally distributed team where there is a culture of autonomy. You’ll also get the chance to work directly with Product Design and Product Management counterparts from time to time.
How do we work together? It starts with milestones planned through collaboration between the PM and EM where we identify and schedule deliverables for a given milestone, additionally, we also like to plan a few milestones in advance and prepare an Issue Board containing a list of Issues for current and a few future milestones which team members can use to pick work from. This process allows for engineers to prioritise deliverables, as well as pick up extra work voluntarily.
<h4>How GitLab will support you</h4>
<ul>
<li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/">Benefits to support your health, finances, and well-being</a></li>
<li><a href="https://about.gitlab.com/company/culture/all-remote/guide/">All remote</a>, <a href="https://about.gitlab.com/company/culture/all-remote/asynchronous/">asynchronous</a> work environment</li>
<li><a href="https://about.gitlab.com/handbook/paid-time-off/">Flexible Paid Time Off</a></li>
<li><a href="https://about.gitlab.com/company/culture/inclusion/erg-guide/#:~:text=Definition%20of%20the%20TMRG%20%2D%20Team%20Member%20Resource%20Groups,-TMRGs%20are%20voluntary&amp;text=The%20purpose%20for%20this%20type,developing%20the%20sense%20of%20belonging.">Team Member Resource Groups</a></li>
<li><a href="https://about.gitlab.com/handbook/stock-options/">Equity Compensation &amp; Employee Stock Purchase Plan</a></li>
<li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#growth-and-development-benefit">Growth and development budget&nbsp;</a></li>
<li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave">Parental leave</a>&nbsp;</li>
<li><a href="https://about.gitlab.com/handbook/finance/procurement/office-equipment-supplies/">Home office</a> support</li>
</ul>
Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from <a href="https://about.gitlab.com/company/culture/inclusion/#examples-of-select-underrepresented-groups">underrepresented groups</a> are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application.<div class="content-conclusion"><hr>
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.&nbsp;&nbsp;
Privacy Policy: Please review our <a href="https://about.gitlab.com/handbook/hiring/candidate/faq/recruitment-privacy-policy/" target="_blank">Recruitment Privacy Policy.</a> Your privacy is important to us.
GitLab is proud to be an equal opportunity workplace and is an affirmative action employer. GitLab’s policies and practices relating to recruitment, employment, career development and advancement, promotion, and retirement are based solely on merit, regardless of race, color, religion, ancestry, sex (including pregnancy, lactation, sexual orientation, gender identity, or gender expression), national origin, age, citizenship, marital status, mental or physical disability, genetic information (including family medical history), discharge status from the military, protected veteran status (which includes disabled veterans, recently separated veterans, active duty wartime or campaign badge veterans, and Armed Forces service medal veterans), or any other basis protected by law. GitLab will not tolerate discrimination or harassment based on any of these characteristics. See also&nbsp;<a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#equal-employment-opportunity-policy" target="_blank">GitLab’s EEO Policy</a>&nbsp;and&nbsp;<a href="https://about.gitlab.com/handbook/labor-and-employment-notices/#eeoc-us-equal-employment-opportunity-commission-notices" target="_blank">EEO is the Law</a>. If you have a disability or special need that requires&nbsp;<a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#reasonable-accommodation" target="_blank">accommodation</a>, please let us know during the&nbsp;<a href="https://about.gitlab.com/handbook/hiring/interviewing/#adjustments-to-our-interview-process" target="_blank">recruiting process</a>.</div>

The GitLab [DevSecOps platform](https://about.gitlab.com/solutions/devops-
platform/) empowers 100,000+ organizations to deliver software faster and more
efficiently. We are one of the [world’s largest all-remote
companies](https://about.gitlab.com/company/culture/all-remote/guide/) with
2,000+ team members and [values](https://handbook.gitlab.com/handbook/values/)
that foster a culture where people embrace the belief that everyone can
contribute. Learn more about [Life at GitLab](https://vimeo.com/778157354).

####  **An overview of this role**

As a Frontend Engineer, your work within the
[Plan](https://about.gitlab.com/handbook/engineering/development/dev/plan/product-
planning/) stage will focus on building and improving high priority and
scalable features for some of our largest customers which connect the work
that engineering teams perform to higher level strategy, across multiple
teams, and in longer time horizons (quarters or years). The core features
include issues, epics, and other tools used in software development planning.

This includes getting to work on a platform (i.e.[ Work
Items](https://docs.gitlab.com/ee/architecture/blueprints/work_items/)) that
the Plan team is building as a foundation of GitLab to serve our users for
years to come, and you’ll get to do that in collaboration with some of the
mort talented engineers out there, including members of the Vue Framework Core
Team.

  
Some interesting links about the team and role:

  * [Plan Handbook](https://about.gitlab.com/handbook/engineering/development/dev/plan/)
  * [Project Management](https://handbook.gitlab.com/handbook/engineering/development/dev/plan-project-management/)
  * [Product Planning](https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/)

**What you’ll do**  

  * You’ll be contributing to a foundational GitLab platform (i.e. _Work Items_ ) that will power core features like Issues, Epics, Design Management, and OKRs for years to come.
  * Develop features and improvements to the GitLab product in a secure, well-tested, and performant way
  * You’ll work with peers within the Plan Stage along with Engineering, Product, and UX counterparts to iterate on new features within your group and across the Plan stage.
  * 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 features iteratively and make improvements with minimal guidance and support from other team members. Collaborate with the team on larger projects.
  * You'll help improve the overall experience of the product by improving the quality of the Frontend we ship, within the [Plan stage.](https://about.gitlab.com/handbook/engineering/development/dev/plan/).
  * You’ll help identify areas of improvements in the code base, both specific to your group and outside your group (eg. [GitLab UI](https://gitlab.com/gitlab-org/gitlab-ui) component library) and make contributions to it.
  * You’ll learn, collaborate, and get opportunities to mentor other Frontend Engineers across the engineering division. Everyone can contribute something new to the team regardless of how long they’ve been in the industry.
  * You’ll work deliverables as determined in the milestone plan (see [how we plan milestones](https://about.gitlab.com/handbook/engineering/development/dev/plan/product-planning/#picking-something-to-work-on)). These are typically features, bugs, technical debt cleanup, security fixes, and maintenance of owned feature areas.
  * You’ll contribute to and follow our workflow process, alongside the rest of the Frontend Engineers and the GitLab community as a whole.

**What you’ll bring  **

  * Professional experience with Vue 2 or 3 and a state management library such as Vuex or VueApollo
  * Professional experience with building frontend webapps with GraphQL
  * Experience with writing automated tests with Jest (bonus for RSpec) 
  * A solid understanding of semantic HTML, CSS and core JavaScript concepts
  * A solid understanding of core web and browser concepts (eg. how the browser parses and constructs a web page)
  * Experience with Ruby and HAML is highly desirable (but not madatory) 
  * 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 software development process
  * Effective communication skills: Regularly achieve consensus with peers, and clear status updates



**About the team**

You’ll be joining either the Product[
Planning](https://about.gitlab.com/handbook/engineering/development/dev/plan/product-
planning/) or Project Management team, which are part of the
[Plan](https://about.gitlab.com/handbook/engineering/development/dev/plan/)
stage, consisting of a globally distributed team where there is a culture of
autonomy. You’ll also get the chance to work directly with Product Design and
Product Management counterparts from time to time.

How do we work together? It starts with milestones planned through
collaboration between the PM and EM where we identify and schedule
deliverables for a given milestone, additionally, we also like to plan a few
milestones in advance and prepare an Issue Board containing a list of Issues
for current and a few future milestones which team members can use to pick
work from. This process allows for engineers to prioritise deliverables, as
well as pick up extra work voluntarily.

#### **How GitLab will support you**

  * [Benefits to support your health, finances, and well-being](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/)
  * [All remote](https://about.gitlab.com/company/culture/all-remote/guide/), [asynchronous](https://about.gitlab.com/company/culture/all-remote/asynchronous/) work environment
  * [Flexible Paid Time Off](https://about.gitlab.com/handbook/paid-time-off/)
  * [Team Member Resource Groups](https://about.gitlab.com/company/culture/inclusion/erg-guide/#:~:text=Definition%20of%20the%20TMRG%20%2D%20Team%20Member%20Resource%20Groups,-TMRGs%20are%20voluntary&text=The%20purpose%20for%20this%20type,developing%20the%20sense%20of%20belonging.)
  * [Equity Compensation & Employee Stock Purchase Plan](https://about.gitlab.com/handbook/stock-options/)
  * [Growth and development budget ](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#growth-and-development-benefit)
  * [Parental leave](https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave) 
  * [Home office](https://about.gitlab.com/handbook/finance/procurement/office-equipment-supplies/) support

Please note that we welcome interest from candidates with varying levels of
experience; many successful candidates do not meet every single requirement.
Additionally, studies have shown that people from [underrepresented
groups](https://about.gitlab.com/company/culture/inclusion/#examples-of-
select-underrepresented-groups) are less likely to apply to a job unless they
meet every single qualification. If you're excited about this role, please
apply and allow our recruiters to assess your application.

* * *

**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.  

**Privacy Policy:** Please review our [Recruitment Privacy
Policy.](https://about.gitlab.com/handbook/hiring/candidate/faq/recruitment-
privacy-policy/) Your privacy is important to us.

GitLab is proud to be an equal opportunity workplace and is an affirmative
action employer. GitLab’s policies and practices relating to recruitment,
employment, career development and advancement, promotion, and retirement are
based solely on merit, regardless of race, color, religion, ancestry, sex
(including pregnancy, lactation, sexual orientation, gender identity, or
gender expression), national origin, age, citizenship, marital status, mental
or physical disability, genetic information (including family medical
history), discharge status from the military, protected veteran status (which
includes disabled veterans, recently separated veterans, active duty wartime
or campaign badge veterans, and Armed Forces service medal veterans), or any
other basis protected by law. GitLab will not tolerate discrimination or
harassment based on any of these characteristics. See also [GitLab’s EEO
Policy](https://about.gitlab.com/handbook/people-policies/inc-usa/#equal-
employment-opportunity-policy) and [EEO is the
Law](https://about.gitlab.com/handbook/labor-and-employment-notices/#eeoc-us-
equal-employment-opportunity-commission-notices). If you have a disability or
special need that requires
[accommodation](https://about.gitlab.com/handbook/people-policies/inc-
usa/#reasonable-accommodation), please let us know during the [recruiting
process](https://about.gitlab.com/handbook/hiring/interviewing/#adjustments-
to-our-interview-process).

