Cloud Security Engineer

About this role

A little about us incident.io is the AI software reliability platform trusted by engineering teams at Netflix, Etsy, and 2,000+ companies who can't afford downtime. The stakes are real, the talent is insane, and somehow it's a genuinely lovely place to work. We all pull our weight, go the extra mile, and put in the bit of magic most companies don't have time for, all while having fun and never taking ourselves too seriously.

We've raised $100+ million from Index Ventures, Insight Partners, and Point Nine, and we're growing fast. There's never been a better time to join. The role in one line Being a Cloud Security Engineer at incident means being the person who keeps the one thing customers rely on when their systems are on fire both up and safe, turning “is this secure?” into “yes, and here’s the proof.” What that looks like day to day As a Cloud Security Engineer at incident, you own the security of the cloud infrastructure that runs our platform: how it’s built, hardened, monitored and defended.

It’s a genuinely varied role. One day you’re tightening IAM across our Google Cloud projects, the next you’re building a Terraform guardrail so engineers get a safe path instead of a ticket, the next you’re leading an investigation into something odd in the audit logs. You’ll own cloud posture and hardening across GCP and GKE, identity and access, security as code in our Terraform and CI/CD pipelines, detection and response, isolation of customer data in our multi-tenant platform, and the cloud-side controls around our AI features.

We formed our security team this year and there are three of us. We’re hiring a Cloud Security Engineer to give the team real depth in cloud, which means little process, no approval chains, and your fingerprints on everything. We say yes wherever we genuinely can, and you’ll have the authority to block a release when it matters. We run on Google Cloud and AWS, with Kubernetes, Terraform, Go, Postgres and TypeScript/React.

We lean on Claude and other LLMs to move faster. Who you are You’ve got deep, hands-on cloud security experience, ideally on Google Cloud. Strong AWS or Azure depth that transfers is fine. You design least-privilege IAM properly, and you’ve secured Kubernetes or container platforms in production. You write code to fix problems, not just report them. Terraform is second nature. You’ve built cloud detection or investigated cloud incidents, and you enjoy following the thread until you find the answer.