Google is still probably one of the best places for a new software engineer who wants to work for a large company in her/his early career to experience how a large, leading software company makes things work, and to experience the pros and cons of working in a large company.
The company is big. There are significant internal organizational complexities. Lots of time can be spent on navigating through internal organizations, management, promotion logistics, etc., rather than actually building quality products.
Reward quality project launches and promote quality people.
An introduction and then a coding question. That's it. No questions about who you are, your resume, or your CS knowledge—none of the stuff in the syllabus they gave you. I just went in and started coding. Strangest "interview" I've done yet. The q
The process went well. There were three LC algo rounds and one BQ round. Overall, it was a very good experience, but I am not very well-prepared. I hope I can get in next time in 2025.
I applied online through a referral and received the coding challenge. Following that, I got an email for an onsite interview. For the onsite, I had four coding rounds, each lasting a minimum of 45 minutes to 1 hour. The entire process took over thr
An introduction and then a coding question. That's it. No questions about who you are, your resume, or your CS knowledge—none of the stuff in the syllabus they gave you. I just went in and started coding. Strangest "interview" I've done yet. The q
The process went well. There were three LC algo rounds and one BQ round. Overall, it was a very good experience, but I am not very well-prepared. I hope I can get in next time in 2025.
I applied online through a referral and received the coding challenge. Following that, I got an email for an onsite interview. For the onsite, I had four coding rounds, each lasting a minimum of 45 minutes to 1 hour. The entire process took over thr