Senior Platform & DevSecOps Engineer

terraform plan: hire_senior_platform_engineer

$ terraform plan

Terraform will perform the following actions:

# role.platform_engineer will be created

+ resource "headcount" "platform_engineer" {

+ title = "Senior Platform & DevSecOps Engineer"

+ location = "Melbourne (hybrid, 3-4 days)"

+ reports_to = "Platform Engineering Lead"

+ status = "GREENFIELD"

+ alert_fatigue = "destroy"

+ toil = "destroy"

+ cognitive_load = -80%

}

Plan: 1 to add, 47 manual deploys to destroy, 1 platform to build.

The honest version of this ad

Most platform engineering ads are a copy-paste of buzzwords with a salary hidden three paragraphs down. We're not doing that.

Here's what's actually true: our customer is a large, well-established business with serious scale, and their Cloud & Platform team has laid the foundations (CI/CD is standing up, observability is in place), but the real build is still ahead. This isn't a role to maintain a finished platform. It's a role to help design it, argue about it, and ship it.

If you've ever muttered "why are we still doing this by hand" in a stand-up, keep reading.

What you'd actually be doing

• Building the Golden Path: a self-service platform that lets developers spin up secure, compliant AWS infrastructure without filing a ticket and waiting three days
• Graduating their IaC: taking Terraform/OpenTofu from "a pile of scripts" to versioned, reusable modules that don't fall over across environments
• Running the engine room: standardising CI/CD pipelines (.NET, React) with real deployment gates, canaries, and rollbacks that actually roll back
• Putting security in the pipeline, not in a PDF: Policy-as-Code (OPA/Sentinel), SAST/DAST, secrets management, baked into the developer workflow instead of bolted on after the fact
• Turning alerts into signal: tuning observability around SLOs/SLIs so the on-call phone stops ringing for things that don't matter
• Being the internal "PM" for platform: talking to the engineers who actually use what you build, and making their lives measurably easier

What you'd bring

• Real AWS depth: serverless, microservices, networking, the stuff that holds up under load, not just the stuff that looks good in a diagram
• Terraform/OpenTofu fluency at the module level, not the "single main.tf" level
• CI/CD pipeline ownership: you've built the pipeline, not just used one someone else built
• A security-first instinct: IAM/RBAC, Policy-as-Code, vulnerability scanning, secrets management, the works
• Comfort with Python, Go, or Bash to automate the boring parts
• 5+ years in DevOps, SRE, or Platform Engineering
• A whiteboard marker you're not afraid of: we'll talk through how you'd actually solve problems, not just whether you've heard of them

What you won't be doing

Babysitting a platform someone else already finished. This is genuinely early. The foundations are laid; the building is still under construction, and you'd be one of the architects, not a tenant.

The practical bit

Permanent role. Competitive base + super, plus performance bonus. Hybrid, typically 3-4 days in office depending on team, with flexibility for the right person. Based in Melbourne.

We move fast on great candidates, so if this sounds like you, don't sit on it.