Great pay, hard problems, and great coworkers.
There was somewhat tense work-life balance pressure, but it was not crazy.
The interview process involved three rounds: a recruiter screen, a one-hour technical screen, and four hours of onsite interviews. The four onsite rounds were System Design, Debugging, Behavioral, and Algorithms – all pretty standard in nature.
The interviewer seemed un-interested from the very beginning. This made the interview tough. I completed the questions and also added tests, but overall the interviewer looked unhappy, as he was from the beginning. End result: rejected.
Given two LeetCode hard problems. They were on graphs and queues. They expect you to know the space and time complexity. Also, they do a lot of incremental difficulty, so make sure your algorithm will scale.
The interview process involved three rounds: a recruiter screen, a one-hour technical screen, and four hours of onsite interviews. The four onsite rounds were System Design, Debugging, Behavioral, and Algorithms – all pretty standard in nature.
The interviewer seemed un-interested from the very beginning. This made the interview tough. I completed the questions and also added tests, but overall the interviewer looked unhappy, as he was from the beginning. End result: rejected.
Given two LeetCode hard problems. They were on graphs and queues. They expect you to know the space and time complexity. Also, they do a lot of incremental difficulty, so make sure your algorithm will scale.