2023–2026 Google New Grad SWE BQ / Googleyness: All Reported Questions From 79 Experiences

Every recoverable BQ and Googleyness question disclosed across 79 firsthand Google New Grad and Early Career interview experiences.

Coverage: Seventy-nine of the 196 deduplicated full-time Google New Grad and Early Career software-engineering reports published from March 2023 through September 2026 explicitly mention BQ, behavioral, Googleyness, or Googlyness. Every concrete question and follow-up that the original authors preserved is included below. Reports that disclose only a broad label such as “standard BQ” are identified as incomplete evidence rather than expanded with invented questions.

Behavioral and Googleyness appeared throughout the loop

At least 79 of the 196 original-author reports explicitly mention BQ, behavioral, Googleyness, or Googlyness. Some candidates had a dedicated 40- or 45-minute round. Others received one or two questions before coding, during a technical round, or while discussing a project.

The questions were not limited to “tell me about a conflict.” They covered judgment, collaboration, changing priorities, inclusion, user impact, integrity, learning, and what the candidate valued in a team.

The counts below are conservative lower bounds from questions or themes directly preserved in the original-author reports. Categories overlap, so they should not be added together.

High-frequency BQ question bank

Conflict and disagreement

These were the most consistently repeated behavioral questions:

1. Tell me about a conflict with a teammate and how you resolved it.
2. Describe a disagreement with a manager or a more senior colleague.
3. What would you do if one person did not fit or collaborate with the rest of the team?
4. Describe a time another person's work affected your own work.
5. Tell me about a difficult colleague and how the relationship changed.
6. What would you do if someone took credit for the whole team's work?

Several candidates reported multiple conflict variations in the same interview: peer conflict, manager conflict, and a teammate who was isolated from the group. Other candidates explicitly said they prepared conflict stories but were never asked one, so conflict was common—not guaranteed.

Collaboration and team support

1. Tell me about a time you helped a peer who was underperforming.
2. What would you do if a teammate was not collaborating?
3. How would you handle a teammate who thought your pace created pressure for them?
4. Describe a cross-team collaboration and what made it difficult.
5. As an individual contributor, how would you improve team culture?
6. Tell me about a time you helped someone fit into a team.
7. If you assigned people work they were expected to like and they rejected the assignments, what would you change?

The strongest repeated pattern was not “be nice.” Interviewers asked what the candidate personally noticed, what they said or changed, and what happened to the team afterward.

Ambiguity, changing priorities, and workload

1. Tell me about a time priorities changed while you were working on a project.
2. Describe a situation where you had to make progress with incomplete or ambiguous information.
3. How do you decide priority when several pieces of work arrive together?
4. Tell me about a time you handled multiple deadlines.
5. Describe a tight deadline and the trade-offs you made.
6. What would you do if the whole team was overloaded and work-life balance was poor?
7. How would you handle multitasking, and what criteria would you use to prioritize?
8. How do you approach work that is important but not motivating?

Follow-ups often asked whether everything was completed, whether the candidate considered giving something up, who was informed, and why one task was prioritized over another.

Challenge, failure, and learning

1. Tell me about a challenging project and why it was difficult.
2. Describe a mistake or failure and how you corrected it.
3. Tell me about an obstacle you overcame.
4. Describe a time a plan or method turned out to be wrong.
5. Tell me about a time you had to learn a new technology quickly.
6. Describe something you learned recently and how it changed your approach.
7. Tell me about a time you challenged the status quo. What would you do if the new approach failed?

Some questions were framed positively—“most rewarding project” or “proudest achievement”—but the follow-up still moved toward difficulty, trade-offs, measurable results, or what the candidate would do differently.

Leadership, influence, and ownership

1. Tell me about a project you led and why it was challenging.
2. Describe a time you stepped up to support a team.
3. Tell me about a time you influenced other people without formal authority.
4. Describe a time you mentored someone.
5. Tell me about a time you went above and beyond for a project or customer.
6. How would you improve team culture as an individual contributor?
7. Describe a decision where you used someone else's perspective.

One recent candidate prepared failure and conflict stories but received questions that stayed around leadership. Another reported that each new question grew out of the previous answer rather than following a fixed list.

Inclusion, different perspectives, and user impact

1. Tell me about working with someone whose background or working style was very different from yours.
2. Describe something you learned from a person with a different background.
3. Tell me about a time you noticed a bias or unsupported assumption.
4. Describe a time you adapted to another person's working style.
5. How would you make a product work for user groups with different needs?
6. If a photo-related feature were being reviewed, what could offend or exclude users? What edge cases would you check?
7. If a last-minute bug could affect people and there was no time to fix everything, what would you do?
8. Tell me about incorporating user or colleague feedback into your work.

These questions were often hypothetical and intentionally underspecified. Reports describe interviewers saying there was no single correct answer, then asking about edge cases, affected users, escalation, and trade-offs.

Motivation, projects, and managers

1. Why Google?
2. What are the top reasons you would join a company?
3. What qualities do you want in your next manager?
4. What did you learn from a previous manager?
5. What did you like and dislike about a previous team or team lead?
6. What is your most interesting, challenging, rewarding, or exciting project?
7. What are you most proud of in your dissertation, internship, or recent work?
8. How could your research or project experience apply to a Google product?

Project questions frequently became the foundation for the rest of the round. Candidates were asked to explain their own decision, not merely describe what the team built.

Remaining one-off and low-frequency questions

The sections above group the repeated question families. The following questions and follow-ups were also directly disclosed, but appeared less often or used a meaningfully different wording.

Background, goals, and work preferences

1. Give a concise self-introduction.
2. What role do you usually play on a team?
3. What is your greatest achievement outside work?
4. Tell me about a personal interest or hobby that you changed.
5. Tell me about your college experience.
6. What are your short-term and long-term goals?
7. What are your future plans?
8. What is one of your weaknesses?
9. What keeps you motivated or helps you maintain passion for your work?
10. What kind of work would you want to do at Google?
11. Which previous company, school-project team, or work group was your favorite?
12. What made that team a good place to work? Was there another reason?
13. What strength or ability do you bring, how did you apply it to a team, and what result followed?
14. How did that strength help you succeed in the working environment?
15. Introduce your dissertation or research area.

Ownership, judgment, and stakeholder situations

1. Tell me about a difficult customer or stakeholder and how you handled the situation.
2. Describe a time you simplified a complex process or system.
3. What was your most successful project or experience?
4. Looking back, how could you have done better?
5. How do you communicate with your team?
6. Tell me about a time the outcome exceeded expectations.
7. Describe a goal you did not reach. Why did it happen, and what did you learn?
8. Tell me about feedback you gave someone and how that person reacted.
9. How would you respond to an unreasonable request?
10. How would you work inside a company or team with a weak culture?
11. How would you respond if someone asked for their request or ticket to receive priority?
12. You are assigned a project with someone more senior than you. How would you handle the working relationship?
13. What would you do if a project or its direction seemed questionable?
14. Tell me about a solution or method that you noticed could be improved.
15. Tell me about a time your integrity was tested.
16. How would you plan the addition of a new product feature?
17. Another team is building the same thing as your team. What would you do? What if neither side wanted to reconcile?
18. How would you stay current and continue contributing while working at Google?
19. What did you do during the past year to improve yourself?
20. Tell me about a time you agreed with a supervisor's decision and why.

Follow-ups preserved by the candidates

1. How did you measure the result or percentage improvement?
2. After fixing the bug or mistake, what remediation or prevention work did you do?
3. Besides presenting data, what else did you do to persuade the other person?
4. Why did the other person propose their original idea?
5. When multitasking, did you complete every task? Did you consider giving something up?
6. Who did you inform when priorities or deadlines changed?
7. Why did you prioritize one task over another?
8. What measurable impact did your action have?
9. Besides the first reason you gave, what else made the team a good place to work?
10. If the new approach failed or a new problem appeared, what would you do next?

What the reports did not disclose

Some of the 79 reports say only “standard BQ,” “teamwork-oriented questions,” “leadership cases,” “conflict questions,” or “résumé plus hypothetical questions.” A few report five to twenty questions but remember none of the wording. Those interviews are included in the frequency count, but their missing questions are not recoverable and are not fabricated here.

The BQ format was not one fixed script

Rapid question bank versus one story with deep follow-ups

Both formats appeared repeatedly.

Some candidates received five to ten relatively quick questions. A few described more than ten or even around twenty questions. The interviewer sometimes rephrased the answer, recorded a short note, and moved directly to the next prompt.

Other candidates spent much longer on one or two stories. Each answer triggered another question about context, personal action, measurable impact, alternatives, or what changed afterward.

Resume use varied

Some interviewers did not appear to have read the résumé and asked the candidate to establish all context. Others spent the opening 10–15 minutes on internships, a dissertation, or a technical project, then built the behavioral questions from those details.

This is why a story still needed to make sense to someone who had never seen the project before.

Experiential and hypothetical questions both appeared

The familiar format was “tell me about a time.” The other format placed the candidate in a new situation: a harmful bug before launch, an overloaded team, disliked task assignments, a non-collaborative peer, or a product that could exclude users.

Candidates sometimes said the hypothetical questions felt harder because the underlying theme was not obvious at first. One question could combine conflict, prioritization, user impact, and leadership.

What interviewers kept probing

Across otherwise different BQ prompts, follow-ups repeatedly returned to five things:

1. Personal ownership: What did you decide or change, rather than what “we” did?
2. Reasoning: Why did you choose that action over the alternatives?
3. Impact: What measurable or observable result followed?
4. People and users: Who was affected, and how did you account for a different perspective?
5. Learning: What would you repeat or change next time?

Several reports say the interviewer summarized the answer back to the candidate or asked whether their interpretation was correct. Others mention detailed note-taking. The pattern suggests that a clean, specific story mattered more than forcing every answer into identical memorized wording.

Process patterns around the interviews

Nine candidates explicitly reported an additional interview round. Reasons included mixed feedback, an unfinished follow-up, overlapping topic coverage, or not enough signal from the original loop. Some candidates advanced after the extra round; others did not. The evidence does not support treating an additional interview as an automatic rejection.

At least 27 candidates mention team matching or project search. Some entered matching after hiring review, some matched before final approval, and some waited for weeks or months. The sequence was not consistent enough to present one universal timeline.

The structured source labels recorded 74 Pass, 36 Fail, five WaitList, 80 Other, and one unavailable result. Other does not establish a final hiring outcome.