1. Glider test: link with questions related to networking and code snippets.

2. Talk with HR.

3. Video call with a technical interviewer for an hour.

4. Onsite interview for 3 hours with 2 or 3 people.

The video call interview involved a walk-through of my resume, covering all my projects and intern experience.

The onsite interview was the worst experience I've had with one of the interviewers. The questions were easy, focusing on hash maps and other data structure-related topics. There were also some basic C++ and OS-related questions.

I had not mentioned C in my resume, but they expected socket programming knowledge. This was only communicated to me during the onsite round, and it was the reason given for my rejection.

My question to the HR representative and the video interviewer is: if they required a specific skill, why wasn't it communicated at the beginning?

The HR representative certainly bragged a lot about the company and its stock values, yet they handled me so badly throughout the interview process. I feel fortunate to have been rejected by them, as the organization is clearly doing very well. The HR representative who handled my candidacy and one of the onsite interviewers are probably the worst people I have encountered in interviews.

I usually check reviews on Glassdoor and have never written one myself until now. This company's interview process compelled me to do so.

Learn in-depth about hash maps, including the complexity of their operations.