Google is known for its engineer-driven culture. As an engineer, you have a lot of freedom to try out new ideas.
Google has well-built infrastructure. So it's very easy to build something on top of current infra without being able to understand how the infra works. This means it's easy to do daily work, but there aren't enough initiatives for an engineer to learn things.
After I passed the phone interview, I had 6 on-site interviews in 2 days, each 45 minutes long. My former co-workers described all the favorite topics. It is mostly questions on Algorithms and Data Structures. Coding is an integral part of an inte
The interview included scripted questions, general engineering questions, work history, and a few more generic "problem solving" questions. For example, "If you were shrunk down to the size of a dime and put in a blender, how would you escape?"
I was contacted through LinkedIn by a recruiter. After giving them a few references from friends who work at Google, I was able to bypass the phone screen. My friends said they received a form that they filled out. Even then, I was passed around to
After I passed the phone interview, I had 6 on-site interviews in 2 days, each 45 minutes long. My former co-workers described all the favorite topics. It is mostly questions on Algorithms and Data Structures. Coding is an integral part of an inte
The interview included scripted questions, general engineering questions, work history, and a few more generic "problem solving" questions. For example, "If you were shrunk down to the size of a dime and put in a blender, how would you escape?"
I was contacted through LinkedIn by a recruiter. After giving them a few references from friends who work at Google, I was able to bypass the phone screen. My friends said they received a form that they filled out. Even then, I was passed around to