Process
I was contacted by a recruiter.
I had a two-person phone interview and then an on-site interview at headquarters. It was a pretty standard interview process, including algorithm questions and programming on whiteboards.
The last interview was with a manager who asked design questions.
The recruiter was not entirely upfront about the position being an SE in Test role. They stated that I "may" also be considered for that role, when in reality, they were primarily looking to fill that position.
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
- 5.0Amazing Perks, Smart ColleaguesSoftware Engineer In Test • Current EmployeeMountain View, California, United StatesJune 7, 2016Pros: Awesome perks. Smart folks to work with.Cons: None. The company is great.
- 4.0Software Engineer in Test - InternSoftware Engineer In Test • Former EmployeeMountain View, California, United StatesOctober 31, 2014Pros: Really exciting projects, fun teammates, really nice benefits.Cons: Work-life balance was not very good, and communication about expectations was horrible. My host refused to meet to discuss my progress, which meant I was always in the dark.
- 4.0An open and collaborative environment, highly innovativeSoftware Engineer In Test • Current EmployeeMountain View, California, United StatesMarch 4, 2008Pros: Just as most people would expect at a company like Google, there is a lot of opportunity to do great things here.Cons: This seems like not a very big con, but to tell you the truth, the parking lot here is always crowded.
Google Interview Questions
