After a very informal interview, I was scheduled for a live coding interview using a shared word processor. The interviewer did not connect at the scheduled time, so we had to reschedule a few hours later.
The coding interview was nothing like the book CTCI or the Google YouTube demonstration. The interviewer pushed me to start coding right away, did not want me to talk, and was not collaborative at all.
At the end, I came up with an interesting solution for the problem but made many silly mistakes, mixing up some variables under the time pressure. The interviewer simply said that it was enough and dismissed me.
There were no questions, only the coding challenge.
It was a problem related to a board game with particular rules, and the state of a piece on the board needed to be checked.
There was a dependence on the pieces in neighboring cells, and a recursive solution was forbidden.
The following metrics were computed from 16 interview experiences for the Google Embedded Software Engineer role in United States.
Google's interview process for their Embedded Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Google's Embedded Software Engineer interview process in United States.