Use AI to find and auto-fix vulnerabilities across Google Cloud's codebase

Google Cloud's security engineering team is hiring a software engineer to build AI-based pipelines that discover novel vulnerabilities across billions of lines of code and automate fixes before they reach production. The role blends backend API development for developer-facing security tools with applying ML/AI to security assessment workflows, at a junior-to-mid level (2 years of software development experience, or 1 with an advanced degree).

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google's standard SWE loop: phone screen(s) with coding, then onsite/virtual onsite with coding, system design, and Googleyness/leadership behavioral rounds.

What this interview tests

Secure backend API design for developer-facing tools
AI/ML pipelines for vulnerability discovery and automated remediation
Distributed systems security assessment and guardrails
System telemetry and security data analysis
Mentoring and cross-stakeholder alignment on security milestones

Common question themes

Design a secure API for a developer-facing security tool

Sketch an automated pipeline that uses AI to find and fix a class of vulnerabilities

How would you assess and harden the security of a given distributed system design

A time you found a gap in a system through log/telemetry analysis and fixed it durably

Fundamentals: secure coding practices and vulnerability analysis basics

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Google Software Engineer interviews

All Google interviews