The whole interview was, in my case, separated into 3 parts.
The first part was a phone screening where you answer 3 theoretical questions.
The second part was a 90-minute coding challenge (similar to LeetCode).
The third part was more about negotiating salary, and you get to hear their expectations of you.
Dijkstra's and A* pathfinding, but the question was posed in a way that made it unclear if these were the correct solutions to their problem.
The following metrics were computed from 142 interview experiences for the Google Software Engineer role in San Francisco, California.
Google's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in San Francisco, California.