Process
I had two phone tech screens for the software engineer position.
First, I don't know why both phone calls were so unclear that I could barely hear the engineer's voice. I felt like I was talking with an engineer who was speaking from inside a cave.
The first tech screen was good, and the engineer was helpful, but the phone call was still unclear.
The second one was one of my worst experiences ever; I think it will be in my top 5.
The questions were basically easy, but the engineer made them hard to understand and set up traps to confuse me. You needed to find a way to stop them from confusing you and provide a correct answer.
I don't know if this is how Google engineers talk to each other, but perhaps Google needs to consider if it's hiring too many people who don't know how to communicate.
I didn't even want to ask the engineer questions; I just wanted to say goodbye after finishing the coding questions. I can imagine it would be hard to work with people like that.
Next time, if you can't hear the engineer's voice clearly, just ask them if they can use a different tool to call you. Otherwise, the unclear voice will destroy your interview.
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
- 2.0It's very hard to land on projects that benefit your careerSoftware Engineer • Current EmployeeMountain View, California, United StatesJuly 24, 2013Pros: Benefits are good. Shuttle transportation can be useful for many people. Occasionally there are interesting talks, but conference rooms are often way too tiny.Cons: The interviews are really bad for the applicant: you learn nothing from what you will be doing and are interviewed only by people from completely different areas of expertise than yours. If you decide to come here, expect to have 5-6 layers of management above you. Unless you are a big shot or manage to get a strong ally, you often get the promise of leading some significant project, only to be exchanged without notice with more "experienced" people. Only a minority of engineers get to do the interesting stuff: Google+, Knowledge Graph, etc. If you are part of the other 99%, things are less exciting and the lower your rank is, the less freedom you have.
- 5.0Good Work, Needs BrainpowerSoftware Engineer • Former EmployeeNew York, New York, United StatesFebruary 22, 2024Pros: Good and nice, actually. Very good to consider.Cons: You might need to put your brain.
- 5.0Great Atmosphere, Too Much PressureSoftware Engineer • Current EmployeeUnited, Louisiana, United StatesAugust 25, 2022Pros: There is a great atmosphere.Cons: Too much pressure to cope with.
Google Interview Questions
