All good in the role.
Too much work stress in the role.
Mostly LeetCode questions. A very frustrating experience for someone who is more of a builder and less of a LeetCode person. It felt more like an interview conducted during campus hiring. Communication was clear and good throughout.
Got a call from HR and scheduled the interviews. There were two coding interviews and one system design interview. In the first coding interview, a priority queue-based question was asked (see LeetCode question no. 1834).
Excellent interview process. The recruiter was friendly, and the interviewers were helpful whenever we got stuck. Though the difficulty was very high, overall, I had a lot of learning.
Mostly LeetCode questions. A very frustrating experience for someone who is more of a builder and less of a LeetCode person. It felt more like an interview conducted during campus hiring. Communication was clear and good throughout.
Got a call from HR and scheduled the interviews. There were two coding interviews and one system design interview. In the first coding interview, a priority queue-based question was asked (see LeetCode question no. 1834).
Excellent interview process. The recruiter was friendly, and the interviewers were helpful whenever we got stuck. Though the difficulty was very high, overall, I had a lot of learning.