Process
Minimal interaction between interviewers to try to minimize groupthink. That's good.
I have had multiple bouts of interviews, and in more than one of them, at least one interviewer argued with me.
Whether that's good or bad depends on if that's what it's like working there. If it is, well, might as well weed out people who don't like to argue about every detail all the time.
Questions
When I tried to use yield return in an answer to a question, my interviewer stopped that question and asked me to implement an iterator.
Was this helpful?
Interview Statistics
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Success Rate
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.
Google Work Experiences
- 4.0Good Pay, Bad ChairsSoftware Engineer • Former EmployeeSan Francisco, California, United StatesSeptember 10, 2020Pros: Good environment. Good people. Good pay. Big breaks. Big vacation.Cons: Competitive. Table tennis. No Hispanic guys. No break time. Bad chairs.
- 5.0Great working environmentSoftware Engineer • Current EmployeeNovember 6, 2018Pros: Here you receive a great opportunity to solve worthwhile problems with outstanding teammates. Great benefits, great pay.Cons: There's the danger of getting too familiar and comfortable with internal tooling. When you do, you can lose touch with the tools and trends of the greater software engineering community. It's like being in a bubble.
- 5.0Best job everSoftware Engineer • Former EmployeeJune 29, 2015Pros: - Very professional colleagues. - Best technical equipment right at hand. - All the fun stuff (canteen, theme floors, ...).Cons: Sometimes organization is a bit chaotic. You need ridiculous amounts of proficiency and luck to get hired.
Google Interview Questions
