I applied online. The process took 3 months. I interviewed at Google (Waterloo, ON) in Apr 2025
Interview
Online assessment, followed by phone assessment, virtual interview, onsite interview, behavioural interview, and another quick meeting/interview discussing role compatibility. The actual interview process wasn't impossible, just two LC mediums, and there was also a team-matching process.
Interview questions [1]
Question 1
Two leetcode medium questions, each roughly 40 mins
I applied online. The process took 4 weeks. I interviewed at Google (Waterloo, ON) in Jul 2024
Interview
Fast, back-to-back purely technical interviews. Interviewers were very open to collaboration, and overall was an enjoyable process. All questions around LC medium with several follow-ups. Received offer 3 weeks later.
I applied through college or university. The process took 8 months. I interviewed at Google (Waterloo, ON) in May 2025
Interview
4.5/5 (well-organized but intense)
Interview Process:
OA (Online Assessment): 2 coding questions (LeetCode Medium/Hard) + behavioral MCQ (60 mins).
Technical Phone Screen (45 mins): Live coding on a collaborative editor (e.g., problem-solving + optimization).
Final Round (2 x 45-min virtual interviews):
Coding: Algorithm design + edge-case discussion.
System Design Lite: High-level design for a small-scale feature (e.g., API caching).
Team Fit (30 mins): Casual chat with a potential team lead about projects and culture.
Interview questions [1]
Question 1
OA (Online Assessment):
"Given a string, find the longest substring with at most K distinct characters." (LeetCode Medium variant)
"Design a rate-limiting algorithm for an API." (Pseudocode + complexity analysis)
Phone Screen:
*"You’re given a grid representing a maze (0 = path, 1 = wall). Find the shortest path from start to end."* (BFS/DFS follow-up: optimize for time/space).
Final Round (Coding):
"Implement an autocomplete system using a trie. How would you handle scaling to millions of users?" (Trie operations + discussion on caching/sharding).
System Design Lite:
"How would you design a tinyURL service?" (Focus on hashing, collisions, and database schema)