Senior DevOps Engineer

We Are Hiring!

For a global Israeli cloud services provider, we are looking for a Senior Engineer to join our team on a remote basis.

We are specifically seeking candidates located in Eastern Europe, Armenia, Azerbaijan, Georgia, or Kazakhstan.

Below is the detailed job description:

Senior DevOps Engineer (5+ Years Experience)

We are looking for an experienced Senior DevOps Engineer to join our team and contribute to large-scale projects. The role is hands-on and requires strong expertise in designing, implementing, and optimizing CI/CD pipelines, automation, and AWS environments.

Requirements

5+ years of professional experience as a DevOps Engineer.

Proven experience in large-scale migration projects, specifically Jenkins → GitHub Actions.

Jenkins expertise: strong knowledge of shared libraries, Groovy, Bash, Jenkins credentials, and Jenkins files.

GitHub Actions expertise: ability to design and manage workflows across multiple repositories, configure secrets and runners, and manage authentication between GitHub and runners.

AWS experience: hands-on work with IAM roles for EC2, IRSA for EKS, STS, SSH, and AWS SDK.

Strong scripting skills: Bash, Groovy, and proven development of automation scripts.

Python and Ansible proficiency.

Proven experience in developing complex pipelines, including those that incorporate different TypeScript frameworks.

Excellent problem-solving skills and ability to work independently on complex technical challenges.

Nice to Have

Familiarity with Terraform.

First and foremost, experience with Jenkins in writing pipelines. Inside Jenkins, a combination of Bash and Groovy. After that, experience in migration from Jenkins to GitHub Actions.

Then, experience with Python.

Languages: Python, Bash, Ansible.

After that, experience with Terraform.

Experience in provisioning resources in AWS: EC2, EKS, NSG, VPC, and similar services.

The key strength should be in writing scripts: these can be interconnected scripts in Bash and Python, where one triggers the other and together they form pipelines.

If all of this is in place, then request from the candidate a detailed description of their experience with Jenkins.

After that, obtain proof of experience with at least 100–500 pipelines, and100–500 triggers and reusables that they have built for pipelines.