GitLab Administrator/Platform Engineer

Svitla Systems Inc. is looking for a GitLab Administrator/Platform Engineer for a full-time position (40 hours per week) in Argentina. Our client is one of the world’s largest and fastest-growing job sites.

Our client is undertaking a one-time, time-bound initiative to migrate existing GitLab service accounts from standard user accounts to GitLab native service accounts. This migration is part of a broader effort to strengthen account security and optimize licensing costs.

Because GitLab does not currently provide tooling to automate this migration, the process must be completed manually on an account-by-account basis. In this role, you will support the migration of existing service accounts, ensuring that each account is correctly converted, validated, and transitioned to the new configuration.

This is a focused contractor position with a clearly defined scope and completion goal. Successful delivery will help strengthen the client’s security posture while reducing ongoing licensing costs.

Timezone Coverage: U.S. Time Zones (ET-PT)

Requirements

• Hands-on experience with GitLab administration or platform engineering.
• Experience working with CI/CD pipelines and automation tooling.
• Experience rotating or replacing credentials and tokens in automation workflows and securely decommissioning outdated access.
• Experience troubleshooting CI/CD or automation integrations that rely 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 professional experience in a relevant technical role.

Will be a plus

• Experience with identity and access migrations.
• Experience with secrets management, credential hygiene, or remediation of credential exposure.
• Experience handling repetitive operational tasks across a large number of similar accounts or tickets in parallel.
• Prior experience with service account migrations, permission replication, or token cutovers, particularly in GitLab or similar source-control platforms.
• Ability to navigate unclear ownership and proactively drive follow-up across multiple teams.

Responsibilities

• Manually migrate all 88 service accounts currently configured as user accounts to GitLab native service accounts, one account at a time.
• Rotate or replace credentials and tokens and securely decommission outdated access as each account is migrated.
• Update permissions and group/project access for the migrated automation identities.
• Coordinate closely with account-owning teams throughout the migration process.
• Validate each migrated account and ensure that associated automation workflows continue to function as expected.
• Track migration progress, identify blockers or ownership gaps, and drive issues through to resolution.