This job post is closed and the position is probably filled. Please do not apply. Work for GitLab and want to re-open this job? Use the edit link in the email when you posted the job!
Production Engineers are responsible for the keeping GitLab.com and many other\nGitLab production systems running smoothly 24/7/365. They're developers \nspecialising in systems, whether it be networking, or the Linux kernel,\nor even a specific interest in scaling, algorithms, or distributed systems.\n\nGitLab.com is a unique site and it brings unique challenges: it’s the biggest \nGitLab instance in existence; in fact, it’s one of the largest single-tenancy \nopen-source SAAS sites on the internet. The experience of our production \nengineers feeds back into other engineer groups within the company, as well as \nto GitLab customers, running on-premise installations.\n\nResponsibilities: \n\n\n\n* Be on a PagerDuty rotation to respond to GitLab.com availability incidents and \n\n* provide support for service engineers with customer incidents.\n\n* Use your on-call shift to prevent incidents from ever happening.\n\n* Manage our infrastructure with Chef, Terraform and Kubernetes.\n\n* Make monitoring and alerting alert on symptoms and not on outages.\n\n\n\n\n\n* Document every action so your learnings turn into repeatable actions and then into automation.\n\n* Improve the deployment process to make it as boring as possible.\n\n* Design, build and maintain core infrastructure pieces that allow GitLab scaling to support hundred of thousands of concurrent users.\n\n* Debug production issues across services and levels of the stack.\n\n* Plan the growth of GitLab's infrastructure.\n\n\n\n\nRequirements: \n\n\n* Think about systems - edge cases, failure modes, behaviors, specific implementations.\n\n* Know your way around Linux and the Unix Shell.\n\n* Know what is the use of config management systems like Chef (the one we use)\n\n* Have strong programming skills - Ruby and/or Go\n\n* Have an urge to collaborate and communicate asynchronously.\n\n* Have an urge to document all the things so you don't need to learn the same thing twice.\n\n* Have a proactive, go-for-it attitude. When you see something broken, you can't help but fix it.\n\n* Have an urge for delivering quickly and iterating fast.\n\n* Share our values, and work in accordance with those values.\n\n\n\n\nProjects you might work on: \n\n\n* Coding infrastructure automation with Chef\n\n* Improving our Prometheus Monitoring or building new Metrics\n\n* Helping release managers deploy and troubleshoot new versions of GitLab-EE.\n\n* Migrate GitLab.com from it’s current home on Azure Cloud to Google Cloud Platform.\n\n* Migrate GitLab.com to Kubernetes. \n\n\n \n\n#Salary and compensation\n
No salary data published by company so we estimated salary based on similar jobs related to Engineer, Cloud, Ruby, SaaS and Linux jobs that are similar:\n\n
$70,000 — $120,000/year\n
\n\n#Benefits\n
๐ฐ 401(k)\n\n๐ Distributed team\n\nโฐ Async\n\n๐ค Vision insurance\n\n๐ฆท Dental insurance\n\n๐ Medical insurance\n\n๐ Unlimited vacation\n\n๐ Paid time off\n\n๐ 4 day workweek\n\n๐ฐ 401k matching\n\n๐ Company retreats\n\n๐ฌ Coworking budget\n\n๐ Learning budget\n\n๐ช Free gym membership\n\n๐ง Mental wellness budget\n\n๐ฅ Home office budget\n\n๐ฅง Pay in crypto\n\n๐ฅธ Pseudonymous\n\n๐ฐ Profit sharing\n\n๐ฐ Equity compensation\n\nโฌ๏ธ No whiteboard interview\n\n๐ No monitoring system\n\n๐ซ No politics at work\n\n๐ We hire old (and young)\n\n
# How do you apply?\n\nThis job post has been closed by the poster, which means they probably have enough applicants now. Please do not apply.