[NDA] Google | L4 | Virtual-Onsite | March 2020 [Reject]
Anonymous User
1711

Hello!

Mobile Engineer - 8+ YoE
Leaving out question specifics due to NDA.

Preparation:
I decided to take my time on the process in order to have time to get familiar with it and have time to study! I have been studying on Codility and HackerRank since June, initially not leetcode, i started doing leetcode problems when i started to study for the onsite!

1st Phone Interview (Oct 2019) :
Android Domain - Basically android arch best practices related to RecyclerView - I thought i crushed this round but the interviewer noted some things i needed to fix so he recommended a 2nd Phone Interview. My recruiter also noted that my next interview would also be android domain.

2nd Phone Interview (Dec 2019) :
Android Domain - The interviewer started asking Android Basics questions like "What is context?, How context relates to resources? how to do threading?" Then there was a problem regarding Multi-threading with LiveData

I left a lot of space for my onsite, trying to be strategic and have plenty of time to study, I was scheduled to travel to NYC in March for my On-site but due to the COVID-19 all the onsites were suspended last week. (i think it my strategy actually backfired... lol )

"Onsite" Virtual Interviews:

So my schedule was supposed to be like this :
Round1 - Algos / DS
Round2 - Algos / DS
Round3 - Googleyness
Round4 - Android
Round5 - Android

So here goes my experience (Ommitting actual questions)

Round1 - Tree problem - something about searching a string in a tree (not binary), part 1 was perfectly easy, i was able to get into a working solution in minutes, with preorder traversal, part2 was a bit trickier, i had to take too much hints in order to get an efficient way to do it.

Round2 - Weighted Graph Problem - I think i did well on this round, maybe i was too slow, followup was to find ways to actually do better, discussed a couple of possible solutions but we did not have time to code.

Round3 - Googleyness - Rocked (i think)

Round4 - I was expecting an android round so i got initially shocked when the interviewer started asking a DS / Algos question, funny enough, he asked the same question as round 1, I pointed that out so he changed the question, The new question i think it was easy, but it took me too much time, again, I was kinda shocked, for me this was my worse round.

Round5 - Again, i was expecting an android round but the interviewer asked a DS / Algos question, this problem seemed easy but it required to be very graphical, i had pen and paper at hand and it was absolutely necessary to get the problem right. I Think this was one of my best.

So this was my day, will update as soon as i get the details!

Update:

Last Thursday I had 2 more interviews, because of those rounds that were supposed to be Android, so, i had 2 Android-Domain-Specific Interviews.

Overall they went really well, they were some kind of app architechture design with a bit of coding, normally the handicap here is time because design questions are way-too open-ended.

The interviewers submitted feedback right away and my packet is on the HC for review now! :D

Update:

I Received an email from the recruiter telling me about the rejection, Feedback was mainly that i was slow coding and was not able to iterate past naive solutions, and a couple other minimal stuff. I could try again in one year.

That's the end for now, more practice and until next time

Comments (5)