In this article
Before you start
Everything else, including how the scoring works, is explained below.
Why interviewers ask this
Interviewers ask behavioral questions because past behavior is evidence they can compare across candidates, and a candidate who cannot give a specific example leaves them with nothing to score. The consequence for you is that a vague answer loses points even if it sounds sensible: the rubric has no row for sounding sensible.
What the round separates is evidence from impression. Google's guide warns that in first encounters "we make snap, unconscious judgments" and then hunt for evidence that confirms them, which it calls confirmation bias, and it presents structured interviewing as the remedy. A weak answer lets the interviewer's impression do the work. A strong answer hands over specifics, with an action you took and a result, so the score rests on what you said.
Google behavioral interviews from first principles
In plain words
- Emergent leadership
- Emergent leadership is a kind of leadership that shows without a manager's title, such as taking initiative, working across teams and driving your own development, which Google's guide says to look for in individual contributors.
- Role-related knowledge is an attribute area that Google's guide recommends defining for a role, and it asks whether a candidate has the functional or technical know-how the job needs, judged from past work examples.
Think of a diving competition. Every diver performs, and judges score against the same published criteria, so a good dive scores well whatever the judge felt about the diver. A structured interview works the same way, and your answers are the dive. The analogy breaks in one place: a diver rehearses a fixed routine, while an interviewer chooses a question and the follow-ups. So you prepare building blocks, not a script.
In one precise sentence: Google says it uses the same questions, grades answers on an identical scale and decides on predetermined qualifications, so your job is to give specific evidence for each quality a question tests.
Step-by-step description
- Answers are scored on a written four-level scale.
- Knowledge, problem solving and leadership.
- Tell a story, or think aloud.
- Build goal, response and next step into the story.
- Three to five stories covering every area twice.
- Google's guide describes standardized rubrics so that all reviewers share an understanding of what an outstanding, solid, borderline and poor response looks like.
- MIT's careers office advises preparing three to five stories from outlines, not memorized scripts.
Step 1: Learn how the scoring works
The first step is to learn that your answer is scored against a written rubric, not judged on overall feel. Google's guide describes its approach as four aspects: vetted, role-relevant questions; recorded feedback on candidate answers; standardized rubrics "so that all reviewers have a shared understanding of what outstanding, solid, borderline, and poor response looks like"; and interviewer training and calibration. Google's candidate page says the same from the other side: "Every candidate is assessed using clear rubrics. We use the same rubrics for everyone being considered for that role" (Google Careers, how we hire, read 2026-10-24). The guide itself is from (Google re:Work, updated March 2026).
The input is your spoken answer, the change is an interviewer's notes and a rating on that four-level scale, and the output is a score later reviewed by others. The guide has interviewers take notes "so they can later be reviewed", so your answer must survive being read by someone who was not in the room.
Step 2: Learn the three attribute areas
The second step is to learn the three areas Google's guide recommends defining for any role, because your stories must cover them. The guide names role-related knowledge, problem solving and leadership. Role-related knowledge asks whether you have the functional or technical know-how for the role. Problem solving asks how you break down a complex scenario and reach a logical, data-driven solution. Leadership asks, for individual contributors, for emergent leadership, and for people managers, the ability to empower a team and develop reports (Google re:Work, March 2026).
The input is a prompt, the change is your sorting it into an area, and the output is the evidence you choose. These are the categories the guide recommends to employers. Google's own careers site used to list four interview areas: general cognitive ability, leadership, role-related knowledge and Googleyness (Google Careers, archived 2019). The label Googleyness is covered in the follow-up questions below. Use the three areas here as a preparation frame, not as Google's current scoring sheet. What you now know: every prompt is probing at least one of three things.
Step 3: Tell the question types apart
The third step is to tell behavioral and hypothetical questions apart, because the guide says a structured interview uses both and they need different answers. A behavioral question asks you to describe prior achievements and match them to the job, as in "Tell me about a time…". A hypothetical question presents a job-related situation, as in "What would you do if…?" The guide adds that behavioral questions reveal patterns of behavior, while hypothetical ones show how you respond to novel situations.
The input is the first sentence of the question, the change is a switch between telling a story and thinking aloud, and the output is the right answer shape. For behavioral, use the STAR structure. For hypothetical, state what you would clarify first, give a recommendation, and name the risk. What you now know: an answer in the wrong shape wastes the question, whatever its content.
Text description of the diagram
- A behavioral question asks you to describe prior achievements and match them to the job.
- A hypothetical question presents a job-related situation, and it shows how you would respond to novel situations.
Step 4: Prepare for fixed follow-up questions
The fourth step is to prepare for follow-ups that are written in advance, because the guide says Google's questions "often contain an initial prompt, along with several follow-ups designed to understand the candidate's thought processes". The follow-ups are predetermined and exist to draw out a high level of detail.
The guide's own behavioral example shows the pattern. The prompt is to tell about a time your behavior had a positive impact on your team, and the attached follow-ups ask about your primary goal and why, how your teammates responded, and what your plan is moving forward. So a good story contains a goal and its reason, how others reacted, and a forward-looking sentence.
Google's candidate page agrees: it says to "expect some follow-up questions" and that behavioral questions "are meant to elicit specific examples over 'I always do X,' so again, preparing a broad library of examples is key" (Google Careers, interview tips, read 2026-10-24). What you now know: the follow-up is part of the question, so build it into the first answer.
Step 5: Build a story bank and check it against the areas
The fifth step is to build a small set of stories and check that each area has a story, with a second one in reserve. MIT's careers office advises preparing three to five stories from outlines, not memorized scripts, because memorizing "may limit your ability to adapt" (MIT Career Advising and Professional Development, read October 2026). Google's own interview-tips page recommends the STAR structure and a broad library of examples (Google Careers, read 2026-10-24). The two-stories-per-area rule below is our rule, not MIT's or Google's: MIT gives the three-to-five total, and two per area is what we add so a second question in one area does not repeat a story.
Tag each story with the areas it can honestly evidence. The worked example below tests this on an invented bank. What you now know: coverage is a property of the whole bank, so check the grid, not each story alone. The wider method is in the story bank section of the behavioral hub.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →Worked example
The four stories below are invented to show the method; yours come from your own work. Each is tagged with the areas it can honestly evidence, and a short script finds the smallest set of stories that covers all three.1
| Story | What it shows | Areas it evidences |
|---|---|---|
| A | Rebuilt a failing data pipeline | Role-related knowledge, problem solving |
| B | Led a migration across two teams | Leadership, problem solving |
| C | Taught a new teammate a legacy system | Leadership, role-related knowledge |
| D | Chose between two designs with partial data | Problem solving |
Two stories are enough to cover all three areas, and four pairs work: A with B, A with C, B with C, and C with D.1 Problem solving has three stories, and role-related knowledge and leadership have two each. The bank meets the two-per-area rule, so the real risk is spending.
If stories B and C are both used on leadership questions in one round, role-related knowledge rests on story A alone and leadership has no story left (computed in the script: with B and C spent, knowledge 1, problem solving 2, leadership 0). The fix is not a bigger bank but a plan: use the stories that carry two areas for the area where you have the fewest alternatives, and tell a different story when a second question in the same area arrives.
Text description of the diagram
- In an illustrative four-story bank, any one of four pairs of stories covers all three areas.
- Problem solving has three stories, and role-related knowledge and leadership have two each.
Next, the answer itself. For the rubric, Google's guide gives four levels and no sample wording, so the table below is our illustration of how the levels differ on the guide's own example prompt. It is not a Google rubric.
| Level | What the answer contains (our illustration) |
|---|---|
| Poor | General statement about being a good teammate, no example |
| Borderline | A real example, but the goal and your own action are unclear |
| Solid | A clear goal, your own actions and how teammates responded |
| Outstanding | All of the above, plus a result and a changed habit going forward |
An illustrative contrast on that prompt, with a 120-second STAR answer in mind. A borderline answer: "We had a messy release process, so we improved it and it went better." A solid-to-outstanding answer: "My goal was to stop weekend releases, because three in a row had failed. I wrote a checklist, ran it with the team for a month, and two teammates adopted it for their own services. Releases failed less often, and I now run a short review before every launch." On the MIT split, a 120-second answer gives Action 72 seconds, Situation 24, Task 12 and Result 12.1
Trade-offs and edge cases
The structure above comes from the guide Google publishes for employers, so it describes how Google says it designs interviews, not a verbatim list of the questions you will meet. Two limits follow.
First, practice differs by role and by round. The guide describes a method; your recruiter can tell you which rounds apply to your role, and Google's own candidate pages (interview tips and how we hire) are the place to confirm the current format. Second, the three areas are the guide's recommended categories. A round for a manager will weight the leadership area differently from one for an individual contributor, and the guide says so.
There is also evidence that structure matters beyond Google. A 2022 re-analysis of selection research found structured interviews had the highest mean operational validity of the methods reviewed, r = .42 (HumRRO summary, September 2022). The authors noted the validities varied widely, so treat it as a useful predictor, not a perfect one. For another employer's published values, compare Netflix behavioral interview questions and Amazon leadership principles.
How to answer it in an interview
Tell me about a time your behavior had a positive impact on your team.
My goal was to stop failed weekend releases, because three in a row had cost us two days. I wrote a short release checklist and ran it with the team for a month. Two teammates adopted it for their own services, and failed releases dropped. What I changed in my own habits is that I now run a ten-minute review before every launch and update the checklist after any miss. I would add one thing I learned: the checklist only worked after we agreed together on who owned each item.
The spoken structure is: goal and reason, what you did, how others responded, what you do differently now. The answer is about 95 words, sayable in under a minute, and it answers the guide's three follow-ups before they are asked.
Common mistakes
(wrong) "We improved the release process." The interviewer cannot tell what you did, so there is nothing to score. (right) "I wrote the checklist and ran it for a month."
(wrong) Telling the story with no goal. The first predetermined follow-up asks for your primary goal and why. (right) Open with the goal and the reason for it.
(wrong) Memorizing a script word for word. It breaks when a follow-up arrives, and it can sound unnatural. (right) Outline each story and say it aloud in different words each time.
(wrong) Using one story for every question in the round. The interviewer may notice the repeat, and one story cannot evidence all three areas. (right) Keep a bank with a second story for each area.
Follow-up questions
How do you prepare for a Googleyness interview?
Googleyness was one of four interview areas on Google's careers site, separate from leadership. The archived page defined it as: "Share how you work individually and on a team, how you help others, how you navigate ambiguity, and how you push yourself to grow outside of your comfort zone" (Google Careers, archived 2019). Google's current pages (October 2026) no longer use the label, but the interview-tips page still lists prompts on conflict, influencing teammates, driving collaboration, growing outside your comfort zone and helping a team succeed when you were not officially the leader. Prepare one story for each of those themes, with the goal, the response and the next step.
How do you prepare for a Google behavioral interview?
Learn the three areas, write three to five story outlines, tag each with the areas it evidences, and rehearse the goal, response and next step for each. Practise aloud, and confirm the rounds with your recruiter. The interview loops guide shows how rounds fit together.
What would you do about an unhealthy team culture when you are not the manager?
Say what you can influence from your seat: raise the issue early with a specific example, propose one small change, and work with the people who can act. A strong answer shows emergent leadership and respect for the manager's role, with a real story where you did this. The leadership interviews guide covers influence without authority.
How do you answer a question about solving a complex problem?
Treat it as the problem-solving area: state the problem and why it was hard, how you broke it into parts, the evidence that chose your solution, and the result. If it is posed as "what would you do", it is hypothetical, so say what you would clarify first and give a recommendation.
Is there an official list of Google behavioral questions?
Not a full list, but Google publishes sample prompts. As of October 2026 its interview-tips page gives prompts on conflict, influencing teammates, driving collaboration, growing outside your comfort zone and helping a team succeed when you were not officially the leader (Google Careers, read 2026-10-24). The re:Work guide adds an example with follow-ups. Treat any longer list of "Google questions" as a candidate report that may be out of date.
How many stories do I need?
Three to five is the usual advice, from MIT's careers office, and our own rule adds at least two stories per area, so a second question in the same area does not repeat a story. MIT does not set the per-area rule. For the closing questions, see questions to ask the interviewer, and for opening yours, tell me about yourself.
- Google says it asks the same questions, grades on one scale and decides on set qualifications.
- The guide's three areas are role-related knowledge, problem solving and leadership.
- Behavioral questions test what you did; hypothetical ones test how you would think.
- Follow-ups are written in advance: goal and why, how others responded, your next step.
- Keep three to five stories, and our rule of at least two for each area.
Sources
- Interview tips — Google Careers (read 2026-10-24), 24 Oct 2026
- How we hire — Google Careers (read 2026-10-24), 24 Oct 2026
- Google careers: how we hire, interview areas (archived) — Google Careers via the Internet Archive (2019 capture), 1 Jan 2019
- A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
- Effective interviewer training for better candidate experiences — Google re:Work (updated March 2026), 1 Mar 2026
- Using the STAR method for your next behavioral interview — MIT Career Advising and Professional Development (undated page; read 2026-10-24), 24 Oct 2026
- Is cognitive ability the best predictor of job performance? New research says it's time to think again — HumRRO (summary of Sackett, Zhang, Berry and Lievens, Journal of Applied Psychology), 27 Sep 2022
