at Google
Location
New York, NY, USA
Compensation
$123k–$175k USD
Type
full time
Posted
1 months ago
Market range · company + function + seniority
p25 · target · p75 · n=64
Posted $175k · well below market
Tailor your résumé to this role in 30 seconds.
Free account · ATS keyword check · per-job bullet rewrite by Claude.
The PRISM (Proactive Access Risk Intelligence and Security Mitigations) team is part of the Access Security Team organization. We proactively focus on uncovering broad risks across the access landscape, gathering and distilling access intelligence from internal systems to fortify security, and deploying comprehensive measures to ensure every angle of access is understood and protected, including enforcing security invariants to prevent future regressions. We are also building the next-generation taxonomy for qualifying access risk, prototyping end-to-end pipelines to uncover security risks associated with agentic identities, and architecting secure-by-default solutions scaled across the enterprise.
As a Security Engineer, you will be working on security research and risk mitigation systems, help scope security problems, and contribute to projects across product areas to transform how Google manages and eliminates internal access risk.
In this role, you will be at the forefront of redefining Google’s internal access landscape. You will not just respond to risks; you will be anticipating them by building the next-generation taxonomy of access risk and architecting 'secure-by-default' solutions that protect our most critical infrastructure. From modeling complex attack paths to securing the rise of agentic identities, you will lead high-impact projects that transform how Google proactively manages risk at an enterprise scale.Individual pay is determined by factors including job-related skills, experience, and relevant education or training.More open roles at Google
Hiring velocity, headcount trend, and every open posting on one page.
Open postings ranked by description similarity — useful if this role isn't quite right.