Intermediate Site Reliability Engineer - Datastores

October 12

Apply Now

Receive Emails with Similar Jobs

GitLab

WebsiteLinkedInAll Job Openings

1001 - 5000 employees

💰 Secondary Market on 2020-11

Description

• Site Reliability Engineers (SREs) are responsible for keeping all user-facing services and other GitLab production systems running smoothly. • Automating every operational task is a core requirement for this role. • Responding to platform emergencies, alerts, and escalations from Customer Support. • Ensure systems exist to manage software life-cycles (e.g. Operating Systems) with a minimum of manual effort. • Develop a fully automated multi-environment observability stack based on the existing SaaS system. • As an SRE you will work on database reliability and performance aspects for GitLab.com as well as work on shipping solutions with the product. • Document every action so your learnings turn into repeatable actions and then into automation.

Requirements

• Have strong engineering experience deploying, managing and scaling PostgreSQL in large and dynamic production SaaS environments • Possessing an in-depth understanding of PostgreSQL internals, including architecture, storage, indexing, and query optimization • Have solid experience operating PostgreSQL databases in a containerized environment using Kubernetes and modern operators from CloudNativePG, Crunchydata or Zolando • Have solid understanding of Kubernetes architecture and experience with Kubernetes clusters in production • Have strong experience with infrastructure automation and configuration management (Chef, Ansible, Puppet, Terraform…) • Experienced with CI/CD pipelines and infrastructure as code (IaC) practices. • Have solid experience monitoring and logging tools for database and container orchestration environments (e.g., Prometheus, Grafana, ELK stack) • Share our values, and work in accordance with those values • Have excellent written and verbal English communication skills, with an urge to collaborate and communicate asynchronously • Have an urge to document all the things so you don't need to learn the same thing twice, and an urge for delivering quickly and iterating fast • Have a proactive, go-for-it attitude. When you see something broken, you can't help but fix it • Bonus: Strong programming skills as a (former) backend engineer - Preferably with Ruby and/or Go.