Two candidates describe Google Security Engineer interviews that mixed application security scenarios, live scripting and SSO protocol questions such as SAML, OAuth and OIDC. Both reported no offer.
$172K
Avg. Base Comp
$281K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two candidates described Google Security Engineer interviews, and both ended without an offer. The second account is brief, but together they point to where the questions concentrated.
The first candidate, who came from an application security background, expected a grilling and found a conversational technical round. The engineer opened with his own background and team, and the questions centered on practical application security and how the candidate reasoned through attack and defense scenarios. The interviewer wanted that reasoning spoken aloud, not just a final answer. Some questions covered infrastructure penetration testing, and the candidate came to see the role as broader than pure AppSec. The round closed with a live script or algorithm task. A mistake, then a flustered second one, ended the exercise early.
The second candidate reached a second round and said the questions centered on authentication and identity, specifically SSO protocols such as SAML, OAuth and OIDC. The interviewers were friendly but seemed rushed, and no word came back afterward.
Taken together, the reports suggest preparing in three areas: talking through security scenarios from both the attacker's and the defender's side, writing small pieces of code under time pressure while staying calm after an error, and being able to explain SSO protocols clearly. Check the posting for scope beyond your own specialty, since the first candidate found the role wider than expected.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Google process.
The interview itself was pretty straightforward, and the people interviewing me were friendly. I made it through to a second round, which was the furthest I got. The questions I remember centered on authentication and identity, specifically SSO protocols like SAML, OAuth, and OIDC. The interviewers seemed busy and a little rushed, and I never heard back after the second round, so I took that as a no.
Prep tip from this candidate
Be ready to explain SSO protocols and how SAML, OAuth, and OIDC differ from one another, since that's what the interviewers focused on. Expect the second round to go deeper than the first.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Google
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| String Shift | |
| Find Bigrams | |
| Minimum Change | |
| Good Grades and Favorite Colors | |
| Find the First Non-Repeating Character in a String | |
| Complete Addresses | |
| Friendship Timeline | |
| Find the Index with Equal Left and Right Sum | |
| The Brackets Problem | |
| N-gram Dictionary | |
| Level Of Rain Water In 2D Terrain | |
| Nearest Common Ancestor | |
| Basic Regex | |
| Cyclic Detection | |
| Sort Strings | |
| Most Repetition | |
| Longest Increasing Subsequence | |
| Term Frequency | |
| Radix Addition | |
| Target Indices | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| Swapping Nodes | |
| Stop Words Filter | |
| Find the Missing Element | |
| Priority Queue Using Linked List | |
| Automatic Histogram | |
| Prime Numbers Identification | |
| Merge N Sorted Lists |
Synthesized from candidate reports. Individual experiences may vary.
One candidate began with an HR screen in which the recruiter explained the hiring steps and what would come next, so the rest of the process held no surprises. In that account, the call set out the stages ahead rather than testing technical depth.
The same candidate had a technical round with an engineer who first shared his background and team. Questions focused on application security, attack and defense scenarios, and some infrastructure penetration testing. The interviewer valued reasoning spoken aloud. The round ended with a live script or algorithm task, and two mistakes in a row led the interviewer to stop it.
A different candidate reached a second round, the furthest they got, and remembered questions on authentication and identity, specifically SSO protocols such as SAML, OAuth and OIDC. The interviewers were friendly but seemed rushed, and the candidate heard nothing after the round, which they took as a rejection.
