DevOps / Platform Engineer

What you'll own

• —CI/CD across every client project, and keeping the pipeline fast enough that nobody routes around it
• —Observability: the dashboards and alerts that mean we know before the client does
• —Cloud cost per client, reported monthly
• —Incident response and the write-up afterwards

What we need

• —Production experience on AWS or GCP, with infrastructure as code
• —Docker, and container orchestration you've genuinely operated
• —CI/CD pipelines you built rather than inherited
• —A security posture you can explain to a procurement questionnaire

Helpful, not required

• —On-premise and air-gapped deployment for regulated clients
• —Terraform, Kubernetes, Prometheus and Grafana
• —Database operations — backups, restores you've actually tested

What this role isn't

So the wrong candidates can rule themselves out in thirty seconds rather than three interviews.

• ×It isn't a pure sysadmin role — you'll write a lot of code.
• ×It isn't siloed. You'll sit with product engineers, not behind a ticket queue.

How we interview

1. 01Screening call — 30 minWhat you've operated and what broke.
2. 02Systems conversation — 90 minWe design a deployment for a real client constraint, including the boring parts.
3. 03Conversation with the Head of Infrastructure — 45 minIncident philosophy and your questions.

Decision within two weeks of the first call. If it's a no, you get a reason, not silence.