Backend Engineer (RoR), Plan

Gitlab

hiring-jobs.com

Backend Engineer (RoR), Plan

Remote

GitLab is an open core software company that develops the most comprehensive AI-powered DevSecOps Platform (https://about.gitlab.com/solutions/devops-platform) , used by more than 100,000 organizations. Our mission (https://about.gitlab.com/company/mission) is to enable everyone to contribute to and co-create the software that powers our world. When everyone can contribute, consumers become contributors, significantly accelerating the rate of human progress. This mission is integral to our culture, influencing how we hire, build products, and lead our industry. We make this possible at GitLab by running our operations (https://about.gitlab.com/handbook/using-gitlab-at-gitlab) on our product and staying aligned with our values (https://about.gitlab.com/handbook/values) . Learn more about Life at GitLab (https://vimeo.com/gitlab/gettoknowgitlab) .

At GitLab, developers are independent and self-organized individual contributors who work together as a tight team in a remote and agile (https://about.gitlab.com/2015/09/14/remote-agile-at-gitlab/) way.

Most backend developers work on all aspects of GitLab, building features, fixing bugs, and generally improving the application. The Product Planning backend team works on the backend part of GitLab for the Portfolio Management, Design Management, and Certify product categories. Among other things, this means working on GitLab’s functionality around Epics, Roadmaps, Requirements, Quality Management, and Service Desk. Our mission is to build planning tools that users love and allow collaboration between all levels of the organization. You can read more about our long-term vision on our direction page (https://about.gitlab.com/direction/plan/) .

The Product Planning team collaborates closely with the rest of the Plan stage, and the wider community, to build and improve features that are in high demand by customers. Features such as Epics are widely used internally in the everyday organization of GitLab.

Responsibilities

  • Develop features and improvements to the GitLab product in a secure, well-tested, and performant way

  • Collaborate with Product Management and other stakeholders within Engineering (Frontend, UX, etc.) to maintain a high bar for quality in a fast-paced, iterative environment

  • Advocate for improvements to product quality, security, and performance

  • Solve technical problems of moderate scope and complexity.

  • Craft code that meets our internal standards for style, maintainability, and best practices for a high-scale web environment.

  • Conduct Code Review (https://about.gitlab.com/handbook/engineering/workflow/code-review/) within our Code Review Guidelines (https://docs.gitlab.com/ee/development/code_review.html) and ensure community contributions receive a swift response.

  • Recognize impediments to our efficiency as a team (“technical debt”), propose and implement solutions

  • Represent GitLab and its values in public communication around specific projects and community contributions.

  • Confidently ship small features and improvements with minimal guidance and support from other team members. Collaborate with the team on larger projects.

  • Participate in Tier 2 or Tier 3 weekday and weekend and occasional night on-call rotations (https://about.gitlab.com/handbook/engineering/development/processes/Infra-Dev-Escalation/process.html) to assist troubleshooting product operations, security operations, and urgent engineering issues.

Requirements

  • Significant professional experience (https://about.gitlab.com/job-families/engineering/backend-engineer/#professional-experience) with Ruby on Rails

  • Professional experience with PostgreSQL or a comparable RDBMS

  • 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 (https://about.gitlab.com/handbook/values/#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 (https://about.gitlab.com/handbook/values/#collaboration) , and clear status updates

  • An inclination towards communication, inclusion, and visibility

  • Experience owning a project from concept to production, including proposal, discussion, and execution.

  • Self-motivated and self-managing (https://about.gitlab.com/handbook/values/#efficiency) , with strong organizational skills.

  • Demonstrated ability to work closely with other parts of the organization

  • Share our values (https://about.gitlab.com/handbook/values/) , and work in accordance with those values

  • Ability to thrive in a fully remote organization

  • Ability to use GitLab

  • Comfort and familiarity with our code review process (https://about.gitlab.com/handbook/engineering/workflow/code-review/)

Nice-to-haves

  • Experience in a peak performance organization, preferably a tech startup

  • An understanding of ActiveRecord, GraphQL, and Sidekiq

  • Experience with the GitLab product as a user or contributor

  • Passionate about/experienced with open source and developer tools

  • 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

  • Computer science education or equivalent experience

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.

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

To help us track our recruitment effort, please indicate in your cover//motivation letter where (hiring-jobs.com) you saw this job posting.

Job Location