The process began with a 45-minute phone interview, covering questions about my projects, the I2C bus, and cache architecture.
The 1:1 interviews consisted of speaking with two engineers before lunch for 45 minutes each. The third engineer joined for lunch, who was the same individual from the phone interview. Following lunch, a fourth engineer conducted a separate interview, and then a fifth and sixth engineer interviewed me together.
All the engineers took extensive notes as I answered questions. The fourth engineer took photos of two 'C' programs I wrote on the whiteboard, stating he would discuss the questions and answers with the team. In fact, the other two engineers also mentioned they would share the Q&A and make a joint decision.
For the position of Network Diagnostics Engineer at Mountain View, CA, the questions were:
Similar boards run without problems with the same version of firmware. How would you troubleshoot this particular board?
At the end of the interview, they walked me to the exit and said they would get back to me, but ultimately declined to make an offer.
Can you draw the HW block diagram of your latest project and explain it?
The following metrics were computed from 1 interview experience for the Google Network Diagnostics Software Engineer role in Mountain View, California.
Google's interview process for their Network Diagnostics Software Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Google's Network Diagnostics Software Engineer interview process in Mountain View, California.