Cloud Security Engineer

· Design and review AWS security architecture; establish secure-by-default patterns across AWS, Azure, and GCP · Identify and remediate security issues using cloud security posture management tools (Wiz) and manual assessments across cloud and data environments · Define and implement security controls for AI tooling, containerized workloads (Amazon EKS/Kubernetes), and cross-platform integrations (Snowflake, Databricks) · Conduct architecture reviews, design reviews, and threat modeling for new systems and services · Harden GitHub repositories, GitHub Actions CI/CD pipelines, and Terraform infrastructure-as-code for security · Assess new cloud services and recommend controls before adoption; establish reference patterns and guardrails for engineering and data teams · Collaborate across Platform Engineering, Cloud Operations, Data Engineering, Networking, and Security teams to embed security best practices

Our client is seeking a Cloud Security Engineer with 6-8 years of experience to design, implement, and harden security controls across multi-cloud and data platforms. You will establish security standards, conduct architecture reviews, and collaborate with engineering teams to embed security into cloud infrastructure and CI/CD pipelines., · 6-8 years of cloud security or related infrastructure security experience · Strong expertise in AWS security architecture, IAM, and cloud security posture management · Proficiency in Kubernetes/Amazon EKS hardening and infrastructure-as-code (Terraform) · Hands-on experience with cloud security tooling, particularly Wiz; familiarity with Azure and GCP security · Programming or scripting capability in Python, TypeScript, Go, or similar languages · Knowledge of security frameworks (NIST CSF, CIS Benchmarks, ISO 27001) and data platform security (Snowflake, Databricks) · Experience securing CI/CD pipelines, GitHub workflows, and container orchestration platforms · Ability to work independently and communicate security concepts effectively across technical and non-technical stakeholders