First of all, in all of my technical interviews, no one bothers introducing themselves or explaining their roles.
I applied for an L4 position and made it past the phone screen. In the onsite interviews, I received three 'hire' results, one 'lean hire,' and one 'no hire.' I presume the 'no hire' came from a technical interview where the interviewer kept interrupting me, and the question was poorly designed.
When the results went to the hiring committee, they stated that based on the 'no hire' result, they would downlevel me to an L3 position, which is entry-level. I have 10 years of work experience, so this felt like a slap in the face. To add insult to injury, I was then required to complete follow-up interviews for the L3 position.
The real kicker was that in the L3 interview, I was asked questions about concurrency and thread blocking—advanced computer science topics typically expected for a senior software engineer. Needless to say, I failed to pass this and was rejected.
On top of all of this, my recruiter was terrible at communication and repeatedly mixed up my information with other candidates.
In any case, my review won't change anything, but I'm sharing this experience. If you're applying to Google, you'll need a lot of patience and persistence.
LeetCode type data structure questions
The following metrics were computed from 4 interview experiences for the Google Software Engineer role in Washington, District of Columbia.
Google's interview process for their Software Engineer roles in Washington, District of Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in Washington, District of Columbia.