The experience was pretty average overall. Some of the questions leaned heavily on technical depth, requiring precise problem-solving, while others were more open-ended prompts designed to see how you think under pressure.
The variety made it a bit unpredictable. One moment it felt like a coding test; the next, like a casual brainstorming session.
Practicing LeetCode-style questions would definitely help with the technical side. However, it also seemed important to be ready for those less-structured discussions where they just want to understand your approach and reasoning.
What projects did you work on at your previous job?
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.