Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en D2L (Toronto, ON) en mar 2023
Entrevista
Overall it was a very easy interview but I felt rushed by the interviewer. First round with the HR was introductory - she was very nice to talk to and asked very basic questions about my past work experiences, why I was interested in D2L and what were my strongest skills etc. I was very happy when she told me they are looking for someone with AWS experience though it wasn't mentioned anywhere in the job posting and I happen to have a lot of AWS experience so we both thought that my skills and experience matched exactly what they were looking for. Next interview was supposed to be code review and I wasn't explicitly told that I will have to write code as well in this round but they had sent me general guidelines on how the interview process would be so I was prepared to write code and didn't mind it at all. And this wasn't writing one or two lines of code to correct the piece I was supposed to review - there was a separate coding challenge unrelated to the review. However they wanted to do a code review AND a coding assignment in 30 minutes which I thought was very rushed and not enough time. Out of the scheduled 30 mins, 5 minutes were spent in introducing each other so we roughly had about 25 minutes to review a snippet of code which was about 30 lines - two interconnected functions and also to write a program to solve a coding challenge. I think its very impractical to expect someone to do both - review a piece of code they are looking at for the first time and then also expect them to come up with the logic, algorithm and write the code for a new problem in a total of 25-30 mins. I had less than 10 mins to solve the coding challenge which I did and also wrote the code - also the coding challenge was easy leet code level so I didn't have issues solving it within the time limit. But all throughout the review and the coding challenge the interviewer was interrupting me with questions/suggestions and comments which further rushed me. Although I was thinking loud and explaining my thought process and everything that came to my mind - his comments/questions were interrupting my logical thinking process and I wasn't very comfortable with it. I expected the interviewer to listen to me and my thoughts before prompting me with his suggestions/comments. It felt as if he wanted to quickly get done with the interview. In spite of the time crunch I completed both the review and coding challenge but got an email after a week saying they have decided to go ahead with other candidates. No worries I wish them all the luck finding the right candidate for the job :) :)
Overall I thought it was very rushed and they should either schedule more than 30 mins if they want to do review and coding challenge in the same interview or have one task per time-slot.
Preguntas de entrevista [1]
Pregunta 1
Coding challenge was you have an array of integers as input and you have to sort them such that all integers >50 are to the right side and <50 are on the left without altering the order of the original array. For example input is [30,45,50,80,40,90] - the output should be [50,80,90,30,45,40].
Recruiter screening then a technical round where there were 2 questions
1)Gave me a code asked how i would optimize it
2) write a sample code to organize 2 lists
Me postulé a través de una recomendación de un empleado. El proceso tomó 6 días. Acudí a una entrevista en D2L (Kitchener, ON) en sep 2018
Entrevista
Multiple levels of interviews with recruiters, senior developers and a manager/director-level employee that covered all aspects of the role, including communication skills, design skills and coding skills. Online coding test with CoderPad.IO which included writing some simple code and doing a code review in C#. Overall a great experience and I commend the team on their process.
Preguntas de entrevista [1]
Pregunta 1
Given an array of int[] like 1,2,3
Find the next largest integer than can be made with these digits (e.g.: 2,1,3)