DevOps, Core Platform
About the role
- Take a change from a commit in CI to a running system on a customer site, and keep every step repeatable.
- Safe upgrades:
- Roll out upgrades step by step with no downtime, watch the system as it changes, and stop and alert the team automatically when something goes wrong.
- Disconnected sites:
- Make installs and upgrades work with no internet, using signed, self-contained packages.
- Release checks:
- Work on the release system that checks that all our services work together, in CI and at release time.
- Collaboration:
- Work with platform architects and developers so every new service is easy to package, deploy and upgrade. Work with our forward deployed engineers, who install and run the software at customer sites, so the same tools run in development and at the customer.
- Documentation:
- Write the procedures that a person at a customer site can follow without our help.
- Growth:
- Make it easier and faster for our engineers to ship changes to customer sites.
- Candidate requirements
- Strong skills in at least one language (Rust, Go, Python, Java).Kubernetes and delivery:
- Hands-on experience with Kubernetes and containers, and with Helm, GitOps (Argo CD or Flux) and CI systems.
- Builder:
- You have built, not just used, tools that deploy or run software.
- Production:
- You have run or debugged upgrades or deployments in production, and you know the basics of metrics, health checks and logs.
- Educational background:
- Degree in computer science, software engineering or a similar field. Equivalent professional experience is equally valued.
- Writing Kubernetes operators or controllers.
- Signing and supply-chain tools, such as Sigstore/cosign and SBOMs.
- Packaging software for air-gapped sites, for example with Zarf and registry mirrors such as Harbor.
- Bare-metal Kubernetes (OpenShift, RKE2 or Talos) with Ceph or MinIO.Mindset
- Pragmatic engineering:
- You choose simple solutions and proven tools first.
- Attention to detail:
- You obsess over edge cases and robustness before you ship a change.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
