I had applied on LinkedIn and a few days later got a call from the HR. I had a telephonic round initially. There was a coding question (basic array manipulation) and a few testing-related questions in the telephonic round. The next day after the interview, I was given detailed feedback of how I had done and what are the things I need to take care of before I interview onsite. The HR was open to delaying the interview if I wanted more time to prepare more. There were 3 coding, 1 testing-related interview, and 1 Googlyness interview. In coding rounds, I had to come up with an algo, optimize it, write code and write test cases for the problem given. 2 of the interviews did not require knowledge of fancy data structures. What was needed was a lot of depth in the simple DS like linked lists, file IO, string/array manipulations, maps, etc. Apart from being good at algorithms, Google also expects the candidate to be an expert at the language chosen. The code quality bar is high. For the testing interview, I was given a scenario and I had to come up with test cases, strategy, etc. There was also a question where I had to give out test data for a given function. Googlyness interview was mostly around scenario-based questions. The interviewer put me in different situations and asked me what I would do in such situations. To prepare for this, think of situations you might have encountered in your working experience and elaborate on those. Most of the interviews were on time; there were minimal delays, if at all. HR was helpful, shared a lot of prep material, provided feedback.
NDA.
The following metrics were computed from 4 interview experiences for the Google Test Engineer role in Bengaluru, Karnataka.
Google's interview process for their Test Engineer roles in Bengaluru, Karnataka is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Test Engineer interview process in Bengaluru, Karnataka.