DevOps Engineer - Invisible Technologies

About The Role

As a DevOps Engineer on the Platform team, you\'ll build and operate the infrastructure that every engineering team at Invisible depends on — Kubernetes, CI/CD, identity, secrets management, networking, and observability — along with the internal tooling that allows engineers and AI coding agents to ship safely and quickly.

The Platform team is small relative to the surface area it covers, which means you\'ll take ownership of production systems early and see the impact of your work across every client engagement. A single well-designed abstraction here removes friction for the entire engineering organisation.

We are looking for engineers who don\'t just apply best practices in IaC, Kubernetes, CI/CD and observability, but understand the problems those practices were designed to solve. Most were built around the pace and failure modes of human engineers. Those assumptions are changing, and we want people ready to help rewrite the rulebook for the agentic era.

What You\’ll Do

• Own platform services end to end — design, build, operate, and improve them, including on-call responsibility


• Deliver infrastructure as code using Terraform, Helm, and ArgoCD, with GitOps as the default operating model


• Build and maintain developer experience tooling: onboarding templates, CI/CD pipelines, local development environments, and self-service capabilities that remove manual gatekeeping


• Contribute to our agent infrastructure — sandboxed execution environments, credential brokering, guardrails, and the internal MCP servers and skills that make coding agents effective against our stack


• Improve observability and alerting so that system health is visible and actionable without manual investigation


• Participate in incident response and post-incident review, treating failures as systemic issues rather than individual ones

What We Need

• Kubernetes & Cloud: Hands-on experience running production Kubernetes with real users and real consequences, on GCP, Azure, or AWS


• Infrastructure as Code: Working knowledge of Terraform, Helm, and GitOps delivery patterns such as ArgoCD or Flux


• Programming: Proficient in Python, able to step outside of it when called for.


• AI Coding Agents: Demonstrable mastery of agentic coding tools. You understand how to scope work so an agent completes it successfully, how to build the context and tooling that makes that possible, and how to identify confidently incorrect output before it reaches production


• Engineering Judgement: You can articulate the reasoning behind the practices you follow — why immutable infrastructure, why trunk-based development, why SLOs — and where each begins to break down when changes are machine-generated