Azure DevOps Engineer

Our client is building out its Azure environment and moving from manual, portal-driven work to everything defined in code. The Azure foundation is in place. Now they need an engineer who can build the delivery side on top of it: the pipelines, the Git Hub setup, the Terraform standards, and the Kubernetes platform that apps will run on.

This is a hands-on role on a small team. You'll work alongside an Azure infrastructure engineer and the team's architect, and you'll have real say in how things get built. A lot of the near-term work is getting new internal apps, including AI tools, safely into production.

What you'll do

• Run Git Hub Enterprise for the organization: org and repo settings, branch protection and rulesets, access, repo templates, and the self-hosted runners that pipelines run on.
• Build Git Hub Actions pipelines that move infrastructure and app changes from code to production, with approvals, safe secrets handling, and a clear way to roll back.
• Lead the migration of existing Bicep and portal-built resources into Terraform without disrupting what's running, and set the team's Terraform standards for modules, state, and reviews.
• Build and operate AKS clusters in Terraform: networking, node pools, ingress, workload identity, secrets, version upgrades, and troubleshooting.
• Decide where new apps should run, whether that's AKS or a simpler managed option like App Service or Container Apps, and get them live with monitoring and alerting in place.
• Write runbooks and hand work over cleanly to Operations so it doesn't depend on you.

Must haves

• Strong hands-on Azure experience in production. You know subscriptions, resource groups, networking basics, and Azure roles and permissions well enough to work on your own.
• Terraform you've personally written and run in production, including bringing existing resources under Terraform and managing state safely.
• Git Hub Actions pipelines you built and maintained for real deployments.
• Real admin experience in Git Hub Enterprise or a Git Hub organization at company scale: permissions, policies, rulesets, or runners. Using Git Hub as a developer isn't enough.
• Kubernetes or AKS clusters you built and ran yourself, including at least one version upgrade or production incident you handled. Deploying apps onto someone else's cluster isn't enough.
• Experience taking an app from code to production, including secrets, monitoring, and what happens when a release goes wrong.
• Comfortable scripting in Power Shell, Bash, or Python.

Nice to haves

• Migrating Bicep or ARM templates to Terraform.
• Ephemeral or autoscaling self-hosted runners, and connecting Git Hub to Azure without stored passwords (OIDC).
• Reusable workflows, repo templates, or a "new project" setup that other teams use.
• Helm, and Git Ops tools like Argo CD or Flux.
• Git Hub Advanced Security (code and secret scanning).
• Azure Monitor, Log Analytics, and Application Insights.
• Azure Container Apps, Azure Functions, or App Service.
• Policy as code with Azure Policy.
• Microsoft Fabric exposure, for future projects.