Google

This was a standard intro to a coding interview. We covered hash maps, trees, and arrays. I didn't do very well, but I think it was a fair interview all things considered.

There are 6 steps and lots of LeetCode problems to solve. It is a long, grueling experience I don't wish on anyone. There are definitely better ways to do this. I don't think I would recommend this to anyone, ever.

I had an interview that lasted over 8 hours, encompassing both phone and on-site stages. A few weeks later, my recruiter informed me that the hiring committee had selected me for hiring. After a few unsuccessful team matching attempts, my recruiter