Great work environment and lots of collaboration!
It was sometimes tedious and boring.
The interview included behavioral questions, followed by data structures and algorithms. It was a great experience overall, but the hurdle to break in was too high. You need to review core CS concepts, as well as demonstrating you're a good team pl
The interview was easy and straightforward. They focused on old projects and wasted no time. The interviewer was kind. The hardest part was answering a computer science fundamentals question. I was done in only a few minutes.
First, I had a call from the recruiter, which was very standard. Then, a technical phone call from an engineer. Google overworks their engineers. The guy I spoke to seemed very disorganized and stressed. Even though he asked for me by name, he had s
The interview included behavioral questions, followed by data structures and algorithms. It was a great experience overall, but the hurdle to break in was too high. You need to review core CS concepts, as well as demonstrating you're a good team pl
The interview was easy and straightforward. They focused on old projects and wasted no time. The interviewer was kind. The hardest part was answering a computer science fundamentals question. I was done in only a few minutes.
First, I had a call from the recruiter, which was very standard. Then, a technical phone call from an engineer. Google overworks their engineers. The guy I spoke to seemed very disorganized and stressed. Even though he asked for me by name, he had s