#108 - GitLab Administrator / Platform Engineer - Service Account Migration

Overview

We are seeking two hands-on GitLab Administrators / Platform Engineers for a temporary, bounded migration initiative. The work centers on converting existing automation identities into GitLab native service accounts while preserving dependent CI/CD workflows, permissions, and operational continuity.

Enterprise experience strongly preferred.

Key Responsibilities

• Migrate a defined portfolio of existing service accounts to GitLab native service accounts, one account at a time.
• Rotate or replace credentials and tokens as each automation identity is cut over.
• Securely decommission old credentials and access after successful validation.
• Update permissions and group/project access for migrated automation identities.
• Diagnose and resolve CI/CD or automation failures caused by credential, token, permission, or identity changes.
• Coordinate migration timing, validation, and follow-up with the teams that own the affected automation.
• Support secure, reliable completion of a time-bounded access-remediation initiative.

Must-Have Skills

• Hands-on GitLab administration or platform engineering experience.
• Experience with CI/CD pipelines and automated tooling.
• Experience rotating or replacing credentials and tokens in automation workflows.
• Experience securely decommissioning old access after a credential or identity cutover.
• Experience debugging CI/CD or automation integrations that depend on service credentials.
• Prior experience migrating service accounts or other non-human identities.
• Experience updating permissions and group/project access for automation identities.
• Mid-to-senior-level experience.

Nice-to-Have Skills

• Experience with identity and access migrations.
• Experience with secrets hygiene or credential-exposure remediation.
• Experience executing repetitive operational work accurately across many similar accounts or tickets.
• Prior service-account migrations, permission replication, or token cutovers in GitLab or a similar source-control platform.
• Ability to untangle unclear ownership and drive follow-up across multiple teams.

Required Tools & Platforms

• GitLab
• GitLab native service accounts or comparable non-human identity models
• CI/CD pipelines and automated tooling
• Credential and token management workflows
• Group/project permissions and access controls

Location, Time & Engagement

• Candidates must be based in an eligible LATAM location.
• Availability for 40 hours per week is required.
• Working-hour alignment with U.S. time zones from Eastern through Pacific is required.