A mid-level DevOps engineer who builds and
runs our delivery pipelines and Azure infrastructure. At 3–5 years, they should
own CI/CD and environments end to end (pipelines, infrastructure as code,
security, monitoring, cost), automate away manual steps, and support
engineering teams shipping our Python, React / Next.js and AI-based
applications.
What separates this level from junior: they
design pipelines and environments others can reuse, treat security and cost as
part of the job, troubleshoot production incidents on their own, and push teams
toward self-service rather than tickets.
Area
What
they should be able to do
Priority
Azure DevOps Services
Administer organizations and projects;
Azure Repos branch policies; Azure Boards; Azure Artifacts feeds; service
connections and permissions
Must have
Azure Pipelines
Multi-stage YAML pipelines, templates and
reusable stages, environments and approvals, variable groups, self-hosted and
Microsoft-hosted agents
Must have
GitHub Actions
Build equivalent workflows; migrate
between Azure Pipelines and GitHub Actions when needed
Strong plus
Infrastructure as code
Terraform and / or Bicep: modules, remote
state, environments, drift detection; plan / apply gated in pipelines
Must have
Azure platform
App Service, Functions, AKS, Container
Apps, Azure SQL / PostgreSQL, Storage, Key Vault, Front Door / Application
Gateway, VNets and private endpoints
Must have
Containers and Kubernetes
Docker image builds and hardening, Azure
Container Registry, AKS operations, Helm, basic GitOps (Flux or Argo CD)
Must have
Identity and security
Microsoft Entra ID, managed identities,
workload identity federation, RBAC, Key Vault secrets, Defender for Cloud,
Azure Policy
Must have
DevSecOps
Secret scanning, dependency and container
scanning, SAST in pipelines, signed artifacts, SBOMs
Must have
Monitoring and reliability
Azure Monitor, Log Analytics (KQL),
Application Insights, alerts, dashboards; incident response and post-incident
reviews
Must have
Scripting
PowerShell and Bash; Azure CLI; enough
Python to automate tasks
Must have
Release strategies
Blue-green, canary, feature flags,
rollbacks, database migrations in pipelines
Must have
Cost management
Azure Cost Management, tagging, budgets,
right-sizing, reserved capacity
Strong plus
AI platform operations
Deploy and secure Azure OpenAI / Azure AI
Foundry resources, model endpoints and quotas; private networking for AI
services
Strong plus
Networking
Hub-and-spoke, NSGs, DNS, private links,
VPN / ExpressRoute basics
Strong plus
Experience Requirements
- 3–5 years in DevOps, platform or cloud engineering, with at least 2 years on Microsoft Azure
- Built and maintained multi-stage YAML pipelines in Azure DevOps across multiple applications and environments
- Provisioned production Azure environments entirely through Terraform or Bicep
- Ran containerized workloads in production on AKS or Azure Container Apps
- Served on call for production systems and led or contributed to incident reviews
- Implemented security controls in pipelines and cloud environments that passed an audit or security review
- Degree in Computer Science, IT or a related field, or equivalent practical experience
Certifications (preferred, not required)
- AZ-400: Designing and Implementing Microsoft DevOps Solutions (Azure DevOps Engineer Expert)
- AZ-104: Azure Administrator Associate
- AZ-305 (Solutions Architect Expert), AZ-500 (Security Engineer), or CKA / CKAD are a plus
Nice to Have
- Experience supporting Python and Node.js / Next.js application stacks
- Experience operating AI workloads: Azure OpenAI, vector databases, GPU or high-memory compute, model quotas and cost controls
- Familiarity with compliance frameworks such as SOC 2, ISO 27001 or GDPR, including evidence collection for audits
- Experience with multi-tenant SaaS environments and customer-specific deployments
- Experience with AWS or GCP alongside Azure
Working Style
- Automates first and documents what can’t be automated
- Treats pipelines and infrastructure as products for developers, with templates and self-service
- Stays calm and methodical during incidents and writes blameless post-incident reviews
- Keeps security and cost in mind by default
- Explains infrastructure choices clearly to developers and non-technical stakeholders



.jpeg)