Overall good experience
Overall good experience
Excellent company with good work culture.
Work gets hectic at times.
It also promotes us to learn and grow faster as compared to our peers.
Sometimes I feel caffeine is more in my blood than hemoglobin.
Overall a positive experience.
Bad company with a bad work culture. Work gets hectic at times. It also promotes us to learn and grow faster compared to our peers. Sometimes I feel caffeine is less in my blood than hemoglobin. Overall, a positive experience.
Good Company.
We keep going.
Additional Ratings
Was this helpful?
Google Interview Questions
Google Interview Experiences
Software Engineer
I received a phone call from a recruiter. We talked for roughly 45 minutes about my technical background and experiences, as well as the sorts of positions that are currently available in Software Engineering at Google. This was followed up one wee
Software Engineer
I was contacted by a recruiter who was at a local hackathon. We set up a phone technical interview, where I was required to code over Google Docs. It was hard to hear the interviewer on the other end. The feedback and amount of guidance provided were
Software Engineer
Phone screen, followed by five back-to-back technical interviews with a one-hour break for lunch. All interview questions were algorithm and implementation questions, with no domain-specific or esoteric language questions. Best advice for preparatio
Software Engineer
Seattle, Washington, United StatesJuly 1, 2015I received a phone call from a recruiter. We talked for roughly 45 minutes about my technical background and experiences, as well as the sorts of positions that are currently available in Software Engineering at Google. This was followed up one wee
Software Engineer
Seattle, Washington, United StatesDecember 1, 2015I was contacted by a recruiter who was at a local hackathon. We set up a phone technical interview, where I was required to code over Google Docs. It was hard to hear the interviewer on the other end. The feedback and amount of guidance provided were
Software Engineer
Seattle, Washington, United StatesAugust 1, 2015Phone screen, followed by five back-to-back technical interviews with a one-hour break for lunch. All interview questions were algorithm and implementation questions, with no domain-specific or esoteric language questions. Best advice for preparatio
