Skip to main content

Staff Cloud Security Engineer

Posted today

quizletMillbrae (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: As a Staff Cloud Security Engineer at Quizlet, you will define technical direction and implement security improvements across cloud infrastructure and public services, with a focus on GCP and GKE. You’ll harden environments, automate controls, and strengthen edge protections, turning data-protection requirements into concrete, auditable measures. Collaborating with infra, identity, and engineering teams, you’ll enable secure, scalable AI-enabled learning tools for a global user base. This is a chance to shape security at scale and impact learners worldwide. Compensation / Benefits Hybrid work in San Francisco 20 vacation days health, dental, and vision insurance 401k with company match Paid Family Leave Volunteer time off (40 hours annually)
Responsibilities: Lead cloud and Kubernetes security improvements including workload identity, policies, and network protections. Operate cloud security tooling, prioritize findings by risk, remediate vulnerabilities, and harden container images. Enhance WAF rules, rate limits, bot defenses, and anomaly detection to balance security with user experience. Build maintainable security automation and review infrastructure as code for secure adoption. Create self-service patterns for securely exposing new services and connecting AI tools/MCP integrations to approved data. Partner with engineering to implement data-protection controls with CI checks and evidence of effectiveness. Guide cross-team security decisions, mentor engineers, and support incident response and on-call responsibilities.
Key requirements: 8+ years working with public-cloud infrastructure 5+ years in cloud security engineering Experience securing GCP and GKE environments Hands-on experience securing production cloud infrastructure and Kubernetes workloads Experience using infrastructure as code (e.g., Terraform) Programming experience in Python or Go for security automation Ability to translate security requirements into practical controls and tests Proven record of leading complex technical work across teams and communicating tradeoffs collaboration clear communication mentorship GCP GKE workload identity

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this