Senior GitLab System Administrator
Senior GitLab System Administrator
Posted today
SENIORITY
Senior
About the role
- Administer and maintain GitLab across multiple environments
- Perform structured version upgrades across all environments following change management procedures
- Manage platform infrastructure
- Maintain and extend Ansible playbooks and Terraform configurations (infrastructure-as-code)
- Setu and Manage AWS Geo DR site
- Administer GitLab Runners (shared Linux runners, EKS runners) and CI/CD infrastructure
- Support cloud-native GitLab deployments including Kubernetes-based installations using Helm charts and container orchestration on EKSMonitor platform health using Splunk, Grafana, and ServiceNow alerting and responding to incidents
- Handle user support requests via Mattermost and ServiceNow escalations
- Manage SSL/TLS certificates, Kerberos Keytabs, and service accounts
- Remediate vulnerabilities and manage Corrective Action Plans (CAPs) within required timelines
- Participate in SAFe Program Increments and sprint ceremonies
- Document procedures, runbooks, and architecture changes in team wiki
- Coordinate with Network, Security, Database, and M365 teams for cross-functional work
- Generic Managerial Skills, If any
- Coordinate with team across multiple towers
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
