Required
3+ years in an operations, SRE, production support, or NOC role, including hands-on experience leading (not just participating in) incident response in a production environment
Solid working experience operating in AWS and Azure — IAM, compute, networking, storage, and an understanding of cost and security trade-offs (not just "basics")
Proficient scripting in Bash and/or PowerShell, plus Python for automation, tooling, and integrating between systems
Hands-on experience building and tuning observability — dashboards, alerts, and SLO/SLI-based monitoring in at least one platform (CloudWatch, Azure Monitor, Grafana, Datadog, etc.), including reducing alert noise and false positives
Track record of authoring and improving runbooks/SOPs, not only following them — turning repeat incidents into documented, ideally automated, resolutions
Experience owning incidents through their full lifecycle: triage, coordination, stakeholder comms, resolution, and driving post-incident reviews / corrective actions
Comfortable in a ticketing system (Jira, ServiceNow, etc.), managing SLAs, and participating in an on-call rotation
Strong written and verbal communication — you'll lead incident comms, run handoffs, and mentor junior engineers
Nice to have
Infrastructure-as-code experience (Terraform, CloudFormation, Bicep/ARM)
Hands-on with CI/CD platforms (Jenkins, Azure DevOps, GitHub Actions) — building or maintaining pipelines, not just triggering them
Container / orchestration exposure (Docker, Kubernetes, ECS/AKS)
Git-based workflows for version-controlling scripts, IaC, and runbooks
Relevant certifications (AWS SysOps Administrator / Solutions Architect Associate, AZ-104, or equivalent)
