J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Block (Vancouver, BC) en mars 2021
Entretien
I applied online, 2 days later a recruiter contacted me for a quick 30' chat about the position and schedule the first pair programming with a software engineer. Then I move on to chat with a team manager where he asked me about previous experience in building ML models and then some more technical questions.
The last round was virtual on-site with 6 interviews (you could split into multiple days).
Last round includes 2 whiteboards, 1 pair programming, 2 Q&A, and 1 with another top manager. All are technical interviews around ML system designs, domain problems, and ML basic understanding.
It's a long and tough process and you learn a lot too. I like it.
Questions d'entretien [1]
Question 1
NDA but learn about the product that the team you are interviewing for will work on. The recruiter will also give you a guide to study.
J'ai postulé via la recommandation d'un employé. Le processus a pris 2 mois. J'ai passé un entretien chez Block
Entretien
The interview process consists of four rounds: two coding interviews, one design interview, and one behavioral interview. Each interview has two interviewers - one who drives the session and one who shadows. Coding interviews feature LeetCode medium-level questions.
Interview is smooth, met a very collabrotive interviewer to work on a OOP question together, which is broken down to a few sections, each section is followed up with how i would improve and how I would test it.
Questions d'entretien [1]
Question 1
it's about designing a class to keep track of average for streamining data using sliding window
J'ai postulé via un recruteur. J'ai passé un entretien chez Block en janv. 2022
Entretien
Got a phone call from recruiter for background check and then invited me to the next tech interview. The recruiter was nice and gave me very detailed instructions on preparing the interview such as what coding problems I should practice, what skills the interview is focusing on testing. However, at the interview, the interviewer seems doesn't care about time complexity, thinking aloud, optimization etc.
