<div>GitLab is an open-core software company that develops the most comprehensive <a href="https://about.gitlab.com/solutions/devops-platform">AI-powered DevSecOps Platform</a>, used by more than 100,000 organizations. Our <a href="https://about.gitlab.com/company/mission">mission</a> 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 human progress. Our platform unites teams and organizations, breaking down barriers and redefining whats possible in software development. Thanks to products like <a href="https://about.gitlab.com/gitlab-duo/">Duo Enterprise</a> and <a href="https://about.gitlab.com/blog/gitlab-duo-agent-platform-what-is-next-for-intelligent-devsecops/">Duo Agent Platform</a>, customers get AI benefits at every stage of the SDLC.  The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our <a href="https://handbook.gitlab.com/handbook/values/">values</a> and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. <a href="https://www.youtube.com/watch?v=OuZIb5zszQI">Co-create the future with us</a> as we build technology that transforms how the world develops software.</div>Site Reliability Engineers (SREs) are responsible for keeping all user-facing services and other GitLab production systems running smoothly. SREs are a blend of pragmatic operators and software craftspeople that apply sound engineering principles, operational discipline, and mature automation to our environments and the GitLab codebase. We specialize in systems, whether it be Databases, the Linux kernel, or some more specific interest in scaling, algorithms, or distributed systems. The<a href="https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/data-access/database-operations"> Database Operations Team </a>mission is to build, run, own and evolve the entire lifecycle of the PostgreSQL database engine for <a href="http://gitlab.com">GitLab.com</a>. The team is focused on owning the reliability, scalability, performance &amp; security of the database engine and its supporting services. The team should be seeking to build their services on top of<a href="https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/foundations.html"> Reliability::Foundations</a> services and cloud vendor managed products, where appropriate, to reduce complexity, improve efficiency and deliver new capabilities at scale and at the speed of business. GitLab.com is a unique site and it brings unique challenges–it’s the biggest GitLab instance in existence. In fact, it’s one of the largest single-tenancy open-source SaaS sites in the world.. The experience of our team feeds back into other engineering groups within the company, as well as to GitLab customers running Dedicated, Self-Managed  and future Cells installations. Responsibilities <ul> <li>Automating every operational task is a core requirement for this role. For example, package updates, configuration changes across all environments, creating tools for automatic provisioning of user facing services, etc.</li> <li>Responding to platform emergencies, alerts, and escalations from Customer Support.</li> <li>Ensure systems exist to manage software life-cycles (e.g. Operating Systems) with a minimum of manual effort.</li> <li>Develop a fully automated multi-environment observability stack based on the existing SaaS system, and extend it to predict capacity needs based on the usage patterns.</li> <li>Plan for new service roll-outs, expansion and capacity management of existing services, and work with users to optimize their resource consumption. </li> </ul> As an SRE you will: <ul> <li>Function as an SRE in building solutions in service of the Database Operations team’s mission and goals.</li> <li>Work with large databases in a dynamic and growth-oriented environment.  Many interesting and challenging problems await solutions.</li> <li>Work on database reliability and performance aspects for GitLab.com from within the Database Operations team as well as work on shipping solutions with the product.</li> <li>Analyze solutions and implement best practices for our main PostgreSQL database clusters and its components.</li> <li>Work on observability of relevant database metrics and make sure we reach our database objectives.</li> <li>Work with partner  DBREs and peer SREs to roll out changes to our production environment and help mitigate database-related production incidents.</li> <li>On-Call support on rotation with the team.</li> <li>Provide database subject-matter expertise to engineering teams (for example through reviews of database migrations, queries and performance optimizations).</li> <li>Work on automation of database infrastructure and help engineering succeed by providing self-service tools.</li> <li>Use the GitLab product to run GitLab.com as a first resort and improve the product as much as possible.</li> <li>Plan the growth of GitLabs database infrastructure.</li> <li>Support and debug database production issues across services and levels of the stack.</li> <li>Make monitoring and alerting alert on symptoms and not on outages.</li> <li>Document every action so your learnings turn into repeatable actions and then into automation.</li> </ul> You may be a fit to this role if you: <ul> <li>Have extensive experience as an SRE supporting database operations teams.</li> <li>Have strong experience running PostgreSQL at scale in large production environments.</li> <li>Have strong experience with infrastructure automation and configuration management (Chef, Ansible, Puppet, Terraform…)</li> <li>Have solid understanding of SQL and PL/pgSQL</li> <li>Significant experience working in a Large SaaS distributed Systems production environment</li> <li>Share our<a href="https://about.gitlab.com/handbook/values/"> values</a>, and work in accordance with those values.</li> <li>Have an urge to document all the things so you dont need to learn the same thing twice, and an urge for delivering quickly and iterating fast.</li> <li>Have a proactive, go-for-it attitude. When you see something broken, you cant help but fix it</li> <li>Strong data modeling and data structure design skills</li> <li>Bonus: Strong programming skills as a (former) backend engineer - Preferably with Ruby and/or Go.</li> </ul> Projects you could work on: <ul> <li>Review, analyze and implement solutions regarding database administration (e.g., backups, performance tuning)</li> <li>Work with Terraform, Chef, Ansible and other tools to build mature automation (automatic setup of new replicas or testing and monitoring of backups).</li> <li>Implement self-service tools for our engineers using GitLab ChatOps.</li> <li>Provide technical assistance and support to other teams on database and database-related application design methodologies, system resources, application tuning.</li> <li>Review database related changes from engineering teams (e.g., database migrations).</li> <li>Recommend query and schema changes to optimize the performance of database queries.</li> <li>Jump on a production incident to mitigate database-related issues on GitLab.com.</li> <li>Participate actively in the infrastructure design and scalability considerations focusing on data storage aspects.</li> <li>Make sure we know how to take the next step to scale the database.</li> <li>Design and develop specifications for future database requirements including enhancements, upgrades, and capacity planning; evaluate alternatives; and make appropriate recommendations.</li> </ul> Performance Indicators Site Reliability Engineers have the following job-family performance indicators: <ul> <li><a href="http://gitlab.com/">GitLab.com</a><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23gitlab-com-availability"> Availability</a></li> <li><a href="http://gitlab.com/">GitLab.com</a><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23gitlab-com-performance"> Performance</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23apdex-and-error-slo-per-service">Apdex and Error SLO per Service</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23mean-time-to-detection-mttd">Mean Time to Detection</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23mean-time-to-resolution-mttr">Mean Time to Resolution</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23mean-time-between-failures-mtbf">Mean Time Between Failure</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23mean-time-to-production-mttp">Mean Time to Production</a></li> <li><a href="https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/%23disaster-recovery-dr-time-to-recover">Disaster Recovery Time to Recovery</a></li> </ul>  <div><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://handbook.gitlab.com/handbook/people-group/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://handbook.gitlab.com/handbook/total-rewards/stock-options/">Equity Compensation &amp; Employee Stock Purchase Plan</a></li> <li><a href="https://handbook.gitlab.com/handbook/people-group/learning-and-development/growth-and-development/">Growth and Development Fund</a></li> <li><a href="https://about.gitlab.com/handbook/total-rewards/benefits/general-and-entity-benefits/#parental-leave">Parental leave</a> </li> <li><a href="https://handbook.gitlab.com/handbook/finance/expenses/#equipment">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 youre excited about this role, please apply and allow our recruiters to assess your application. <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.   Privacy Policy: Please review our <a href="https://handbook.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 <a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#equal-employment-opportunity-policy" target="_blank">GitLab’s EEO Policy</a> and <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 <a href="https://about.gitlab.com/handbook/people-policies/inc-usa/#reasonable-accommodation" target="_blank">accommodation</a>, please let us know during the <a href="https://about.gitlab.com/handbook/hiring/interviewing/#adjustments-to-our-interview-process" target="_blank">recruiting process</a>.</div>