Job Description: Site Reliability Engineer – Contractor

Position Title: Site Reliability Engineer – Contractor Functional Group: SOI WDigital SRE Location: Sydney / Hybrid Engagement Duration: 6 Months

The Mission As a Site Reliability Engineer within the SOI WDigital SRE team, your mission is to bridge the gap between complex multi-cloud operations and automated, self-healing infrastructure. You will be instrumental in driving platform resilience, availability, and scalability across Google Cloud Platform (GCP) and Microsoft Azure (AKS) environments. In this role, you will lead the implementation of enterprise-wide runbook automation using PagerDuty Runbook Automation (Rundeck), replacing manual operations with repeatable, software-driven workflows, proactive Dynatrace event triggers, one-click disaster recovery failover pipelines, and autonomous remediation routines.

Key Accountabilities ● Runbook & Operational Automation: Architect, build, and maintain end-to-end

automated runbooks and self-healing workflows using PagerDuty Runbook Automation (Rundeck) to reduce toil, execute reliable DR failovers, and significantly lower Mean Time to Resolution (MTTR).

● Automated Incident Remediation: Integrate telemetry alerts with automated execution workflows to diagnose, triage, and resolve recurring production incidents without human intervention.

● Infrastructure as Code (IaC) & Platform Engineering: Develop and maintain modular, reusable Terraform code following GitOps best practices. Deploy and manage secure, self-hosted runner infrastructure across Azure (AKS / Container Apps) and GCP (Cloud Run).

● Kubernetes Orchestration & Disaster Recovery: Manage and optimize containerized workloads across AKS and GKE using Helm. Build parameter-driven cross-region failover automation and self-healing pod restart/remediation controls.

● Observability, Auditing & Governance: Connect Dynatrace alerting webhooks directly to automation execution engines. Stream real-time runbook audit logs and execution histories into Google BigQuery to support governance and Looker reporting.

Must-Have Requirements ● Cloud Engineering Depth: Minimum 5+ years of hands-on engineering experience

in Microsoft Azure (primary) with working knowledge and strong exposure to Google Cloud Platform (GCP).

● Infrastructure as Code (IaC): Deep proficiency in Terraform (modular development, state file management, drift resolution) and GitOps delivery pipelines.

● Container & Kubernetes Expertise: Strong experience deploying, configuring, and operating workloads on Kubernetes (Azure AKS and/or GCP GKE)

● Scripting & Software Automation: Advanced scripting proficiency in Python or Bash (Go is a strong plus) for systems integration, REST API interactions, and custom tooling.

● CI/CD & Secret Security: Practical experience building and securing CI/CD pipelines (GitHub Actions or Azure DevOps) and managing secrets using Azure Key Vault or Google Secret Manager.

Good-to-Have ● Runbook & Workflow Automation: Hands-on track record deploying and

orchestrating jobs via PagerDuty Runbook Automation (Rundeck) or equivalent enterprise event-driven action platforms.

● Observability & Streaming: Hands-on experience ingesting operational telemetry/audit logs into Google BigQuery for Looker visualization.

● ITSM Integration: Experience integrating automation tools with ServiceNow REST APIs (incident auto-creation, work note updates, and CMDB CI mapping).

● Advanced Resilience Patterns: Experience designing cross-region cloud disaster recovery runbooks, chaos engineering experiments, or automated traffic rerouting.

● Next-Gen SRE Mindset: Familiarity with modern Agentic SRE patterns, LLM-assisted incident triage, and cloud cost-optimization (FinOps) strategies.

Core Attributes ● Relentless Anti-Toil Mindset: An engineering instinct to replace repetitive, manual

tasks with deterministic code and self-healing logic. ● Ownership Under Pressure: High accountability for system availability with strong

diagnostic capabilities during complex incident investigations. ● Cross-Functional Collaboration: Ability to articulate technical trade-offs clearly to

both application development squads and platform engineering peers.