Archived Interview Experiences

My phone screen used a frontend coding question. The interviewer was friendly, came prepared with slides, and offered hints. There was ample time for Q&A at the end.

I interviewed the previous week and failed to solve the coding problem. The interviewer gave no hints throughout the entire interview. I encountered a hard-level problem and was un...

I did not finish the coding implementation in time and failed the phone screen.

The onsite consisted of four rounds: system design, coding, debugging, and a hiring manager (HM) round. The system design round was difficult due to an unfamiliar question and a po...

I spent some time discussing the optimal approach with the interviewer, then debugged two small bugs before completing the implementation. After passing, I received an onsite invit...

The phone screen for a Data Engineer role consisted of 20 minutes of Python followed by 30 minutes of SQL with 4 questions. All questions were variations of known problems rather t...

The interviewer immediately required an optimal solution without allowing any discussion. The interviewer gave no interaction throughout and showed no engagement. I found the exper...

The interviewer was helpful and provided guidance throughout. I had just started practicing and wrote code with bugs I could not fix in time, resulting in a failure.

I used this onsite as practice and found the overall difficulty high. All communication with HR was via email only. I had already lost interest after learning the compensation rang...

I was surprised to encounter a project deep dive in a phone screen, as this is uncommon. The coding section was an incremental problem with three parts, each adding new rules on to...

I received a rejection email two days after the onsite. The four rounds were debugging, coding, system design, and HM. The debugging round was the most confusing, and I struggled d...