Next step
Tell me what you're building
Send me a short description of the problem and I'll tell you whether I'm the right fit, what it would cost, and how long it would take. No pitch deck.
- Phone
- +46 70 753 73 78
- elinorwigertz
Backend, platform and SRE work on Spotify's core infrastructure, at global scale
Cloud / DevOps
Spotify's Core Infrastructure group builds and operates the platform Spotify's backend services run on. It serves 11–12 million backend requests per second, globally, for 777 million monthly users in 184 markets, on a Kubernetes fleet spanning regions from Europe and the US to Asia. I joined in September 2026 for backend, platform and SRE work at that scale.
01
Seeing the compute the fleet can actually get used to mean jumping between many monitoring systems and panels in GCP. I built a single pane of glass for it, alone. It shows what compute is available, reserved and running out, per region, live, for anyone in the company who needs it. Everyone and everything is visible in one place, quickly, which was basically impossible before. It was picked up the moment it existed and now drives compute planning for the rest of the year, critically for Black Friday and Cyber Monday.
02
At this scale the risky part of removing an unhealthy machine is doing it without causing an outage. Every node in the fleet runs a health agent I built, and nodes are never allowed to retire themselves. They report to one central service, where I built the part that decides and acts. It takes a faulty node out of rotation, keeps it for debugging and alerts the team, and it is rate-limited so it can never take down a whole cluster. A service that can reach every machine in a global fleet is only as safe as its limits, so the limits were the work.
03
Creating or updating a custom tenant cluster touches GitHub Enterprise, Backstage and Jira. I automated it with AI agents under one rule. The agent makes the decisions, and every action it takes in those systems goes through strict scripts it is required to use. Whatever gets created or posted is deterministic and consistent, however the agent got there. That rule is what makes an agent safe to put in a real workflow.
04
Alongside the build work I upgraded critical platform services across Spotify's global server fleet, policy enforcement among them, and that work has continued with image verification. I also took part in the global GKE version upgrades and took over several projects in handover, among them a new multi-tenant auth and IAM system and the next generation of service auth. None of it waited on a ramp-up. I was working across the entire platform, globally, within the first days.
Principal Engineer
GCP / GKE / Kubernetes / Java / React / Python / Bash / gRPC / Grafana / Terraform / Terraform Cloud / Backstage / AI agents

Zero idle compute cost
Automated builds and Steam releases for the studio behind Core Keeper
Principal Engineer
GitHub Actions / AWS / EC2 / S3 +6
Zero to self-service CI/CD
From manual deploys to developer self-service
DevOps Architect & Engineer
Kubernetes / AWS EKS / Terraform / Terragrunt +9
100+ apps across 4 regions
Platform engineering and SRE for a global developer platform
Principal Engineer
Kubernetes / AWS / Azure / Terraform +9
Next step
Send me a short description of the problem and I'll tell you whether I'm the right fit, what it would cost, and how long it would take. No pitch deck.