Staff DevOps Engineer

Our mission is to become the global standard for addressing. Street addresses weren’t designed for 2026. They aren’t accurate enough to specify building entrances, and they don’t exist for parks, rural areas and many parts of the world. This makes it hard to find places and causes problems and inefficiencies on a global scale. That’s why we created what3words . We divided the world into 3m squares and gave each square a unique combination of three words. It’s the easiest way to find and share precise locations. Over the last year, what3words has been used in 193 countries, and our monthly active users continue to grow at an impressive pace. Our tech is used by emergency services, delivery companies, eCommerce businesses, ride-hailing apps and NGOs, and is integrated into the navigation systems of millions of cars around the world. The role: At what3words , we're proud of our tech stack. We have built a massively scalable, microservices-based architecture, based around Kubernetes on AWS. You'll be exposed to technologies such as EKS, Terraform, Terragrunt, Istio, Karpenter, Flux, GitHub Actions, Prometheus, Grafana, Go, Python, Lambda and CloudFront — with a little GCP alongside. Our DevOps team is deliberately broad: the team owns platform engineering, SRE, observability and security. The remit is wide and the ownership is end-to-end, so you'll carry work from the design call through to how it behaves in production. You'll work closely with colleagues in our UK office, so you'll need to be effective asynchronously and comfortable making your case in writing. Responsibilities: Own our infrastructure as code as a governed product rather than a pile of configuration — a versioned, tested module library with clear ownership, change control and automated quality gates. Build the self-service paths that let product teams provision what they need without waiting on us, then measure adoption and iterate until they're genuinely used. Make reliability a property of the delivery path rather than something inspected afterwards, with service level objectives, dashboards and alerting wired in by default. Shift Left Security approach for workflows — policy as code, least privilege and secure-by-default templates, so that our teams can build on a foundation of good decisions. Treat cloud cost as an engineering responsibility, with commitment and allocation decisions made deliberately. Take open-ended platform problems through to durable outcomes against multi-quarter...

Summary and match are AI-generated; verify details on the original posting.

Listed via Himalayas. All sources