Google Behavioral Interview Cheat Sheet: Googleyness, GCA & the Four Attributes

Updated June 30, 2026 · techinterview.org

Google Behavioral Interview Cheat Sheet: Googleyness, GCA & the Four Attributes

Every Google interview loop, regardless of role or level, gets scored against the same four attributes: General Cognitive Ability, Role-Related Knowledge, Leadership, and Googleyness. That structure has held steady for more than a decade, but two of the four dimensions changed shape after 2018, and most of the prep advice circulating online still describes the pre-2018 version. This is the current cheat sheet: how the evaluation actually works, what each attribute tests now, the probing questions interviewers ask under each one, and the story bank you need to walk in prepared.

How Google’s behavioral evaluation works

A typical onsite loop runs four to six interviews, mixing coding or domain-specific rounds with one or two rounds built around behavioral questions, plus a dedicated Googleyness-style round at many levels. Each interviewer is briefed to probe one or two of the four attributes, not all of them at once, and each interviewer writes independent feedback immediately after the round, before comparing notes with anyone else. That feedback includes a written narrative plus a rating on a standard scale running from No Hire through Strong Hire.

The decision does not sit with your interviewers. It sits with a hiring committee made up of Googlers who were not in the room for any of your rounds. Committee members read the full packet on their own time, score it independently, then meet to discuss and reach a decision together. That structure exists specifically to stop a single strong or weak personality in the room from swinging an outcome, but it has a real consequence for candidates: your interview answers have to be self-contained. The committee member reading your feedback packet has no memory of your tone, your handshake, or the joke you made at the start of the call. They have the interviewer’s notes and your rating. If a story lands well in the room but doesn’t translate onto paper, it does not help you.

The committee can also move your level up or down from what the recruiter targeted going in, based on how the loop performed relative to the bar for each level. A candidate targeting a mid-level role who shows senior-level scope and judgment across the loop can get bumped up; the reverse also happens. That’s one more reason the stories you tell need to carry explicit scope: who was affected, how large the decision was, and what would have happened if you hadn’t acted.

The four hiring attributes

Coding and system-design rounds map mostly to Role-Related Knowledge with some General Cognitive Ability mixed in. Behavioral rounds map mostly to Leadership with some Googleyness. The dedicated culture round, where one still exists in the loop, maps almost entirely to Googleyness with a little Leadership. Knowing which attribute a given question is fishing for tells you which story from your bank to reach for.

General Cognitive Ability (GCA)

What it actually means: GCA used to be tested with brainteasers — how many golf balls fit in a school bus, why manhole covers are round. Bock said in 2013 that this approach was a waste of time because it didn’t predict job performance and mostly let interviewers feel clever. GCA today means something closer to structured reasoning: can you learn quickly, break an unfamiliar problem into parts, and reason out loud through ambiguity without a script.

What interviewers write in feedback: notes on whether you clarified the problem before diving in, whether your reasoning had a visible structure an outsider could follow, whether you adjusted when new information contradicted your first instinct, and whether you reached a defensible conclusion rather than just an answer.

Probing questions: “Walk me through a project you’ve worked on. Why did you make the technical choices you made?” “What would you measure to evaluate the success of [a specific product]?” “How would you approach [a deliberately ambiguous problem]?” “Tell me about a time you had to learn something unfamiliar quickly in order to solve a problem.”

Story prompt: pick a story where you were handed a problem you hadn’t seen before, with incomplete information, and can narrate your reasoning step by step — not just the outcome, but the order in which you ruled things out.

Role-Related Knowledge (RRK)

What it actually means: domain-specific competence for the actual job — coding ability for an engineering role, market and pricing judgment for a strategy or finance role, systems fluency for an SRE role. Most of the RRK signal is generated in the technical or domain-specific rounds rather than the behavioral ones, and several people who’ve been through committee describe it as functioning more like a threshold you have to clear than the attribute that differentiates a Hire from a Strong Hire once you’re through the loop.

What interviewers write in feedback: specific technical or domain judgments you made, the depth of your reasoning about tradeoffs within your field, and whether your expertise held up under follow-up questions from someone who knows the domain well.

Probing questions: “Tell me about a technical or domain decision where you evaluated more than one approach.” “Describe a project where your specific expertise changed the outcome.” “Where did you push back on a decision because you knew the domain better than the person proposing it?” “What’s something in your field you had to teach yourself on the job?”

Story prompt: choose a story that shows a call only someone with your specific expertise could have made, and be ready to explain the alternative approach you rejected and why.

Leadership

What it actually means: Leadership at Google is not restricted to people who manage direct reports. The rubric explicitly covers emergent leadership — stepping up to drive an outcome without a formal title or mandate to do so. Google works cross-functionally by default, so a strong Leadership signal often comes from an individual contributor who influenced peers, other teams, or a decision above their pay grade without anyone assigning them the job.

What interviewers write in feedback: the scope of people or teams your decision affected, how you built buy-in from people who didn’t report to you, and whether you owned the outcome even when you had no authority to force it.

Probing questions: “Tell me about a time you led a project without any formal authority over the people involved.” “Describe a time you had to convince a peer or another team to change direction.” “Tell me about a decision you made that affected people outside your immediate team.” “How did you handle a disagreement with someone more senior than you?”

Story prompt: prepare a story where you drove an outcome across a team boundary while holding no formal power over the people you needed, and can name the specific actions that brought them along.

Googleyness

What it actually means: before 2018, Googleyness was a loose culture-fit conversation: “what’s a hobby that says something about how you think,” “tell me something most people don’t know about you.” Interviewers were told to look for a vibe, and the rubric was subjective enough to let it slide toward matching candidates who resembled the interviewer. A run of internal events in 2017 and 2018 — including the fallout from an internal memo and its author’s termination, the 2018 walkout over how the company handled harassment complaints, and an internal push around diversity and inclusion — put pressure on that vibe-check model, alongside research showing loosely-defined culture-fit assessments can hurt diversity outcomes without adding predictive value. The result was a tightened rubric built around four specific sub-dimensions: comfort with ambiguity, bias for action, collaborative orientation, and intellectual humility. Some interviewer training material has moved away from the word “Googleyness” entirely in favor of “behavioral round,” but the underlying assessment is the same four things.

What interviewers write in feedback: notes tied directly to one of the four sub-dimensions — did the candidate move forward with incomplete data, did they name a tradeoff between two imperfect options and choose one, did they describe genuinely working through a disagreement rather than steamrolling it, did they name something they were wrong about without minimizing it.

Probing questions: “Tell me about a time you had to make a decision without enough data.” “Tell me about a time you had to choose between two imperfect options.” “Tell me about a time you disagreed with a colleague and had to find a path forward together.” “Tell me about a time you were wrong about something significant.”

Story prompt: prepare a story where you made real progress despite missing information or an unresolved disagreement with someone, and be ready to say plainly what you got wrong and what you’d do differently now.

Building your Google story bank

Unlike Amazon’s 16 named Leadership Principles, Google’s rubric is four attributes with a handful of sub-dimensions underneath Googleyness and Leadership. That means fewer buckets to cover, but each bucket needs more depth, because a committee member reading a thin story has nothing else to go on. Aim for 8-10 stories that collectively touch all four attributes, with at least two options for GCA and at least two for Leadership, since those tend to get probed most often across a typical loop.

For each story, prepare:

• Situation: one or two sentences of context — the team, the timeframe, what was at stake. Stop there. A long setup eats the time you need for the part interviewers actually score.
• Task: the specific thing you personally owned, not the team’s broader goal. Name a deadline, a metric, or a decision that was yours.
• Action: what you specifically did, in first person. This is where most of your answer should live — the two or three real decisions you made, the tradeoffs behind them, and what you’d say if someone asked “why that and not the alternative.”
• Result: a measurable outcome, plus how you measured it. “It went well” invites a follow-up you won’t have an answer for.
• Reflection: one genuine thing you’d do differently. This single line is often what separates a Hire from a Strong Hire on Googleyness, because intellectual humility is scored explicitly.

Build a simple matrix before your loop: rows are your 8-10 stories, columns are the four attributes plus the Googleyness sub-dimensions. Mark which cells each story covers. Any attribute with no coverage is a gap you need to fill before onsite, not something to discover mid-interview.

Common pitfalls

• Treating GCA as a puzzle to solve. There is no clever trick answer anymore. The interviewer is scoring how you structure the problem, not whether you land on the “right” number.
• Treating Googleyness as a personality contest. “Show personality,” “be quirky,” and “demonstrate culture fit” are pre-2018 advice. The round is rubric-driven now, and the four sub-dimensions are what get scored, not whether you seem fun to grab lunch with.
• Using “we” instead of “I.” Committee members can’t tell what you personally did from a story told entirely in the collective. Be specific about your role versus the team’s.
• Leadership stories that describe a title, not an action. “I was the tech lead” isn’t a Leadership story by itself. The interviewer needs the moment you influenced someone who didn’t have to listen to you.
• Assuming context carries between rounds. Each interviewer writes independent feedback and the committee reads the packet cold. Don’t reference “as I mentioned earlier” or assume a later interviewer knows what an earlier one heard.
• No real reflection. A polished failure story that ends without a genuine lesson reads as rehearsed rather than as real self-assessment, and intellectual humility is graded directly under Googleyness.

Frequently Asked Questions

See also: Tell Me About Yourself • Tell Me About a Time You Failed • Animal, Tree, and Superpower Questions • The Cracking the Coding Interview Effect