Process
The process took about two months. I had two phone screens: the first was behavioral, and the second was technical. Afterwards, they said they would call me, and about a month later, they arranged an in-person interview. I had to do a problem for them and then discussed the results with them. Finally, I had group interviews with the team I was supposed to work with.
Questions
Place a person or object at a midpoint in a field. Note that the person or object does not know numbers or distance. It's unclear how big the field is, though it has dimensions.
Was this helpful?
Interview Statistics
The following metrics were computed from 44 interview experiences for the Google Software Engineer In Test role in United States.
Success Rate
Google's interview process for their Software Engineer In Test 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 In Test interview process in United States.
Google Work Experiences
- 3.0Fast Promotions, Not Much BadSoftware Engineer In Test • Former EmployeeIrvine, California, United StatesNovember 2, 2014Pros: Promotions that were not too long.Cons: Not much to complain about, in my opinion.
- 5.0Software Engineer in TestSoftware Engineer In Test • Former EmployeeMountain View, California, United StatesMay 20, 2019Pros: Superb work culture, great teams to work for.Cons: Too much work pressure and stringent deadlines for SW.
- 3.0Passionate Work, Lacking GuidanceSoftware Engineer In Test • Former EmployeeMountain View, California, United StatesJanuary 25, 2015Pros: Really good work environment. You have to be passionate about doing something there. Otherwise, you won't be able to keep up.Cons: My manager wasn't particularly the best. He didn't offer a lot of guidance or leadership, though you should be self-motivated to work.
Google Interview Questions
