Senior Infrastructure Engineer

Required

• This is a builder's role, and the bar is high:
• You've taken infrastructure from zero to one - designed and shipped a platform capability that other engineers came to depend on, not just operated one that already existed.
• You write real software (Go, Python, or similar). You build tooling, automation, and services - you don't only wire up other people's tools.
• You're deep in GCP and/or AWS - compute, IAM, VPC, networking, storage, load balancing - and comfortable operating across clouds.
• You've run Kubernetes in production (GKE/EKS) and are up to date with the state of the art for IaC.
• You can debug low-level problems without hand-holding - a networking issue, a saturated node, a slow query, a failing deploy - and get to the actual cause.
• You're fluent across the modern platform toolchain: GitOps (Argo/Flux), containers, CI/CD, observability built on SLOs rather than dashboards no one reads.
• If you've built platforms that other engineers rely on every day, we want to talk.
• What makes people thrive here
• High ownership and low ego. Mission-first. Comfortable where speed and rigor have to coexist - something that takes a quarter elsewhere is expected to move in weeks here, without cutting the corners that matter for security and reliability. You see infra, security, data, and product as one connected system, and you turn one-off fixes into reusable paved roads by instinct.
• What should give you pause
• The scope is real and the playbook isn't fully written - you'll be writing it. Reliability and compliance expectations are high, and mistakes here show up as real incidents for customers and internal teams. If you prefer an environment where everything is defined before you start, this will feel uncomfortable. If that kind of ownership is exactly what you're after, you'll love it.