Google Interview Experiences

The online coding assessment they make you do before anything else even happens is intense, then had an HR chat and two back-to back technical interviews with engineers. Questions about algorithms, graph traversal, and dynamic programming. They also asked about how I'd design a system at scale, felt like they were testing both coding ability and problem solving approach.

Passed the online coding assessment but bombed the interviews, they were back to back and the second one was harder because you can't just rely on patterns you've memorized. One was a graph problem where you had to optimize on the spot with complexity analysis and the behavioral covered resolving a team conflict and they probed for way more detail than I had, process took 2 months.

they give you a 24 hour take home case study with actual ridesharing data where you have to analyze it and write up a full report with your methodology and assumptions and conclusions. I spent way too much time making the writeup look good and polished and ran out of time to actually do proper modeling. should have just focused on the analysis first and cleaned up the report at the end.

60 min OA with 2 algorithmic problems used Python then a collaborative phone interview, third round was abstract logic puzzles and recursive stuff unlike anything on leetcode so use whatever language you want just don't try OCaml for first time during an interview.

long process, recruiter screen then written assessment then three interviews for product sense analytical thinking and leadership. market sizing was harder than expected.

Recruiter screen was easy going, both technical rounds hard which I solved clean (tree optimization)

I had 2 rounds on interview, botn was medium Leetcode. The first question was the variation of Fizz Buzz, where we need to check multiple conditions before printing anything. The second question was design a template like google doc, where each line has a character limit, and if the word exceeds the limit it should be placed in the next line.

3 rounds last one had coding question in python using hash tables they helped me along when I got stuck and eventually solved it but took me some time.

I was scheduled a technical round and behavioral round with Google on the same day. They were both ~1hr. I felt it wasn't a good experience because the engineers who interviewed me seemed like they couldn't be arsed, which made me more nervous. The engineer who conducted the technical interview didn't explain the question well and also messed up on the problem constraints which I had to clarify. The question was not a LC style question, surprisingly. For the behavioral it was pretty standard asking about experience and how you work with others.

Made it to the last interview they asked a leetcode hard and I just couldn't figure it out. Would say OOP is very important to know for the process

HR screen then manager interview then technical, the technical had a LeetCode medium or could've been hard idk problem about shortening file paths and some resume questions and they wanted to know why Google and about a time I received negative feedback. Three rounds for a co-op seems like a lot.

application took forever just to set up the account. Got an email for an interview like 3 months later and by that point I forgot I even applied. Two people on the call asking basic behavioral stuff, tell me about a time you worked on a team, how do you handle deadlines. Also some questions about databases which were easy. It was painfully slow and I already accepted something else by the time they got back to me.

3 rounds with various team members, common behavioral questions asked