The Role
The infrastructure runs on AWS today — and the roadmap expands it into Azure and GCP as the product scales across regions (US → EU → Middle East → APAC). You’ll own that trajectory: lead the infrastructure team, set the GitOps and automation standards, and be the technical authority on how the platform is built, deployed, and operated. This is a hands-on leadership role — you’ll be in the architecture decisions and in the code, not just reviewing other people’s PRs.
About the Product
Production cybersecurity infrastructure — Kubernetes-based, AWS-primary, with real security and compliance constraints baked in from day one. The platform serves actual security operations, which means reliability and hardening aren’t process requirements, they’re product requirements.
The stack: AWS is the current foundation — EKS, and the supporting services that go with a production Kubernetes environment. GitOps runs on ArgoCD with Helm and Terraform. CI/CD, scripting, and observability (Prometheus, Grafana, ELK) complete the platform layer. Azure and GCP are on the roadmap, not in scope today — but the architecture decisions being made now need to accommodate them.
What You’ll Be Doing
- Lead the infrastructure team: set technical direction, run architecture reviews, and own the engineering standards for cloud infrastructure and DevOps practices
- Own and evolve the GitOps stack — ArgoCD, Helm, Terraform — and drive zero-touch deployment automation across environments
- Architect and execute multi-region expansion: US is live; EU, Middle East, and APAC follow — each with its own latency, compliance, and data residency constraints
- Build and maintain CI/CD pipelines that support backend, data, and AI teams shipping safely at speed
- Harden AWS infrastructure to meet the security and compliance requirements of a cybersecurity product; establish the patterns that carry forward into Azure and GCP
- Drive observability across the platform — Prometheus, Grafana, ELK — and own the reliability posture: SLOs, incident response, operational trade-offs
- Participate in distributed systems architecture decisions alongside backend and data engineering leads
Leadership & Management
This is a team lead role with direct ownership of people, not just systems. You’ll define how the infrastructure team operates — hiring bar, technical standards, on-call culture, knowledge sharing. The expectation is that the team gets stronger under your lead, not just the infrastructure.
What We Expect
Must-Have
- 4+ years of hands-on DevOps, Platform, or Infrastructure Engineering
- 1+ years in a technical lead or team lead capacity — real accountability for team output and standards
- Production AWS experience — deep, not broad; you know where the sharp edges are
- ArgoCD and GitOps in production — must
- Strong Kubernetes and Helm experience at production scale
- Solid Terraform, CI/CD, and scripting (Bash, Python, or Go)
- Monitoring and logging stack in production: Prometheus, Grafana, ELK
- Ability to reason about multi-region architecture trade-offs — latency, data residency, failover
- Strong ownership mindset; able to operate with high autonomy and communicate clearly across engineering teams
- English B2+
Nice to Have
- Azure or GCP hands-on experience — relevant given the multi-cloud roadmap
- Background in cybersecurity, high-security SaaS, fintech, or data platforms
- Experience supporting R&D teams in fast-growing environments
- Incident response and production on-call ownership
Why This Role Is Worth Your Time
- Multi-region expansion is a concrete, near-term project — not a future promise; US is live, EU and beyond are next
- You’ll set the infrastructure standards for a cybersecurity product where the bar for reliability and security is defined by the domain, not by policy
- High autonomy, strong technical peers, and direct involvement in architecture decisions that span the full engineering org
- Clear path from team lead to infrastructure architect as the platform and team scale
