Senior GitLab Engineer

Uppgiften

As Senior GitLab Engineer, you'll take ownership of our self-managed GitLab. Almost everything our engineers do runs through it: source code, CI/CD, the container registry, and the tooling that delivers changes into our infrastructure. After that, you'll run it as a service that engineering can rely on as Verda grows. You'll be part of our IT team and own the GitLab service, while engineering teams own what they build on it and Security sets the security policy. You'll work closely with our DevEx team to make developers' lives easier, and train backup owners in IT, so GitLab never depends on one person. Own GitLab end to end: Configuration, maintenance, upgrades, troubleshooting, and the roadmap for where GitLab goes next. You will work with teams to decide how the instance is best run, and you are accountable for it running well. Architecture and resilience: Design how we run GitLab so it is highly available, performs well, and can recover from failures as Verda grows. This includes capacity planning and scaling decisions. Backup, recovery, and continuity: Set up automated backups for repositories, databases, configuration, and secrets, and test restores regularly. Agree recovery targets with the engineering teams and document them in line with Verda's continuity policy. Shared CI runners: Build and run the shared CI runner fleet, so teams get fast, reliable pipelines without managing their own infrastructure. Teams that need their own runners, for example for deployments, keep owning them. You set the standard for how those runners connect and work with Security to keep all runners secure. Monitoring and operational reliability: Monitor GitLab's health, performance, storage, and capacity, and tune it as usage grows. Set up alerts that are useful, lead incident response and root-cause analysis, and fix problems for the long term rather than just restarting. Safe change: Test upgrades, configuration changes, and new features in staging before they reach production. Apply security releases quickly, keep rollback plans tested, and manage configuration as code where possible. Security and access: Keep GitLab patched and securely configured, together with Security. Set up SSO, group-based access, and a clear group structure, look after tokens and service accounts, and keep audit logs that show who did what. Automation and documentation: Automate admin work with the GitLab APIs and CLI. Write runbooks that someone else can follow under pressure, and train backup owners in IT, so GitLab never depends on one person.