Environment.
People.
Work station.
Life balance.
There were no cons. There was only good stuff about it.
Skip the first initial interview, as I performed well in their interview one year ago. The onsite consisted of 5 rounds. Ten questions were asked, all focused on coding. There were no design questions. One question was from "Cracking the Coding Inte
Calm, the interviewer was polite and nice. The question was quite hard, and the interviewer initially did not provide me with a lot of hints. Overall, I had an OK experience. Google as a company is quite hard and needs a lot of preparation to get in.
A giant waste of time. This was for a cloud role. Google will only ever care about LeetCode problems rather than asking questions about microservice architectures. Don't bother unless you've devoted your life to LeetCode and forsaken real-world know
Skip the first initial interview, as I performed well in their interview one year ago. The onsite consisted of 5 rounds. Ten questions were asked, all focused on coding. There were no design questions. One question was from "Cracking the Coding Inte
Calm, the interviewer was polite and nice. The question was quite hard, and the interviewer initially did not provide me with a lot of hints. Overall, I had an OK experience. Google as a company is quite hard and needs a lot of preparation to get in.
A giant waste of time. This was for a cloud role. Google will only ever care about LeetCode problems rather than asking questions about microservice architectures. Don't bother unless you've devoted your life to LeetCode and forsaken real-world know