Devops Engineer in Edinburgh

Edinburgh, United Kingdom | Posted on 06/01/2026 We are looking for a skilled and pragmatic DevOps Engineer to own and evolve our infrastructure across the EMEIA region. This is a dual-horizon role: you will keep our existing VM-based systems healthy while leading a greenfield effort to design and build the managed environment that those solutions will migrate onto. A significant proportion of what we build is produced rapidly using AI-assisted, structured development. That means our solutions can move from idea to deployment faster than ever, and our infrastructure needs to keep pace. We need someone who thrives in a fast-moving, ambiguous environment, can absorb change quickly, and treats adaptability as a core part of the job rather than an occasional demand. The new managed environment is most likely to be based on Kube — Apple’s internal Kubernetes (EKS) deployment — though the final architecture will be a team decision and AWS@Apple remains an option for workloads requiring greater control. You will help inform that decision and then own the build‑out, regardless of which direction is chosen. You will work closely with data engineers, developers, and analysts, acting as the infrastructure backbone for a team that moves quickly and expects you to move with it. The role also involves working directly with third‑party vendors who support some of the tools being deployed, and collaborating with teams outside of EMEIA — including WorldWide — to align on standards, share solutions, and resolve cross‑regional dependencies. KEY RESPONSIBILITIES Lead the design and build‑out of a new managed container environment to replace existing VM-based infrastructure — the most likely candidate is Kube (Apple’s internal Kubernetes/EKS cluster), but the final decision will be made collaboratively as a team Contribute meaningfully to the environment selection decision: weigh trade‑offs between managed solutions (Kube) and more directly controlled alternatives (AWS@Apple), considering maintenance overhead, operational control, and team capability Own the migration of existing VM-based workloads onto the new platform, managing sequencing, risk, and continuity of service throughout Establish and maintain the standard workflow for deploying solutions: build locally -> containerise -> publish to Kube -> configure connectivity to Apple internal system dependencies Apple Internal Networking if you do it three times, you build a process You adapt quickly: the tools, environments, and solutions you support can change fast, and you treat that as normal rather than exceptional You are pragmatic under pressure: you know when to stop the bleeding first and fix it properly later You are self‑directed and comfortable owning problems end‑to‑end with minimal hand‑hanging You are a willing partner to developers who move fast — you keep up, add guardrails where they matter, and don’t become a bottleneck WHAT SUCCESS LOOKS LIKE A new managed container environment is designed, built, and running — with existing VM‑based workloads migrated onto it in a controlled, sequenced way The standard deployment path (build -> containerise -> publish -> connect) is well‑established, documented, and easy for the team to use Connectivity from the new environment to Apple internal systems (Snowflake, Appleconnect, Shield, Floodgate, etc.) is reliable, well‑understood, and correctly secured Teams are unblocked quickly when they need new integrations, access, or capabilities — even when the solutions they are deploying have been built at speed Production issues are resolved rapidly, with lasting fixes following close behind Monitoring catches issues before users do The infrastructure estate — both old and new — is well‑documented, well‑understood, and in a known‑good state #J-18808-Ljbffr