Senior Cloud Security Engineer

OpenKrill; United States; À distance; USD 150 000 - 190 000; Plein temps

Résumé du poste

OpenKrill is seeking a Senior Cloud Security Engineer to secure cloud environments by default. You will design guardrails, automation, and monitoring across AWS, GCP, and Azure with a DevOps mindset, integrating security into pipelines and IaC.

Work closely with platform, infrastructure, and compliance teams to build secure reference architectures, automate protections, and lead incident response for cloud environments across North America.

Qualifications

• Hands-on experience securing at least two major clouds (AWS, GCP, Azure).
• Knowledge of CIS Benchmarks and provider security foundations.
• Ability to write automation and maintainable infrastructure code.
• Strong communication to explain risk to engineers and partners.

Responsabilités

• Own security posture across AWS, GCP, and Azure with consistent controls.
• Design secure reference architectures and reusable patterns for cloud environments.
• Embed security into IaC with policy as code and pre-deploy checks.
• Secure CI/CD pipelines and software supply chain with guardrails and key management.
• Implement least-privilege IAM across clouds and manage federation.

Connaissances

DevOps background

Cloud security practices

Scripting in Python/Go

IaC (Terraform/OpenTofu)

Strong communication

Multi-cloud security

Outils

Prowler

Checkov

Trivy

OPA

Falco

Description du poste

SENIOR CLOUD SECURITY ENGINEER

THE ROLE

We're hiring a Senior Cloud Security Engineer to make our cloud environments secure by default. You'll design and build the guardrails, automation, and detection that keep our infrastructure defensible across multiple cloud providers.

You'll do it with a DevOps mindset: writing code, shipping changes through the same pipelines our engineers use, and building paved roads teams want to adopt, rather than handing down policy from the outside.

This role partners closely with platform and infrastructure engineering, customer support, and delivery teams, as well as IT and compliance.

WHAT YOU'LL DO

• Own the security posture of our cloud environments across Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure, applying consistent controls across providers.
• Design secure reference architectures and reusable patterns — account and project structure, network segmentation, encryption and key management, secrets management — that teams can adopt instead of reinventing.
• Build security into Infrastructure as Code (IaC) through hardened modules, policy as code, and pre-deploy checks, so misconfigurations are caught before they reach production.
• Secure Continuous Integration / Continuous Delivery (CI/CD) pipelines and the software supply chain: pipeline permissions, secrets handling, artifact integrity, and short-lived workload identity in place of long-lived keys.
• Design and enforce least-privilege Identity and Access Management (IAM) across clouds, including role design, federation with our identity provider, and periodic access reviews.
• Write code and scripts to automate security controls, remediation, and evidence collection — if you do something twice, you automate it the third time.
• Operate and tune Cloud Security Posture Management (CSPM) and cloud-native security services, and drive findings through to remediation with owning teams.
• Build logging and detection for cloud control-plane and workload activity, and lead the cloud side of incident response.
• Contribute security controls and evidence to our compliance posture (System and Organization Controls 2, or SOC 2, ISO 27001, etc.).

WHAT YOU'LL NEED (REQUIRED)

• A DevOps foundation — you've worked in a DevOps, Site Reliability Engineering (SRE), or platform engineering role, and you've built and operated production infrastructure and CI/CD pipelines yourself, not just reviewed them.
• Hands-on production experience securing at least two major cloud providers (AWS, GCP, or Azure), and a clear understanding of how their identity, networking, and logging models differ.
• Deep knowledge of cloud security best practices — for example, the Center for Internet Security (CIS) Benchmarks and each provider's security foundations guidance — and the judgment to apply them pragmatically rather than as a checklist.
• Fluency in proven cloud security patterns: least-privilege IAM and workload identity, network segmentation and private connectivity, encryption and key management, secrets management, centralized logging, and preventive guardrails (for example, AWS Service Control Policies or GCP Organization Policies).
• Strong coding and scripting skills in at least one general-purpose language (for example, Python or Go) plus shell scripting; you write automation other engineers can read and maintain.
• Hands-on experience with IaC (for example, Terraform or OpenTofu) and with embedding security checks into it.
• Strong communication skills — you work directly with engineers and can explain risk in terms they'll act on.

NICE TO HAVE

• Familiarity with open-source cloud security tooling (for example, Prowler for posture assessment, Checkov or Trivy for IaC and container scanning, Open Policy Agent (OPA) for policy as code, Falco for runtime detection).
• Container and Kubernetes security experience (Amazon EKS, Google Kubernetes Engine, or Azure Kubernetes Service), including admission control and runtime policy.
• A relevant cloud security certification (for example, AWS Certified Security – Specialty, Google Professional Cloud Security Engineer, Microsoft Azure Security Engineer Associate, or Certified Cloud Security Professional, CCSP).
• Experience securing SaaS and developer platforms, such as identity providers and GitHub organizations.
• Experience supporting a SOC 2, ISO 27001, or similar program, including compliance automation platforms.
• Hands-on cloud incident response or forensics experience.

WHAT SUCCESS LOOKS LIKE (FIRST 90 DAYS)

• You've mapped our cloud footprint across providers — accounts and projects, identities, internet exposure, and sensitive data stores — and identified the highest-priority risks with a remediation plan.
• Baseline guardrails, centralized logging, and posture monitoring cover every cloud account and project, with findings routed to the teams that own them.
• Security checks run automatically on infrastructure changes in CI/CD, and engineers know how to engage you early on new infrastructure work.

LOCATION AND WORK MODEL

Remote in North America