AWS DevOps Engineer (Jenkins to Gitlab migration)

Introduction

• 36 hours per week
• Start: asap
• End: 30 April 2027
• Extension is possible
• ZZP is allowed
• Hybrid working applicable
• Mandatory skillset needed: Hands-on migration experience from Jenkins to Gitlab
• The relocation is not possible for this role

Job description

Development Services Team

Development Services is an international/global team. Our vision is to enable development teams to adopt Standardized Platforms, Pipelines and DevX across all teams. As a member of Development Services team, you will be interacting very closely with product development teams, in different regions across the globe.

Your Job

As a DevOps Engineer – Development Services, roll out GitLab standardized CI/CD pipelines across multiple product teams and regions. You will play a key role in the platform transition from Jenkins to GitLab CI/CD, and in enabling secure, scalable deployments on Red Hat OpenShift Private Cloud and AWS-based Public cloud platforms.

This role combines hands-on engineering, platform enablement, and DevSecOps governance in a regulated enterprise environment

Responsibilities:

CI/CD & Pipeline Engineering

• Migrate from bitbucket & Jenkins, AWS CodeCommit & Code Pipeline to GitLab

• Contribute to GitLab usage standards, pipeline templates, and best practices

• Integrate GitLab with enterprise tooling (e.g. artifact repositories, security scanners, observability)

• Apply Git workflows, branching strategies, and merge request standards (trunk based development with feature toggles)

• Deploy and operate applications on Red Hat OpenShift (private cloud platform)

• Support deployments on AWS based platforms (e.g. ECS/Fargate)

Security & Compliance (DevSecOps)

• Embed security controls into CI/CD pipelines (SAST, DAST, dependency scanning)

• Ensure pipelines comply with internal standards and regulatory requirements

• Support audit ready pipeline designs and evidence generation

Collaboration & Enablement

• Actively support development teams during migrations and onboarding

• Deliver training sessions and workshops on pipelines, GitLab, and DevOps practices

• Share knowledge and best practices across product teams and regions

Required Experience & Skills

• Strong hands on experience with GitLab CI/CD

• Experience migrating from Jenkins pipelines to GitLab

• Strong Git knowledge and modern branching strategies

• Scripting skills (e.g. Python, Bash)

• Experience working in complex, distributed enterprise environments

Technical Skills

• GitLab CI/CD Expert

• Jenkins-to-GitLab Migration Experience

• Git & Trunk-Based Development

• Python/Bash Automation

• DevSecOps Security Controls

• OpenShift/Kubernetes

• AWS Deployments

Profile & Competencies

• Strong engineering mindset and problem solving skills

• Ownership mentality and ability to work independently

• Excellent communication and stakeholder collaboration skills

• Flexible, adaptive, and eager to continuously learn

• Comfortable working across regions and cultures

• Proven track record in large scale technical or migration initiatives

Education

• Relevant Bachelor’s or Master’s degree in Computer Science, Engineering, or a related field

Extra information:

DevOps Engineer Role and Technical Priorities

The DevOps Engineer will join an existing team to speed up the Jenkins-to-GitLab migration. GitLab and Jenkins are the leading requirements, with OpenShift and AWS also relevant and other Kubernetes or cloud experience potentially acceptable.

Candidate Screening and Migration Experience

CVs did not reflect their actual experience. Validate migration contributions with questions about the candidate’s role, design decisions, organization, and number of pipelines migrated.

Interview Structure and GitLab Experience

Interviews begin with migration-related technical questions and then follow the candidate’s CV; both technical and interpersonal considerations may arise in either round. A candidate without direct migration experience may still be considered if they have built GitLab pipelines or setups from scratch rather than only maintaining them.