Senior Attack Engineer, GCP

Horizon3

1d•$206,278 - $242,680•Remote

About The Position

Horizon3 is seeking a Senior Attack Engineer with deep Google Cloud Platform (GCP) expertise to build the next generation of cloud attack capabilities for its NodeZero platform. The role owns development of GCP attack content from the ground up, including researching Google Cloud services, identifying attack paths and misconfigurations, developing offensive capabilities, and shaping how NodeZero assesses GCP environments at scale. The position serves as a technical lead in defining Horizon3’s GCP offensive security strategy and influencing how GCP attacks are integrated into the platform. The engineer will lead GCP attack research and build, validate, and maintain production-quality Python attack capabilities across cloud services. The work includes chaining weaknesses into realistic attack paths with reliable proof of exploitability and actionable customer outcomes, setting technical direction and priorities, collaborating with Product and Engineering, and documenting research and design decisions. The role also includes reviewing designs and code, mentoring engineers, and contributing to internal enablement and suitable external technical content. Horizon3 is a fully remote cybersecurity company. The job may require up to 10% travel. The company describes its culture as collaborative and inclusive, with competitive compensation, equity and benefits.

Requirements

Deep hands-on experience with GCP security and offensive cloud operations, including reasoning about IAM permissions, service identities, trust, and resource access.
Expert understanding of cloud attack paths and cloud-native security concepts.
Strong Python engineering skills and experience turning security research or manual techniques into dependable, production-quality automation or product capabilities.
Passion for building products, not just finding vulnerabilities.
10+ years of professional software engineering and/or offensive security experience.
Experience with cloud penetration testing, red teaming, offensive security research, or building cloud security products.
A record of owning ambiguous technical work, making sound trade-offs, and communicating clearly with technical and non-technical partners.
Strong written communication and a habit of documenting research and design decisions.

Nice To Haves

Experience with cloud privilege escalation and identity attacks.
Familiarity with AWS, Azure, or OCI offensive security.
Experience integrating security research into production software.
Experience with GKE, Kubernetes, Terraform, gcloud, Google Cloud APIs, or cloud-native CI/CD.
Contributions to security research, open-source projects, conference talks, or vulnerability disclosure.
Experience mapping cloud attack coverage to frameworks such as MITRE ATT&CK for Cloud.

Responsibilities

Lead research into GCP attack paths, identity and trust relationships, service misconfigurations, and emerging attacker techniques.
Design, implement, and validate production-quality Python attack capabilities across GCP IAM, service accounts and workload identities, compute, Kubernetes/GKE, storage, databases, secrets, networking, and other cloud-native services.
Chain individual weaknesses into realistic attack paths with reliable proof of exploitability and clear, actionable customer outcomes.
Set technical direction for GCP attack coverage, identify gaps, prioritize work with Product and Engineering, and translate research and customer needs into a sequenced roadmap.
Build and maintain safe, repeatable attack logic and supporting tests; investigate failures and improve reliability, precision, and maintainability.
Collaborate with software engineers, attack engineers, and offensive security SMEs to bring new capabilities into production.
Document research findings, attack methodologies, and technical design decisions.
Review designs and code, share domain expertise, and mentor engineers developing GCP attack content.
Contribute to internal enablement and, where appropriate, external research or technical content.