The interview process was very unprofessional. He did cut me off while I was giving my introduction, and I was just talking about my experience in tech stacks, which I believe is important. He was more worried about the time constraints than about me, the interviewee.

While the interview round was for SDE-3, I was asked a DSA question. Then he mentioned he wanted an optimal solution, so I started from brute force and was thinking through to optimize it. Again, he did cut me off and wanted me to code the brute force approach itself. Then he distracted me by asking trivial questions and not giving me enough time to think on an optimal solution.

There was a contrast in communication between what the recruiter mentioned versus what was expected in the interview. I was told that the interview was not language-specific, but Java-specific questions kept coming up in spite of my mentioning that my background is in other languages (Go, Python).

Implementation of a hashmap in Java was asked. But again, I took it as a general problem-solving exercise by stating, "Let's try to design the hashmap from scratch and not go into language specifics." So I came up with open addressing, which I checked is used in Python, with which the interviewer was not satisfied. He straight away said, "This is not how a hashmap is implemented." Again, the hashmap designing was being done in the last 3 minutes. To me, it appeared like too much attachment to a specific tech stack.

Apart from this, there were some gaps in communication as well. Probably the interviewer was not comfortable in English, so I had to make him repeat what he was trying to say to make sense out of his statements.

Companies should understand that while they are judging an interviewee on their technical skills, the interviewer is also judging the company's work culture and the environment by the interviewer's behavior.

1. DSA problem on Linked List
2. DSA problem on checking palindrome
3. Design Hashmap
4. Design notifications system.