Drimva

Google

Staff Security Engineer, Trust and Safety Intel Security Engineering

Seattle, WA, USA +1 · Staff · Full-time · Posted Oct 20, 2026

Location
Seattle, WA, USA
Washington D.C., DC, USA
Experience
8 years in security assessments, design reviews, or threat modeling; 8 years in security engineering, computer and network security, and security protocols; 8 years of coding; 3 years of technical team leadership or enterprise technical risk analysis.
Education
Bachelor's degree or equivalent practical experience.

About the job

Leads detection and response for severe AI-related security incidents and develops intelligence tools, processes, and signals to identify and mitigate emerging security risks.

What you'll do

  • Lead incident preparedness, including cross-Google relationships, playbooks, escalation procedures, and process improvements.
  • Support urgent detection and response for critical AI security issues, including business-hours on-call incident management.
  • Develop tools, processes, and signal sources to detect, enrich, and analyze security issues; inform stakeholders and mobilize risk mitigation.

What they ask for

  • Bachelor's degree or equivalent practical experience.
  • 8 years of experience with security assessments, security design reviews, or threat modeling.
  • 8 years of experience in security engineering, computer and network security, and security protocols.
  • 8 years of coding experience in one or more general purpose languages; 3 years leading teams technically or leading technical risk analysis in an enterprise environment.

Nice to have

  • 8 years of experience in a security field such as application security, network security, or incident response.
  • Experience working with product teams to remediate identified issues.

Pay

$207000 - $300000 USD base salary

AI focus

Leads detection and response for severe GenAI-related security incidents and develops intelligence capabilities focused on GenAI products and emerging frontier AI risks.

Model-written summary · the original posting is authoritative

First seen Oct 21, 2026 · Last verified Nov 5, 2026 (UTC)