Senior Platform Engineer

HEY THERE! You've run Kubernetes in production long enough to know the difference between using a cluster and owning one. Maybe you're part of a large platform team where you only ever see your slice. Here, you'd see all of it: our Platform Engineering team is small and senior, building and running the infrastructure that Yazio's Backend and Data Engineering teams deploy to every day. We're hiring a Senior Platform Engineer to help us run that platform and push it further toward cloud-native. Let's shape the future of nutrition together and make Yazio the most successful nutrition app worldwide! This role is 100% remote and open to candidates based in Germany, Spain, Portugal or the UK. YOUR MISSION Think of our platform as an internal product, with Yazio's engineers as your users. You'll: Run and evolve our Kubernetes landscape (Amazon EKS, plus on-prem clusters via Rancher). Every deployment at Yazio lands on what you operate Automate deployment and scaling until releases are a non-event, and guide engineering teams in getting the most out of that automation Build out observability so you spot problems before users notice them: metrics, dashboards, alerting Dig into infrastructure-level incidents and turn what you find into fixes that stick Design the abstractions that let Backend and Data Engineers ship without opening a ticket Have a real say in our shift away from the remaining self-hosted infrastructure: what moves to the cloud, what stays and what gets automated away YOUR PROFILE You'll thrive here if: You've operated Kubernetes in production for years. Upgrades, capacity planning, debugging the cluster itself, not just the workloads running on it Observability, GitOps and deployment automation are how you work by default, not extras you bolt on later You're at home on a Linux host, and the second time you touch something manual, you automate it You know databases (relational and key-value) and networking well enough to reason through a production issue. You don't need to be a DBA or a network engineer; curiosity covers the rest Small team, changing priorities, nobody handing you a spec: that sounds like your kind of week When you explain a complex technical trade-off, people leave the conversation clearer than they arrived Bonus points for: Go (a lot of our tooling is written in it, and so is the Kubernetes ecosystem) or Python beyond simple scripting Running self-hosted databases in production, replication and recovery included Deep networking knowledge (TLS, TCP/UDP internals) Operating on-prem Kubernetes with Rancher OUR CORE TECH STACK Here's what we currently run in production: Infrastructure & platform: Kubernetes (Amazon EKS and on-prem via Rancher), Docker, Linux-based systems, AWS CI/CD & automation: GitHub Actions, ArgoCD, Ansible, GitOps workflows Databases: MariaDB and PostgreSQL Monitoring & observability: Prometheus, Grafana, InfluxDB, Elasticsearch, Graylog Programming: Go, Python, Bash If you've run Kubernetes