Google behavioral interview: Googleyness and Leadership, plus the four hiring attributes
Every interviewer writes standardized feedback that maps to these attributes. The G&L round covers Googleyness (comfort with ambiguity, bias to action, collaboration) and emergent leadership: stepping up when the situation needs it.
| Progress | Principle | Your story |
|---|---|---|
| General Cognitive AbilityDiving deep · Ambiguity and judgment | Write a story | |
Sample answer: Tell me about a problem where the obvious cause was not the real oneWhether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Situation Our product catalogue service had short latency spikes roughly every ten minutes, where the slowest requests jumped from about 200 milliseconds to four seconds. The team had blamed the database for weeks and was planning to move to larger database servers. Task I was on call that week and wanted to be sure the expensive fix would actually work before we paid for it. Action First I lined up the spikes against database metrics, and the database was not busy during them; queries were slow because many arrived at once. So I looked at what sent them. Our service cached product data for exactly ten minutes. When we deployed, every instance filled its cache at the same moment, so the entries also expired at the same moment, and thousands of requests went to the database together. I confirmed it by reading the cache code and by reproducing the pattern on staging with a load test: same ten-minute spikes. The fix was small. I added a random spread of plus or minus two minutes to each entry's expiry and made sure only one request per key reloaded data while others waited for it. I tested it on staging, then rolled it out to one instance before the rest. Result The spikes disappeared; the slowest requests stayed under 300 milliseconds. We cancelled the database upgrade, which would have cost more than the rest of our yearly hosting for that service. I wrote a short note on synchronised cache expiry, and we added it to our design review checklist. Tip: Show you went to the data or the code to find the real root cause. Diving deep: weak answer, follow-ups and level differences | ||
| Role-Related Knowledge and ExperienceDiving deep · Ambiguity and judgment | Write a story | |
Sample answer: Tell me about a problem where the obvious cause was not the real oneWhether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Situation Our product catalogue service had short latency spikes roughly every ten minutes, where the slowest requests jumped from about 200 milliseconds to four seconds. The team had blamed the database for weeks and was planning to move to larger database servers. Task I was on call that week and wanted to be sure the expensive fix would actually work before we paid for it. Action First I lined up the spikes against database metrics, and the database was not busy during them; queries were slow because many arrived at once. So I looked at what sent them. Our service cached product data for exactly ten minutes. When we deployed, every instance filled its cache at the same moment, so the entries also expired at the same moment, and thousands of requests went to the database together. I confirmed it by reading the cache code and by reproducing the pattern on staging with a load test: same ten-minute spikes. The fix was small. I added a random spread of plus or minus two minutes to each entry's expiry and made sure only one request per key reloaded data while others waited for it. I tested it on staging, then rolled it out to one instance before the rest. Result The spikes disappeared; the slowest requests stayed under 300 milliseconds. We cancelled the database upgrade, which would have cost more than the rest of our yearly hosting for that service. I wrote a short note on synchronised cache expiry, and we added it to our design review checklist. Tip: Show you went to the data or the code to find the real root cause. Diving deep: weak answer, follow-ups and level differences | ||
| LeadershipCollaboration and inclusion | Write a story | |
Sample answer: Describe a project that needed several teams. How did you get them aligned?Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other. Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me. Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part. Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs. Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences | ||
| GoogleynessResilience and courage · Ambiguity and judgment | Write a story | |
Sample answer: Describe a setback that almost made you give up. What kept you going?Whether you keep going after something goes wrong, without denial or blame, and whether you have the courage to make or support a hard call. They want to see how you kept yourself and others steady and what changed because you persisted. Situation My team rebuilt the checkout page of our shopping app to make it faster. We launched it twice, and both times we rolled it back within a day: first for a payment bug on one browser, then for a drop in completed orders we could not explain. Leadership was close to cancelling the project. Task I was the lead engineer. Morale on the team was low, and I had to decide whether to argue for a third attempt and, if so, make sure it would not fail the same way. Action I took a day to understand both failures. The browser bug was simple; the order drop was the real issue. From session recordings, I found that the new page hid the delivery-date selector behind a tap, and people abandoned when they could not see the date. Neither failure meant the rebuild was wrong; both meant our launch process was. I wrote a short plan for a third attempt with three changes: an automated test across our top five browsers, a gradual rollout starting at five percent with a comparison of completed orders against the old page, and an automatic switch back if orders dropped more than one percent. I presented it to leadership and said plainly that if this attempt failed, I would recommend stopping. I also talked to the team openly about the two rollbacks so nobody carried the blame alone. Result The third launch went to a hundred percent over two weeks with no rollback. Page load time fell by 40 percent and completed orders rose by about two percent. The gradual rollout with an automatic switch back became the standard for every customer-facing launch on our team. Tip: Show you kept going through a setback or made an unpopular call that was right. Resilience and courage: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Google behavioral interview based on?
Googleyness and Leadership, plus the four hiring attributes: General Cognitive Ability, Role-Related Knowledge and Experience, Leadership, Googleyness. Every interviewer writes standardized feedback that maps to these attributes. The G&L round covers Googleyness (comfort with ambiguity, bias to action, collaboration) and emergent leadership: stepping up when the situation needs it.
How do I answer Google questions on "General Cognitive Ability"?
Whether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Show you went to the data or the code to find the real root cause. A typical question: Tell me about a problem where the obvious cause was not the real one
How do I answer Google questions on "Role-Related Knowledge and Experience"?
Whether you go to the data and the code yourself instead of accepting the first explanation, and whether you can explain a technical cause simply. They also want to see that you checked your theory before acting on it. Show you went to the data or the code to find the real root cause. A typical question: Tell me about a problem where the obvious cause was not the real one