Senior Backend Engineer, Plan: Knowledge Engineering (Ruby)

at GitLab

Remote, APAC

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

Knowledge (https://handbook.gitlab.com/handbook/engineering/development/dev/plan/knowledge/) is a small team owning GitLab Wiki, GitLab Pages, and everything related to markdown and text editing in GitLab. Our next focus is transforming GitLab Wiki from a simple Git wrapper to a fully-featured knowledge management solution with search, intuitive navigation, comments, permissions, etc. We also maintain GitLab Pages - a very popular static website hosting solution written in Go, focusing on ensuring high availability and performance. And we manage markdown features across GitLab, powered by a Rust-based parser, adding dynamic capabilities like link expansions and more.

As the new Senior Backend Engineer, you will work on the highly requested features as well as maintaining the existing features by investigating and fixing existing bugs You’ll get to know our codebase, roadmap, and working methods. You will then take ownership and be responsible for both architecture and hands-on implementation. You’ll also help the team and community via code review, issue refinement, engaging with users and open-source contributors on public issues and merge requests, and advocating for process improvements.

Some examples of our projects:

• GitLab Wiki roadmap (https://gitlab.com/groups/gitlab-org/-/epics/12826)

• GitLab Pages roadmap (https://gitlab.com/groups/gitlab-org/-/epics/7766)

• Rich Text editor roadmap (https://gitlab.com/groups/gitlab-org/-/epics/5401)

What You’ll Do

• Drive the development of specific features for GitLab Wiki and GitLab Pages together with the team, from initial issue analysis and architecting solutions to writing the code.

• Support other team members and advocate for quality via code reviews, participating in retrospectives, and helping to onboard new engineers.

• Collaborate across teams: engage with other engineers, product manager, infrastructure teams, and users to refine feature specifications and drive them to general availability.

• Advocate for improvements to product quality, security, performance, and team processes.

• Iterate in everything you do : identify the minimal viable changes (https://handbook.gitlab.com/handbook/product/product-principles/#the-minimal-viable-change-mvc) and constantly ship value to users while keeping a larger product vision in mind

• Engage with community contributors and users on public issues: figure out the best solutions for specific issues, write detailed “how to implement” guides, and support contributors in the review process.

What You’ll Bring

• Significant professional experience with Ruby On Rails. 70% of our code is in the Rails monolith, so you need to be comfortable with it and enjoy writing Ruby code.

• SQL and Database Proficiency : Proficiency in writing efficient SQL queries, preferably with PostgreSQL, to manage and manipulate data effectively.

• Some experience with Go or Rust (non-professional experience is fine)

• Professional experience building web applications and APIs (REST or GraphQL )

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

• Adopt to Asynchronous Work (https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/) : Manage priorities effectively focusing on results. Communicate clearly and navigate team dynamics proactively in our remote setting.

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

• Contributions to GitLab are highly regarded , but not strictly necessary.

About the team

You’ll join a distributed team around the globe with backend and frontend engineers, a Product Manager, and an Engineering Manager. You will have support from staff engineers in larger technically challenging projects. We collaborate mostly asynchronously without many meetings, and engineers are actively participating in shaping the product direction and the team’s workflows. We use Go and Rust in parts of our products, so you can sharpen your skills with these technologies. Most of our features are completely free and open-source, and we have an active open-source community.

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

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