Volvo Cars

One platform, two clouds, and teams who did not choose your abstractions

Delivery runs on Flux and ArgoCD, service-to-service traffic on Istio, across Azure and AWS. Owning areas of a shared platform is mostly reliability work for other people's applications: incident response, SLOs and SLIs defined in Grafana, postmortems, and a release process (versioning strategy, rollout guides, user notifications) that a hundred teams can actually plan around.

Clouds

AKS + EKS

Delivery

Flux + ArgoCD

Mesh

Istio

Self-service means a Backstage plugin, not a ticket

I built Backstage plugins in TypeScript and React so application teams could answer their own questions: live ArgoCD deployment status for their own services, and an AI/RAG-powered support bot in React and Node.js for the platform questions that would otherwise have arrived as tickets. Platform work is usually judged on infrastructure, but what a developer actually meets is a page, so someone on the platform side has to be able to build the page.

Compliance and cost are platform features too

I established the security compliance framework across the estate (PCI compliance and CVE management) and implemented dynamic cost optimisation across 1000+ nodes spanning both Azure and AWS.