My guess is that the interview difficulty, hiring bar, and interview types (code, design, etc.) depend on the level you are interviewing for. I interviewed for L4 specifically (I believe the title is SWE III).
The process began with a quick HR phone call, followed by a technical phone screen, and finally, the virtual onsite, which included four coding interviews and one behavioral interview.
I passed the onsite and met with a couple of hiring managers for the team matching stage. During team matching, I withdrew from the process. I had a strong offer from another company that was about to expire, and I felt my Google recruiter was taking too long to respond. I didn't receive an explicit offer, but they implied I would get one once I found a team.
My technical screen questions were easy to medium, but the onsite questions were somewhat harder. I started every onsite interview looking at the problem and being completely clueless as to how to solve it. However, by following advice from resources like CTCI, I devised a basic approach that worked. I then iterated with some help from the interviewer to write reasonable code – not amazing code, but reasonable.
Cannot give away anything due to NDA.
The following metrics were computed from 2 interview experiences for the Google Software Engineer III role in Seattle, Washington.
Google's interview process for their Software Engineer III roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer III interview process in Seattle, Washington.