The interview began with an online assessment. The questions were both LeetCode easy to easy-medium.
After that, the recruiter reached out, and we had a 15-minute chat about Google, my interests and deadlines, and the interview process.
Following this, I scheduled the on-site interviews, which consisted of three technical rounds and one behavioral round.
The technical rounds featured LeetCode easy to LeetCode medium problems, all of which were very doable.
The first two interviewers were great, but the last technical interviewer had a thick accent and poor reception, leading to frequent delays and cutouts.
The behavioral round was surprisingly the hardest of the four. It involved basic questions about my experience and how I would act in certain situations. However, my interviewer had absolutely no conversational skills, and it felt like talking to a wall. Every answer I gave was met with short, curt responses that I found a bit rude.
Questions covered tries, sorting, stacks, greedy algorithms, and backtracking.
Many people also encountered dynamic programming and graph theory problems, but I did not.
The following metrics were computed from 28 interview experiences for the Google Software Engineer- Early Career role in United States.
Google's interview process for their Software Engineer- Early Career 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- Early Career interview process in United States.