Recruiter sent out numerous interview guides to review before the interview that repeatedly said 'talk out loud'. Interviewers asked questions that had pretty obvious answers so I explained all the more obvious but less optimal solutions before touching on the optimal one. The interviewers spent a lot of time asking about why those weren't optimal and apparently reported this as if I had to be guided to a solution. For what may be the first time ever, I got interview feedback saying I got to the optimal solution but it took some guiding. In summary, I did what the interview prep asked me to do, explain my thought process. This was perceived as if I kept taking the wrong path to the solution.
Interview questions [1]
Question 1
Easy questions with obvious, cliche solutions like "use a binary tree" or "use a hash map"
After clearing all the interviews in 2 months, here comes the team match. Where no one ever knows when they gonna get a team match call. Even if you get the TM call next comes the HC again no one knows why they reject.
Interview questions [1]
Question 1
Coding questions from Leetcode google tagged but deep dived into it based on the level.
The interview lasted about a day, with 5 different interviewers. For each section, the technical questions took most of the part. They also showed me their office in Toronto, which was nice
Interview questions [1]
Question 1
What was the most difficult problem you solved during your last job?
it was difficult. lengthy dsa questions. design was ok. needs nice preperation. googlyness also needs preperation. it was difficult. lengthy dsa questions. design was ok. needs nice preperation. googlyness also needs preperation.
