DevOps Engineer

pAre you a Senior DevOps Engineer who wants to own the infrastructure behind a live product, rather than maintain one corner of someone else's platform? /p pA hospitality technology company whose platform runs live restaurant operations is adding a second DevOps engineer to own and harden the cloud infrastructure it all runs on. /p pFully remote across Europe. B2B contract, invoiced through your own entity. /p p2 stages: /p ul liConversation with the Founder /li liTechnical Interview with the Tech Team /li /ul pThe platform is live, in production, and restaurants depend on it during service. When the infrastructure has a bad night, restaurants have a bad night. /p ul liOver 100 million transactions processed to date /li liAround 500GB of live operational data across restaurant customers /li liSeries A closing, with revenue growing month on month /li liAn engineering team of eight: CTO, three backend, mobile, frontend, data and DevOps /li /ul pThe next step is making that infrastructure resilient enough. Repeatable, observable, secure, and able to survive losing a region. That is where you come in. /p pYou will own and improve the cloud infrastructure alongside the existing DevOps engineer, from the EKS clusters and Aurora databases through to security and disaster recovery. /p h3The Role: /h3 pYou will work alongside the existing DevOps engineer, and closely with the CTO and the backend and data engineers who ship on top of what you both build. /p pThis is hands on. You write the Terraform, run the clusters, tune the databases and test the failover yourself. /p pIn a two person DevOps function, you will have a real say in how infrastructure is built, deployed and recovered. /p pThis is a long term, full time engagement on a B2B basis, not a fixed scope project. The team already works this way across Europe, so the setup is established rather than experimental. /p h3What You Will Be Doing: /h3 ul liRunning AWS infrastructure across EKS, networking, DNS, load balancing, security and cost /li liOwning Aurora PostgreSQL clusters: performance, monitoring, backups, replication and failover /li liBuilding and maintaining infrastructure as code in Terraform, so every environment is reliable and repeatable /li liImplementing GitOps based Kubernetes deployments using Argo CD or Flux /li liBuilding multi-region disaster recovery end to end: infrastructure failover, database recovery, and DR testing that proves it works /li liTightening security across secrets management, access controls and vulnerability management /li liBuilding metrics, logging and tracing so problems are caught before restaurants feel them /li /ul h3Experience We Are Looking For: /h3 ul liFive or more years in DevOps, SRE, Platform Engineering or Cloud Infrastructure /li liStrong production experience with AWS, Kubernetes on EKS, Terraform, Linux and containerised workloads /li liManaging, monitoring and troubleshooting PostgreSQL in production, ideally AWS Aurora PostgreSQL /li liMetrics, logging and tracing with the Grafana open source stack on Kubernetes, for example Prometheus or Mimir, Loki and Tempo /li liDesigning secure, highly available, multi-region infrastructure and disaster recovery /li liStrong troubleshooting across cloud infrastructure, Kubernetes, networking and databases /li liReal projects you can talk through, professional or personal, where you built it, ran it and fixed it /li /ul h3Nice To Have: /h3 ul liGitOps with Argo CD or Flux /li liCloudflare, edge networking and WebSocket based applications /li liAWS, Kubernetes (CKA, CKAD), Terraform or other cloud native certifications /li liHigh traffic or latency sensitive production systems /li /ul pThis is not the role for you if you want a large platform team to hand work to, or would rather maintain a finished platform than build the next version of one. /p pIt is the role for you if you are already the person who knows how production actually hangs together, and you want to shape the infrastructure, the standards and the DR plan rather than inherit them. /p pThis is a senior role. Not a 9-5, not a 9-9-6. Judged on output. /p