Skip to main content

DevOps / Automation Engineer (Azure-Focused)

Posted 2 days ago

techdigital groupMiddletown (NJ)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Objective Identify a DevOps engineer capable of designing and implementing end-to-end CI/CD and cloud infrastructure, with strong emphasis on Azure ecosystem, automation, and migration from ADO to GitHub Actions. Must Have'sStrong recent hands-on experience in Microsoft Azure (preferred over AWS). Expertise in CI/CD tools: Azure DevOps (ADO) GitHub & GitHub Actions JFrog ArtifactoryHands-on experience with Infrastructure as Code (Terraform).Key Responsibilities Design and implement end-to-end CI/CD pipelines across Azure DevOps, GitHub, and GitHub Actions. Lead migration from Azure DevOps (ADO) to GitHub Actions, including repository and artifact transition using JFrog. Architect and deliver cloud infrastructure solutions (cloud/on-prem/hybrid) with strong automation orientation. Build scalable and reusable DevOps automation frameworks using Terraform. Implement and manage containerized environments using Docker and Kubernetes (AKS). Drive CI/CD best practices including pipeline standardization, automation, and optimization. Mandatory Skills (Must Have) Strong recent hands-on experience in Microsoft Azure (preferred over AWS). Expertise in CI/CD tools: Azure DevOps (ADO) GitHub & GitHub Actions JFrog ArtifactoryHands-on experience with Infrastructure as Code (Terraform). Deep understanding of Azure Kubernetes Service (AKS) and networking/integration concepts. Strong experience in Linux, Docker, and containerization.
Desired Skills: (Good to Have) Experience with GitLab (indicative of GitHub Actions adaptability). Knowledge of hybrid/cloud infrastructure architectures. Key Evaluation Criteria Area What to Look For Cloud Platform Strong Azure experience (recent hands-on) CI/CD Proven design of pipelines using GitHub Actions + ADO Migration Experience ADO → GitHub Actions transformation Automation Terraform-led infrastructure automation Containers AKS + Docker + Kubernetes expertise Artifacts Experience with JFrog integration End-to-End Ownership Designed full CI/CD + infrastructure stack

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this