The interview process began with a recruiter screen, followed by a technical screen. During the technical screen, I was asked to solve LeetCode 242 (Valid Anagram), which I successfully completed.

Next, I set up the virtual onsite interviews. This consisted of one technical interview, one "system design" interview (though it wasn't truly system design), one manager interview, and one HR screening.

During the technical interview, the interviewer spent the first 20 minutes asking questions about my previous projects. Then, I was asked to solve LeetCode 20 (Valid Parentheses) with a twist. With approximately 18 minutes remaining, the interviewer stated, "I don't feel like asking another question." This was a rather abrupt end to the interview.

The system design interview followed a similar pattern. The first 20 minutes were dedicated to questions about my past projects. The interviewer then took 10 minutes (not an exaggeration) to introduce the challenge, which could realistically have been explained in 2 minutes. This left me with only 30 minutes to solve the problem. I began by outlining a high-level system design, but the interviewers quickly steered me towards database design and schema. This became the primary focus of our discussion, and the interview concluded shortly after. It seemed they were not interested in typical system design topics but rather focused on database design.

Overall, I felt that interviewers should not dedicate the first 20 minutes to questions about previous projects. Additionally, the "system design" interview should be renamed, as it focused solely on database design, not system design.

I was not impressed with the interviewers during the virtual onsite.

LC 242 - Valid Anagram

LC 20 (Valid Parentheses, with a twist)

The "system design" question was designing a version system for different apps where you could tag certain versions to different user groups.