Initially, I had an assessment with two coding questions on HackerRank.
Next, I was scheduled for a recruiter call to explain the process for the next steps. I was told about a virtual onsite, which included one "Googleyness" round and three coding rounds.
On the interview day, the first round was the "Googleyness" round. The subsequent coding rounds felt like: LeetCode Easy, then Medium, then Hard.
I did not do well in the second coding round where I got confused with the question, and also the interviewer was a bit rude. That's where I thought I had lost my chance. However, I surprisingly got to the third round, did well, and the interviewer was quite impressed. They told me, "I hope to see you at Google," which gave me hope.
Two weeks later, I received an email from the recruiter for feedback and was then called the next day. I was told that I wasn't selected. I was very disappointed.
Basic questions like "Tell me about yourself," "Work experience," "Challenging task," and "Team project," etc.
Regular expressions (arithmetic operations) - simplify and give the answer (pseudocode and test cases) asked me to walk through the test cases.
Questions with a mix of HashMaps, trees, and Linked Lists.
The following metrics were computed from 1 interview experience for the Google Software Engineer- Early Career role in Atlanta, Georgia.
Google's interview process for their Software Engineer- Early Career roles in Atlanta, Georgia 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 Atlanta, Georgia.