Google · Phone screen → Onsite
In process2025–2026 Google New Grad / L3 Interviews: 13 Experiences (Part 2 :)
Part 2 of a two-part roundup of thirteen firsthand Google New Grad and L3 interview reports.
Continued candidate experiences
09: Hypothetical BQ, Climbing Stairs, and list-based large-number addition
Report date: December 2, 2025 · Role: Google NG · Location: Not shown · Result: Fail
BQ
One hypothetical asked how the candidate would join a team where everyone was busy and work-life balance was poor.
Technical
- The first question was LeetCode 70, Climbing Stairs. The source wrote the title as an obfuscated Chinese alias.
- The second used two lists to represent large numbers and asked the candidate to simulate addition.
- The source did not state digit order, carry format, or the range of each list element.
10: Early Career R1 with checklist-style BQ and DP
Report date: December 5, 2025 · Role: Google Early Career SDE · Location: Not shown · Result: Pass
- The process had two stages, with two interviews in each stage, normally back-to-back.
- R1 included one behavioral and one technical interview.
- The BQ interviewer followed a list of about five or six questions.
- Topics included a difficult challenge, conflict with a coworker, and a tight deadline.
- The technical interview was a dynamic-programming problem at about LeetCode Medium difficulty.
- The source did not reveal the DP prompt.
11: Nested JSON serialization and four BQ prompts
Report date: December 8, 2025 · Role: Google NG · Location: Not shown · Result: Not disclosed
Coding
- Serialize a dictionary into a JSON string.
- Keys are strings. Values may be strings, lists, or nested dictionaries.
- The example {"a":"b", "c":"d"} should produce the equivalent JSON object string.
- The source did not state escaping or support for other JSON types.
BQ
Favorite project; working with people from different places; handling stolen credit; and the three most important qualities in a company.
12: Inverse Coin Change and a Course Schedule variant
Report date: December 9, 2025 · Role: Google 26NG · Location: Not shown · Result: Not disclosed
Onsite setup
Two 45-minute interviews were back-to-back. The candidate used a Chromebook and shared whiteboard.
Technical round 1
- Start from Coin Change counting, where dp[i] is the number of ways to make amount i.
- Receive the completed dp array and recover the coin set.
- The candidate needed a hint and worked through examples.
- The candidate reached the algorithm and finished just in time.
- A second hint exposed a loop bug.
- The source did not state uniqueness, duplicate-coin, or no-solution rules.
Technical round 2
A Course Schedule variant was solved quickly, but the exact variant was not preserved.
13: Meeting Rooms II under a wrapper plus five BQ topics
Report date: December 9, 2025 · Role: Google 26NG SWE · Location: Not shown · Result: Not disclosed
Coding
- The first two parts were simple for-loop tasks, but the prompts were not preserved.
- The third part was Meeting Rooms II wrapped in a different story.
- The wrapper, samples, and endpoint rules were not preserved.
BQ
A challenging project, a plan that changed, mentoring someone, conflict with someone, and the top three reasons to join the company.
What repeated often enough to prioritize
Tier 1: Practice the full reasoning path
- Clarify the input, output, and missing rules.
- Give a simple correct approach before optimizing.
- Explain why the next approach is better.
- Dry run the code and test small edge cases.
- State what changed after a hint or follow-up.
Tier 2: Prepare these concrete areas
- Union-Find and DFS for connectivity.
- Trees, BFS, and lowest common ancestor.
- Intervals and meeting-room counting.
- Heaps for k smallest pair sums.
- HashMaps, frequency ordering, and weighted random selection.
- Nested-string and JSON parsing.
- Dynamic programming, including inverse-DP reasoning.
- API and data-structure design.
Tier 3: Prepare detailed behavioral stories
- Conflict and disagreement.
- Helping a teammate.
- Working with a senior teammate or manager.
- Adapting to change.
- Protecting different user groups.
- Multitasking, setbacks, and personal impact.
There’s still sooooo much more to do hiahiahia, I’ll be backkk! Expect having 10+ parts
Comments
0No comments yet — be the first to share what you know.