How Google Scores Behavioural Interviews (2026)

Google behavioural interviews are commonly described as scoring 6 signals: Comfort with ambiguity, Bias to action, Collaboration, Emergent leadership, Intellectual humility, Doing the right thing for users. On top of the general behavioural rubric, each one is judged on its own, so a single weak signal stays visible even when the rest are strong.

Each signal, at every level

Comfort with ambiguity (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradDescribes freezing or giving up when a project brief or assignment was unclear.Waited for a professor or mentor to clarify everything before starting.Describes making a reasonable assumption on an unclear project and checking it early.Describes structuring a vague project brief into clear steps and getting it agreed.
JuniorDescribes freezing or giving up when requirements were unclear.Waited for full requirements before starting any work.Describes starting on unclear requirements with stated assumptions and checking them.Describes turning an unclear task into a plan and confirming it with stakeholders.
Mid-levelDescribes freezing or giving up when requirements were unclear.Handled ambiguity only after a lead broke the problem down for them.Describes breaking an ambiguous project into steps and resolving unknowns as they went.Describes progressing on an ambiguous project and reducing the ambiguity for the whole team.
SeniorDescribes freezing or giving up when requirements were unclear.Handled ambiguity within a defined project, not in setting its goals.Describes defining goals for an ambiguous multi-team problem and moving it forward.Describes defining an ambiguous problem other teams avoided and creating a clear path.
StaffDescribes freezing or giving up when direction was unclear.Handled ambiguity at project level but not in setting org direction.Describes setting direction for an organisation when the strategy itself was unclear.Describes turning org-level uncertainty into a strategy several teams adopted.

Bias to action (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradDescribes waiting to be told what to do in every situation.Acted only after a teammate or mentor pushed them to.Describes starting work on a project or club task without being asked.Describes taking quick, sensible action on a blocked team project that unblocked others.
JuniorDescribes waiting to be told what to do in every situation.Acted only after being pushed by a lead.Describes acting on a problem in their area without waiting for instructions.Describes acting quickly on a problem outside their task while managing the risk.
Mid-levelDescribes waiting to be told what to do in every situation.Acts within assigned work but escalates rather than acts on wider problems.Describes acting quickly on a project problem with a reversible first step.Describes moving fast on an urgent problem and explaining why the risk was acceptable.
SeniorDescribes waiting to be told what to do in every situation.Acts quickly on own team's problems but waits on cross-team ones.Describes driving a stalled multi-team effort forward with a calculated first step.Describes acting decisively on a cross-team problem and setting a fast, safe path.
StaffDescribes waiting to be told what to do in every situation.Acts decisively on team problems but defers on org-level ones.Describes unblocking an org-level decision that had stalled, with a reversible plan.Describes creating a culture or mechanism that lets several teams act faster safely.

Collaboration (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradDescribes working alone or speaks dismissively of teammates.Describes group work but only their own part, with no interaction.Describes sharing work and helping a teammate on a group project.Describes bringing a struggling project group together around a shared plan.
JuniorDescribes working alone or speaks dismissively of teammates.Describes collaborating only when it was required.Describes working closely with teammates and seeking and using feedback.Describes helping teammates succeed beyond their own task.
Mid-levelDescribes working alone or speaks dismissively of teammates.Collaborates within their team but describes friction with others.Describes working well with other roles, such as design or product, to deliver.Describes building a working relationship with a difficult partner to deliver together.
SeniorDescribes working alone or speaks dismissively of colleagues.Collaborates well within the team but not across teams.Describes building alignment across teams with different priorities.Describes turning a tense cross-team relationship into a lasting partnership.
StaffDescribes working alone or speaks dismissively of colleagues.Collaborates across a few teams but not at org level.Describes aligning several organisations on a shared plan.Describes building cross-org ways of working that outlasted their involvement.

Emergent leadership (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradDescribes no moment of stepping up, even when a group project stalled.Stepped up only when a teacher or mentor assigned them the lead.Describes stepping in to organise a stalled group or club task without a title.Describes stepping in to lead, then handing back once the group was on track.
JuniorDescribes no moment of stepping up when the team needed it.Led only when formally asked to.Describes stepping in to help solve a team problem without formal authority.Describes stepping in to lead a fix, then stepping back once it was solved.
Mid-levelDescribes no moment of stepping up when the team needed it.Steps up but holds on to control after the problem is solved.Describes leading a team effort without authority, then stepping back.Describes leading without authority and growing someone else into the lead role.
SeniorDescribes no moment of stepping up when the team needed it.Leads within their own team only.Describes stepping in to lead a cross-team problem, then handing off cleanly.Describes leading a cross-team effort without authority and leaving others owning it.
StaffDescribes no moment of stepping up when the organisation needed it.Leads across teams only when given formal authority.Describes stepping in to lead an org-level problem without formal authority.Describes leading an org-level fix, then building owners so they could step out.

Intellectual humility (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradInsists they were right in every story and dismisses feedback.Accepts feedback only when a teacher or mentor insisted.Describes changing their mind after feedback from a teammate or mentor.Describes seeking out criticism of their own work and improving it.
JuniorInsists they were right in every story and dismisses feedback.Accepts feedback reluctantly, only when required.Describes admitting a mistake and changing course after feedback.Describes asking for critique early and changing their approach because of it.
Mid-levelInsists they were right in every story and dismisses feedback.Admits mistakes but frames them as others' fault.Describes changing their position when a colleague had better evidence.Describes publicly changing their mind and crediting the person who was right.
SeniorInsists they were right in every story and dismisses feedback.Admits small mistakes but defends every significant decision.Describes reversing a significant decision when evidence showed they were wrong.Describes inviting challenge to their own plan and adopting a junior colleague's better idea.
StaffInsists they were right in every story and dismisses feedback.Admits mistakes privately but not to the wider organisation.Describes openly reversing an org-level decision when it proved wrong.Describes building review habits that let others challenge their decisions safely.

Doing the right thing for users (5%)

Level1 · Poor2 · Borderline3 · Solid4 · Outstanding
Intern / new gradNever mentions the users of any project they describe.Mentions users only when asked who the project was for.Describes a choice made on a project because it was better for its users.Describes testing a project with real users and changing it based on what they said.
JuniorNever mentions users in any story.Mentions the users of their work only when the interviewer asks about them.Describes a decision driven by what was right for users.Describes raising a user problem nobody asked them to fix and fixing it.
Mid-levelNever mentions users in any story.Mentions users but decisions were driven by convenience or deadlines.Describes trading off a deadline or shortcut to do right by users.Describes pushing back on a requirement that would have hurt users and winning the case.
SeniorNever mentions users in any story.Considers users for their own work only.Describes steering a multi-team decision towards what was right for users.Describes holding a user-protecting line under pressure from senior stakeholders.
StaffNever mentions users in any story.Considers users at project level, not in org decisions.Describes shaping org priorities around a user problem with evidence.Describes changing an org policy or practice so users were protected at scale.

The general dimensions still apply: see the full behavioural interview rubric.

Get scored against this rubric

Pick Google when you start a mock and the AI interviewer adds these Google-specific checks to its scoring.

Practise a behavioural round

Where this rubric comes from

These rubrics are researched: they follow the scoring methods big-tech companies describe publicly (behaviourally anchored ratings, bar raisers, leadership principles, named interview signals) and how their rounds are commonly run. No company publishes its actual scoring sheet, so the level-by-level wording is our own synthesis. It is the same rubric our AI interviewer scores every mock against.

Questions, answered

How does Google score Behavioural Interviews?
Google behavioural interviews are commonly described as scoring 6 signals: Comfort with ambiguity, Bias to action, Collaboration, Emergent leadership, Intellectual humility, Doing the right thing for users. On top of the general behavioural rubric, each one is judged on its own, so a single weak signal stays visible even when the rest are strong.
Is this Google's official rubric?
These rubrics are researched: they follow the scoring methods big-tech companies describe publicly (behaviourally anchored ratings, bar raisers, leadership principles, named interview signals) and how their rounds are commonly run. No company publishes its actual scoring sheet, so the level-by-level wording is our own synthesis. It is the same rubric our AI interviewer scores every mock against.