**Round 1 : Online Assessment **
Hackerearth based test, 3 Coding questions, 90 minutes.
Level : Very Hard
I got 3 questions with the following weightages :
1 Medium : Scored (50/50)
1 Hard : Scored (100/100)
1 Hard : Scored (60/100)
This was hands down the toughest OA I have given. Do not remember the exact questions but it involved the following concepts :
Q1 : TreeMap/Binary Search (Medium)
Q2 : Graph Based Question (HARD)
Q3 : 2D DP based problem on a tree (HARD)
I scored a total of (210/250) in this round and the 1st Virtual Onsite Interview was scheduled.

Round 2 : Virtual Onsite 2 (DSA)
First 10 minutes we introduced ourselves and briefly talked about our roles at our respective organizations.
1st Question (Medium-Hard) : Tree based DP question, question is not on leetcode/gfg.
2nd Question (Easy-Medium) : Design data structure with O(1) add/delete/getRandom() (https://leetcode.com/problems/insert-delete-getrandom-o1/)
The interviewer was very polite and helpful. I struggled a little in the first question, but the interviewer was kind enough to give me a hint based on which I was able to solve it.
The second question I had done previously on LC, so explained the approach and coded it.
Note : Didn't run the code on IDE but I was expected to dry run sample test cases for both problems.
Recieved call after an hour after interview that I had cleared the 1st Onsite round and scheduled the LLD round.

Round 3 : Virtual Onsite 2 (LLD (apparently))
This is the round which made me lose all hope and faith in myself and the process.
I went into the interview, the interviewer was 10 minutes late, didn't switch on their camera and to my surprise posed a HLD problem. I did mention it to the interviewer that a LLD format was communicated to me. I was given the following response :
"How does it matter, are you not prepared for HLD?".
He posed the HLD question, and throughout the discussion he felt uninterested, at some points I had to call out "hello hello" multiple times because there was no response from the other side when asking doubts, asking feedback on a design decision etc. Things were going barely okay uptil this point. Now he poses the question :
"How will you add/remove servers without downtime?"
Answering this question brought me to the topic of consistent hashing, I kid you not, the interviewer had 0 idea what consistent hashing was. This is when I opened draw.io, shared my screen and started explaining the concept of consistent-hashing, the ring structure, redundant/virtual servers with k hash functions.
This is the response I recieved :
"you are just throwing words at me, I do not understand why you are talking about hashing in a System Design interview?"
I tried to again put into perspective the concept, and how it solves the problem of downtime during addition/deletion of servers (god bless Gaurav Sen for the incredible video on consisten hashing!), but he ended the interview on the note "Please accept that you're wrong, do not keep repeating about hashing, I was not looking for this answer".
I asked what he was looking for, he told me that you should have said DB sharding. This was the moment I was like, umm what?
Wasn't the question about reducing downtime when adding/deleting servers? How does DB sharding come into the picture? He refused to elaborate, said it was nice talking to you, good luck and disconnected.
Verdict : The HR kept ignoring my messages and calls for a week, earlier all responses were within 12 hours from her. After a week I recieved a generic rejection email.

What I learnt from this?
I have been preparing LC, LLD, HLD, OS for quite some time now, this was to minimise the chances of me messing up an opportunity. Never took into account the possibility that the interviewer might mess up my chance, it hurts way more.
I have come to terms with it now, there are no shortages of companies/opportunities/roles in the market right now.
I treat the interviewers/HR personel as ambassadors of the company, if they're behaving like this now, I think it was for the better that I am not joining this organisation.